[L3 CR] Horizontal Review: Accessibility

[timcappalli]

Request URL: https://github.com/w3c/a11y-request/

FAST Checklist (https://w3c.github.io/apa/fast/checklist.html):

If technology provides features to accept user input

• There is a mechanism to label user input controls in an unambiguous and clear manner.
• Authors can associate extended help information with a control.
• If there is an input error, it is possible to associate the error message clearly with the specific control that is in error.
• There is a mechanism to report and set the state or value of controls programmatically.
• Authors can address multiple types of input hardware (keyboard, pointing device, touch screen, voice recognition, etc.), or the technology supports hardware-agnostic input methods.
• User input does not require specific physical characteristics (e.g., fingerprint readers).
• Authors can ensure a "meaningful" order of controls exists regardless of presentation.

If technology allows time limits

• A feature exists to allow time limits to be extended.
• Time limits for different parts of a task, such as reading instructions vs providing input, can be set separately.

If technology defines an API

• If the API can be used for structured content, it provides features to represent all aspects of the content including hidden accessibility features.
• If the API relies on user agents to generate a user interface, the specification provides guidance about accessibility requirements needed to enable full interaction with the API.

[MasterKale]

Request for review has been created: w3c/a11y-request#101