The GAAD Pledge requires us to publish accessibility coding standards
We have a fairly extensive set of coding standards published online https://www.drupal.org/docs/develop/standards → however nothing on accessibility.
WordPress has adopted this https://developer.wordpress.org/coding-standards/wordpress-coding-standa...
It doesn't need to be too exhaustive, as we already have some good content posted elsewhere. We can choose to link to it.
We can state like:
- code should have no axe-core errors (axe clean)
- WAI-ARIA should only be used if semantics cannot be achieved through HTML
- Dynamic changes to the DOM will be announced to the reader with Drupal.announce()
- Elements will be hidden in a consistent fashion with the Drupal CSS classes (visually-hidden, hidden & focusable)
- The TabbingManager should be used of the tab order needs to be adjusted
I don't think we need to repeat content that is provided elsewhere. This can just be a concise place to provide high-level accessibility guidance for busy developers.
Active
Idea
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
+1
Although, if this is a requirement of the GAAD Pledge do is this issue necessary?
This is being implemented in 📌 Add Accessibility Coding Standards Active .