Call for Review: HTML Accessibility API Mappings (HTML-AAM) Working Draft

Dear WAI Interest Group Participants,

We invite you to comment on a new Working Draft of HTML Accessibility API Mappings 1.1 (HTML-AAM) at:

HTML Accessibility API Mappings is intended for HTML user agent developers responsible for accessibility in their user agent. It defines how user agents map HTML markup to platform accessibility application programming interfaces (APIs). Documenting these mappings promotes interoperable exposure of roles, states, properties, and events implemented by accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent. It does this by extending the Core Accessibility API Mappings 1.1 (CORE-AAM) and the Accessible Name and Description: Computation and API Mappings 1.1 to provide HTML-specific guidance for how the HTML user agent must respond to keyboard focus, native HTML features, and role, state and property attributes provided via WAI-ARIA.

The mappings defined in this specification were previously published as HTML to Platform Accessibility APIs Implementation Guide, which supported WAI-ARIA 1.0 and HTML 5.0. Since the time that document was created, work on WAI-ARIA 1.1 and HTML 5.1 have led to a larger set of related Accessibility API mappings and the need to express the mappings for various technologies in a consistent manner. This specification therefore replaces the role of HTML to Platform Accessibility APIs Implementation Guide, and that draft specification will be retired.

HTML-AAM is part of a suite of WAI-ARIA-related specifications introduced in the WAI-ARIA Overview at <>.

WAI-ARIA 1.0 is currently a W3C Recommendation. It remains the recommended version for production user agent implementations and authors at this time. WAI-ARIA 1.1 is currently a Working Draft and is supported by this Working Draft of HTML-AAM 1.0. The versions are currently at different levels because HTML-AAM does not have a previous Recommendation, and the two specifications may evolve on different timelines. Eventually these specifications are expected to advance to Recommendation, at which point they would subsume WAI-ARIA 1.0. The stages of specification development are explained in How WAI Develops Accessibility Guidelines through the W3C Process at: <>.

The in-progress updates to HTML Accessibility API Mappings 1.0 are available in an Editors' Draft at <>.

The status of WAI-ARIA versions is updated in the WAI-ARIA FAQ: <>

*For review*:
The First Public Working Draft of HTML Accessibility API Mappings (HTML-AAM) provides another technology-specific module that provides accessibility API mapping support for features in WAI-ARIA 1.1. Other technology-specific mappings will follow. This version provides an initial set of mappings for HTML elements.

Please submit comments to the publicly-archived e-mail:
or file an issue in W3C Bugzilla:
by *8 May 2015*

HTML Accessibility API Mappings is developed through the HTML Accessibility Task Force, a joint task force of the Protocols and Formats Working Group and the HTML Working Group. Information about the HTML Accessibility Task Force Home Page is at: <>.

The first URIs above go to the latest version of this document. The "dated" version of this draft is <>. The difference between these URIs are explained in Referencing and Linking to WAI Guidelines and Technical Documents at: <>.

Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.

Janina Sajka, HTML Accessibility Task Force Co-Facilitator
Charles McCathie-Neville, HTML Accessibility Task Force Co-Facilitator
Paul Cotton, HTML WG Co-Chair
Sam Ruby, HTML WG Co-Chair
Maciej Stachowiak, HTML WG Co-Chair
Michael Cooper, PFWG W3C Staff Contact
Judy Brewer, WAI Domain Lead
Philippe Le Hégaret, Interaction Domain Lead


Received on Tuesday, 7 April 2015 22:11:42 UTC