#Accessibility

Automatically closed - issue fixed for 2 weeks with no activity.

The ideas project is being deprecated.

The issue summary refers to the problem in Seven, Bartik, and Umami themes. Since 2 of those are no longer in core and there has been several years of work on Umami, is this still relevant? Are there existing issues in core for remaining problems?

If the community approves such a list, what would be the criteria used to do that and where would that criteria as well as the results be documented?

The core ideas project is being deprecated, moving to core.

Drupal has signed the GAAD pledge and there are issues in other projects for implementation. Therefore closing this issue.

The Coding Standards are being discussed in 📌 GAAD Pledge - Publish Accessibility Coding Standards Active
The documentation is being done in 📌 Update documentation for GAAD Pledge Active

This is being implemented in 📌 Add Accessibility Coding Standards Active .

This needs to be converted to the new coding standards issue template. That will including adding proposed text.

The page in IS has the following.

The Drupal Accessibility Team and project governance will follow the latest recommended release of the WCAG guidelines (WCAG 2.2 AA).

So, I think this has been fixed.

This was partly changed in 🐛 Umami page.tpl.php breaks block placeholders Needs review which was similar but I think more problems were identified here.

@berdir just opened 🐛 Umami page template renders header regions multiple times Active too.

We don't have dropbuttons for saving anymore so we need a title and IS update here.

Also #19 is probably going to cause massive confusion over this if that wasn't also taken into account.

I was too :)

Automatically closed - issue fixed for 2 weeks with no activity.

@rinku jacob 13, 📌 Potentially remove -ms-high-contrast Needs work is probably the correct issue for your changes.

What's the status of this issue?

I believe the ViewsUpdateConfig functions now are properly looping through existing views and setting the grouping to the default if it is not already set.

If using grouping on existing views, the default is the

element as it is already set to, after the config update executes.

themusician → changed the visibility of the branch drupal-1383696-drupal-1383696-82 to hidden.

themusician → changed the visibility of the branch drupal-1383696-drupal-1383696-82 to active.

i've assigned the issue to myself and already created a MR.. Will work on an initial draft the next few days...

I have created a kernel and Nightwatch tests for this merge request.

I am looking into it.

This field type and widget is being deprecated and moved out of core eventually, do we want to bother working on the wording of it? 🌱 [Meta] Deprecate text_with_summary Active

Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .

aaron.hirtenstein → credited waako → .

Hi my name is Ana (@anilu) and we are at Drupalcon Atlanta mentored contribution workshop and are working in documentation for Media core module

I was here!

I attended

I was here!

I'll review the MR

Automatically closed - issue fixed for 2 weeks with no activity.

Claro has overrides for these. If they are only fixed in the toolbar module, the changes won't appear in Claro.

Perhaps the correct solution involves removing the Claro overrides.

MR needs review

The Firefox prefers-color-scheme emulation doesn't work like I thought, so disregard point 1 in #8 🐛 FF & Chrome "dialog close" icon has poor contrast in WHCM + White theme Active . The icon appears with good contrast when the text / background colors are changed manually in the color settings.

However, I see the problem in dark themes on Edge Mac with the Page Colors setting.

It looks like dark theme forced-colors mode worked in Chrome as of 🐛 Dialog close icon not reliably visible in forced colors mode Fixed . I don't know what is different now.

Attaching screenshots of the problem in Edge, and in Edge & Chrome after the change in the MR.

Problem in Edge with Page Colors setting

After the changes in the MR

Edge with Page Colors setting

Chrome, forced-colors, dark