• AccessibleDocumentation

Guideline 12. Provide accessible user agent documentation and help

12.1 Provide accessible documentation (P1)

1. Ensure that at least one version of the user agent documentation conforms to at least level Double-A of the Web Content Accessibility Guidelines 1.0 [WCAG10].

Normative inclusions and exclusions

1. Conformance detail: For user agent features

UAAG2 ISSUES

12.2 Provide documentation of accessibility features (P1)

1. Provide documentation of all user agent features that benefit accessibility.

Sufficient Techniques

1. The user agent may satisfy this checkpoint either by
   • providing a centralized view of the accessibility features, or
   • integrating accessibility features into the rest of the documentation.

A centralized view is sufficient to satisfy this checkpoint and is required to satisfy checkpoint 12.5.

Normative inclusions and exclusions

1. For the purposes of this checkpoint, a user agent feature that benefits accessibility is one implemented to satisfy the requirements of this document (including the requirements of checkpoints 8.1 and 7.3, and the API requirements of guideline 6).
2. Conformance detail: For user agent features

Notes

• The help system should include discussion of user agent features that benefit accessibility. The user agent should satisfy this checkpoint by providing both centralized and integrated views of accessibility features in the documentation.

UAAG2 ISSUES

• see http://lists.w3.org/Archives/Public/w3c-wai-ua/2006OctDec/0049.html

• Update normative inclusion 1. to include "only if a feature is implemented" (the inclusion specifies the requirements of 8.1, 7.3, and guideline 6. some of the requirements may not be implemented, and the UA should not have to document them) (conformance for 12.2 is determined by dcoumentation, not implementation.)

12.3 Provide documentation of default bindings (P1)

1. Provide documentation of the default user agent input configuration (e.g., the default keyboard bindings).

ckl: 2. Establish and document how the user agent resolves key binding conflicts between the user agent user interface, user agent extensions (e.g plug-ins), HTML elements (i.e. accesskeys), and javascript functions (i.e. keypress events).

Sufficient Techniques

1. If the user agent does not allow the user to override the default user agent input configuration (see checkpoint 11.3), the documentation used to satisfy this checkpoint also satisfies checkpoint 11.1.

Normative inclusions and exclusions

1. Conformance detail: For user agent features

Notes

• Documentation should warn the user whenever the default input configuration is inconsistent with conventions of the operating environment.

UAAG2 ISSUES

• Remove sufficient technique from 12.3 (poorly worded and a statement of fact)

12.4 Provide documentation of changes between versions (P2)

1. Provide documentation of changes since the previous version of the user agent to features that benefit accessibility.

Normative inclusions and exclusions

1. The features that benefit accessibility are those defined in checkpoint 12.2.
2. Conformance detail: For user agent features

UAAG2 ISSUES

12.5 Provide dedicated accessibility section (P2)

1. Provide a centralized view of all features of the user agent that benefit accessibility, in a dedicated section of the documentation.

Sufficient Techniques

1. A centralized view is required to satisfy this checkpoint and is sufficient to satisfy checkpoint 12.2.

Normative inclusions and exclusions

1. The features that benefit accessibility are those defined in checkpoint 12.2.
2. Conformance detail: For user agent features

UAAG2 ISSUES

• needs clarification in wording in normative inclusion 1, specifing user agent features rather than content.
• expand Normative inclustion to include content info from 8.1 and techniques of 12.2