• AccessibleSpecs

Guideline 8. Implement specifications that benefit accessibility

8.1 Implement accessibility features (P1)

1. Implement the accessibility features of specifications (e.g., markup languages, style sheet languages, metadata languages, and graphics formats).

Normative inclusions and exclusions

1. This checkpoint applies to both W3C-developed and non-W3C specifications.
2. For the purposes of this checkpoint, an accessibility feature of a specification is either:
   • one identified as such in the specification, or
   • one that allows the author to satisfy any requirement of the "Web Content Accessibility Guidelines 1.0" [WCAG10].
3. The user agent is not required to satisfy this checkpoint for all implemented specifications; see the section on conformance profiles for more information.
4. Conformance detail: For all content

Notes

• The Techniques document [UAAG10-TECHS] provides information about the accessibility features of some specifications, including W3C specifications.

UAAG2 ISSUES

• what kind of information are we trying to convey to the user about the relationsship of columnes in a colgroup. What is the UA supposed to communicate to the user.
• TABINDEX and ACCESSKEY as curently implementd are confusing to end users. Although TABINDEX=-1 and ACCESSKEY are used extensively in AJAX and new web applications. How to resolve?

8.2 Conform to specifications (P2)

1. 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 [WCAG10].

Sufficient techniques

1. When a requirement of another specification contradicts a requirement of the current document, the user agent may disregard the requirement of the other specification and still satisfy this checkpoint.

Normative inclusions and exclusions

1. A specification is considered "available" if it is published (e.g., as a W3C Recommendation) in time for integration into a user agent's development cycle.
2. The user agent is not required to satisfy this checkpoint for all implemented specifications; see the section on conformance profiles for more information.
3. Conformance detail: For all content

Notes

• For instance, for markup, the user agent may conform to HTML 4 [HTML4], XHTML 1.0 [XHTML10], and/or XML 1.0 [XML]. For style sheets, the user agent may conform to CSS ([CSS1], [CSS2]). For mathematics, the user agent may conform to MathML 2.0 [MATHML20]. For synchronized multimedia, the user agent may conform to SMIL 1.0 [SMIL].

UAAG2 ISSUES

• Should this be removed due to vagueness. Can you pick an choose conformance to specifications. Or, must a UA conform to all specifications for all item in the UAAG conformance claim.