Many clients, particularly administrations are paying attentions to following standards and may impose their site to be W3C compliant.
The purpose of this META is to determine whether Drupal Core should follow W3C and if yes, to list initiatives, issues and tools to make it happen.
As an helper tool, I have started to port
W3C Validator →
module. You can use the 8.x-dev version to find out that Drupal Core does not validate W3C standards yet.
Currently, it does only :
- validate websites accessible through the internet
- validates node pages and admin pages (either as anonymous or registered user)
- display nymber of errors / warnings
- display what's wrong
None.
None.
Active
11.0 🔥
ajax system
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Used to alert the accessibility topic maintainer(s) that an issue significantly affects (or has the potential to affect) the accessibility of Drupal, and their signoff is needed (see the governance policy draft for more information). Useful links: Drupal's accessibility standards, the Drupal Core accessibility gate.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Regarding the accessibility aspects of W3C validation, there is some overlap with ✨ Automate Accessibility Checks for Core Active
Specific implementations from that issue are in 📌 Automated A11y tests in Nightwatch Fixed , 📌 Automated A11y tests in PHPUnit Needs work .