The W3C has released Web Content Accessibility Guidelines (WCAG) 2.1 - which introduces new Success Criteria. Our current accessibility gate aims to satisfy WCAG Success Criteria at levels A and AA. This looks like a very significant expansion of WCAG, so we can expect it to affect Drupal in a lot of challenging ways.
An update to the WCAG supporting documents ("Understanding WCAG") is also proposed (this is where the longer details, examples, testing notes, and techniques live).
As of 24 April 2018 Proposed Recommendation, the following new Success Criteria are confirmed.
Note that some new Success Criteria are also being introduced at level AAA, but since our target is level AA it is not essential that we address these.
Drupal 8 is already leading the way as an accessible CMS. Let's hold on to this achievement :-)
YES. UI and theme changes are expected, e.g.
@todo: Flesh this out when we know more, especially when it reaches the candidate recommendation stage
None expected, as yet.
None expected, as yet.
Postponed: needs info
11.0 🔥
markup
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Moving to core from the ideas queue (which is deprecated).
This issue is very old, and I feel like we already adopted WCAG 2.1 already? https://www.drupal.org/about/core/policies/core-change-policies/core-gat... →
Yes, we're striving for WCAG 2.2 now https://www.drupal.org/about/features/accessibility →