Problem/Motivation
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.
Remaining tasks
- Define if Drupal Core should follow W3C standards.
- Identify helper tools that might help finding misvalidation.
- Define where child-issues should be open per point / per page or per type.
- Characterize where Drupal does comply W3C and open child-issues.
- Fix child-issues.
Proposed resolution
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 list node pages and shows the result number of error and warnings, but I plan to improve it soon to validate admin pages, user pages, .... as well as displaying details about what's wrong.
User interface changes
None.
API changes
None.
Beta phase evaluation
| Issue category | Bug because it does not seems expected to not validate W3C test. |
|---|---|
| Issue priority | Major because this seems serious to me but does not break any functionnality. |
| Unfrozen changes | Unfrozen because it only changes output markup not APIs |
| Prioritized changes | The main goal of this issue is accessibility and standard respects. |
| Disruption | None. |