ARIA Deliverables

WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies. The ARIA Project Plan details intended timeline and milestones for this work.

The work has been divided into a series of modules and related documents. The deliverables are:

Deliverable Description Status Editors' Draft Formal Version
ARIA Core Specifications
Accessible Rich Internet Applications (WAI-ARIA) 1.1 This specification provides an ontology of roles, states, and properties that set out an abstract model for accessible interfaces and can be used to improve the accessibility and interoperability of Web Content and Applications. This information can be mapped to accessibility frameworks that use this information to provide alternative access solutions. Similarly, this information can be used to change the rendering of content dynamically using different style sheet properties. The result is an interoperable method for associating behaviors with document-level markup. In Working Drafts; Approaching readiness for CR Editors' draft of Accessible Rich Internet Applications (WAI-ARIA) 1.1 Formal published version of Accessible Rich Internet Applications (WAI-ARIA) 1.1
Core Accessibility API Mappings 1.1 Describes how user agents should map WAI-ARIA features to platform accessibility APIs. Other Accessibility API Mappings specifications depend on and extend this Core specification for specific technologies, including native techology features and WAI-ARIA extensions. In Working Drafts; Approaching readiness for CR Editors' draft of Core Accessibility API Mappings 1.1 Formal published version of Core Accessibility API Mappings 1.1
Accessible Name and Description: Computation and API Mappings 1.1 Describes how user agents determine names and descriptions of accessible objects from web content languages and expose them in accessibility APIs. In Working Drafts; Approaching readiness for CR Editors' draft of Accessible Name and Description: Computation and API Mappings 1.1 Formal published version of Accessible Name and Description: Computation and API Mappings 1.1
Accessible Rich Internet Applications (WAI-ARIA) 2.0 Work to begin after ARIA 1.1 wraps up
ARIA Extensions
Digital Publishing WAI-ARIA Module 1.0 Defines a WAI-ARIA module encompassing an ontology of roles, states and properties specific to the digital publishing industry. This allows an author to convey user interface behaviors and structural information to assistive technologies and to enable semantic navigation, styling and interactive features used by readers. It is expected this will complement HTML5. In Working Drafts Editors' draft of Digital Publishing WAI-ARIA Module 1.0 Formal published version of Digital Publishing WAI-ARIA Module 1.0
Graphics WAI-ARIA Module 1.0 Defines a WAI-ARIA module of roles, states, and properties specific to web graphics. These semantics allow an author to convey user interface behaviors and structural information to assistive technologies and to enable semantic navigation, styling and interactive features used by readers. It is expected this will complement HTML5 and SVG2. In Editors' Drafts, FPWD anticipated soon Editors' draft of Graphics WAI-ARIA Module 1.0 Formal published version of WAI-ARIA Graphics Module 1.0
Cognitive WAI-ARIA Module 1.0 Work not yet begun
WAI-ARIA Interaction Module 1.0 Work not yet begun
Accessibility API Mapping Extensions
Digital Publishing Accessibility API Mappings 1.1 This document describes how user agents maps digital publishing markup to platform accessibility APIs based on the Core Accessibility API Mappings specification for user agents. In Editors' Drafts Editors' draft of Digital Publishing Accessibility API Mappings 1.0 Formal published version of Digital Publishing Accessibility API Mappings 1.0
HTML Accessibility API Mappings 1.1 This document describes how user agents map HTML5.1 [[!HTML51]] elements and attributes to platform accessibility API roles, states and properties on a variety of platforms, based on the Core Accessibility API Mappings specification for user agents. This document is designed to leverage these core mappings for the HTML5.1 host language. In Working Drafts Editors' draft of HTML Accessibility API Mappings 1.0 Formal published version of HTML Accessibility API Mappings 1.0
SVG Accessibility API Mappings 1.1 This document describes how user agents maps SVG2 markup to platform accessibility APIs based on the Core Accessibility API Mappings specification for user agents. In Working Drafts Editors' draft of SVG Accessibility API Mappings 1.0 Formal published version of SVG Accessibility API Mappings 1.0
ARIA Support Resources
Requirements for Accessible Rich Internet Applications 1.1 This roadmap that describes the problem, what W3C specifications will be used to correct the problem, and the timeline for the new specifications. Work not yet begun Editors' draft of Requirements for Accessible Rich Internet Applications 1.1
WAI-ARIA Authoring Practices 1.1 Provides recommended approaches to create accessible Web content using WAI-ARIA roles, states, and properties to make widgets, navigation, and behaviors accessible. Also describes considerations that might not be evident to most implementors from the WAI-ARIA specification alone. in Working Drafts Editors' draft of WAI-ARIA Authoring Practices 1.1 Formal published version of WAI-ARIA Authoring Practices 1.1
Using WAI-ARIA in HTML Practical guide for developers on how to add accessibility information to HTML elements using the WAI-ARIA 1.1 in HTML 5.1, which especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies. In Working Drafts Editors' draft of Using WAI-ARIA in HTML Formal published version of Using WAI-ARIA in HTML
User Context Properties
User Context Properties 1.0 defines a set of preferences that users can choose to expose to web applications. Web applications can use this information to optimize the presentation without a requirement to target a specific device, operating system, or locale. Handover from IndieUI WG not yet completed

Also see the WAI-ARIA Overview Page. Editors' sources for the above specifications are maintained in the W3C ARIA GitHub repository. GitHub users can watch this repository and send pull requests.