Guideline 8:
Implement specifications that benefit accessibility
Support the accessibility features of all implemented specifications. Implement W3C Recommendations when available and appropriate for a task.
Developers should implement open specifications. Conformance to open specifications benefits interoperability and accessibility by making it easier to design assistive technologies (also discussed in guideline 6).
While developers should implement the accessibility features of any specification (checkpoint 8.1), this document recommends conformance to W3C Recommendations in particular (checkpoint 8.2) for several reasons:
- W3C specifications include "built-in" accessibility features.
- W3C specifications undergo early review to ensure that accessibility issues are considered during the design phase. This review includes review from stakeholders in accessibility.
- W3C specifications are developed in a consensus process (refer to the process defined by the W3C Process Document [W3CPROCESS]). W3C encourages the public to review and comment on these specifications (public Working Drafts, Candidate Recommendations, and Proposed Recommendations). For information about how specifications become W3C Recommendations, refer to the W3C Recommendation track ([W3CPROCESS], section 6.2). W3C Recommendations (and other technical reports) are published at the W3C Web site.
Checkpoints
8.1
[P1] | - Implement the accessibility features of specifications (e.g., markup languages, style sheet languages, metadata languages, and graphics formats).
|
|---|
8.2
[P2] | -
Use and conform to either
- W3C Recommendations when they are available and appropriate for a task, or
- non-W3C specifications that enable the creation of content that conforms at level A or better to the Web Content Accessibility Guidelines 1.0.
|
|---|