DRAFT Accessible Rich Internet Applications Working Group Charter

The mission of the Accessible Rich Internet Applications Working Group is to enhance the accessibility of web content through the development of supplemental attributes, including roles, states, and other properties, that can be applied to native host language elements and exposed via platform accessibility APIs.

Join the Accessible Rich Internet Applications Working Group.

This proposed charter is available on GitHub . Feel free to raise issues .

Charter Status See the group status page and detailed change history .
Start date 01 January 2027
End date 31 December 2028
Chairs
  • James Nurthen (Evinced Inc.)
  • Valerie Young (Igalia)
Team Contacts Daniel Montalvo (0.50 FTE )
Meeting Schedule Teleconferences: The Working Group and its Task Forces generally each hold weekly teleconferences, but this may vary over time according to agenda and preferences.
Face-to-face: The Working Group generally meets during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 2 per year.
See also this group calendar

Motivation and Background

The Accessible Rich Internet Application suite has consistently provided mechanisms to make rich internet applications and other complex web user interfaces accessible to people with disabilities.

The suite consists of:

The Working Group plans to continue developing these technical specifications to provide guidance for:

Scope

Out of Scope

The following features are out of scope, and will not be addressed by this Working group:

  • Technologies for which corresponding Accessibility API Mappings do not need to be defined

Deliverables

In order to maximize the likelihood of achieving the success criteria described below, the ARIA Working Group will follow a work flow designed to see each feature from its road map through to completion, with ARIA feature development, platform accessibility API mapping, implementation, testing , and authoring guidance taking place at the same time.

For deliverables marked as "Living Recommendation", the Working Group intends to publish a snapshot of each of the document as a W3C recommendation before the Charter period ends.

Updated document status is available on the group publication status page .

Draft state indicates the state of the deliverable at the time of the charter approval. Expected completion indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.

Normative Specifications

The Working Group will deliver the following W3C normative specifications:

Accessible Name and Description Computation 1.2 (Living Recommendation)

This document describes how user agents determine the names and descriptions of accessible objects from web content languages. This information is in turn exposed through accessibility APIs so that assistive technologies can identify these objects and present their names or descriptions to users. Documenting the algorithm through which names and descriptions are to be determined promotes interoperable exposure of these properties among different accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent.

Draft state: Working Draft

Expected completion: Q4 2028

Latest publication: 2026-05-29

Exclusion Draft: https://www.w3.org/TR/2019/WD-accname-1.2-20190711/
Exclusion period began on 2019-07-11 and ended on 2019-12-08.

Exclusion Draft Charter : Produced under Working Group Charter: https://www.w3.org/2018/11/aria-charter.html

Accessible Rich Internet Applications (WAI-ARIA) 1.3 (Living Recommendation)

Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and interoperability of web content and applications. These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup. This version adds features new since WAI-ARIA 1.1 [wai-aria-1.1] to improve interoperability with assistive technologies to form a more consistent accessibility model for [HTML] and [SVG2]. This specification complements both [HTML] and [SVG2].

Draft state: Working Draft

Expected completion: Q4 2028

Latest publication: 2026-06-04

Exclusion Draft: https://www.w3.org/TR/2024/WD-wai-aria-1.3-20240123/
Exclusion period began on 2024-01-23 and ended on 2024-06-21.

Exclusion Draft Charter : Produced under Working Group Charter: https://www.w3.org/2022/02/aria-charter

Core Accessibility API Mappings 1.2 (Living Recommendation)
This document describes how user agents should expose semantics of web content languages to accessibility APIs. This helps users with disabilities to obtain and interact with information using assistive technologies. 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.

Draft state:

Expected completion: Q4 2028

Latest publication: 2026-07-02

Exclusion Draft: https://www.w3.org/TR/2024/CR-core-aam-1.2-20241121/
Exclusion period began on 2024-11-21 and ended on 2025-01-20.

Exclusion Draft Charter : Produced under Working Group Charter: https://www.w3.org/2022/02/aria-charter

HTML Accessibility API Mappings 1.0 (Living Recommendation)

HTML Accessibility API Mappings (HTML-AAM) defines how user agents map HTML [HTML] elements and attributes to platform accessibility application programming interfaces (APIs). It leverages and extends the Core Accessibility API Mappings 1.2 and the Accessible Name and Description Computation 1.1 for use with the HTML host language. 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.

The HTML-AAM is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

Draft state: Working Draft

Expected completion: Q4 2028

Latest publication: 2026-07-10

Exclusion Draft: https://www.w3.org/TR/2015/WD-html-aam-1.0-20150407/
Exclusion period began on 2015-04-09 and ended on 2015-09-06.

Exclusion Draft Charter : Produced under Working Group Charter: https://www.w3.org/2013/09/html-charter

ARIA in HTML

This specification defines the authoring rules (author conformance requirements) for the use of Accessible Rich Internet Applications (WAI-ARIA) 1.1 and Digital Publishing WAI-ARIA Module 1.0 attributes on [HTML] elements. This specification's primary objective is to define requirements for use with conformance checking tools used by authors (i.e., web developers). These requirements will aid authors in their development of web content, including custom interfaces/widgets, that makes use of ARIA to complement or extend the features of the host language [HTML].

Latest publication: 2026-08-11

Tentative Deliverables

Depending on the incubation progress, interest from multiple implementers, and the consensus of the Group participants, the Working Group may adopt or update the following documents as Rec-track specifications:

Digital Publishing WAI-ARIA Module
@@@
Digital Publishing Accessibility API Mappings
@@@
Graphics Accessibility API Mappings
@@@
Graphics ARIA
@@@
SVG Accessibility API Mappings

Describes how user agents map SVG markup to platform accessibility APIs. When user agents support this specification, SVG authors can create accessible rich internet applications, including charts, graphs, and other drawings.

Draft state: Working Draft

Expected completion: Q4 2028

Latest publication: 2026-05-29

Exclusion Draft: https://www.w3.org/TR/2015/WD-svg-aam-1.0-20150226/
Exclusion period began on 2015-02-26 and ended on 2015-07-26.

Exclusion Draft Charter : Produced under Working Group Charter: http://www.w3.org/WAI/PF/charter201006

MathML Accessibility API Mappings

The MathML Accessibility API Mappings (MathML-AAM) specification defines how user agents map Mathematical Markup Language (MathML) [MathML3] to platform accessibility APIs. It extends the Core Accessibility API Mappings (CORE-AAM) specification [CORE-AAM-1.2].

This specification is intended for user agent developers responsible for MathML accessibility in their product. The goal of this specification is to maximize the accessibility of MathML content by ensuring each assistive technology receives MathML content with the roles, states, and properties it expects.

At the present time, this specification contains mappings for the subset of MathML contained in the MathML Core specification [MathML-Core]. The reason why is that this subset contains the elements and attributes from MathML which are exposed to assistive technologies via platform accessibility APIs.

The MathML-AAM is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

Draft state: Working Draft

Expected completion: Q4 2028

Latest publication: ======= href="https://www.w3.org/TR/2026/WD-mathml-aam-1.0-20260529/"> >>>>>>> upstream 2026-05-29

Exclusion Draft: https://www.w3.org/TR/2015/WD-mathml-aam-1.0-20150226/
Exclusion period began on 2015-02-26 and ended on 2015-07-26.

Exclusion Draft Charter : Produced under Working Group Charter: http://www.w3.org/WAI/PF/charter201006

PDF Accessibility API Mappings (Living Recommendation)

This specification will define how user agents map PDF elements and attributes to platform accessibility application programming interfaces (APIs).

Draft state: No draft

Expected completion: Q4 2028

AT Driver (Living Recommendation)

The AT-driver specification defines a protocol for introspection and remote control of assistive technology software.

Draft state: Editor's Draft

Expected completion: Q4 2028

CSS Accessibility API Mappings (Living Recommendation)

CSS Accessibility API Mappings ( CSS -AAM) defines how user agents map CSS pseudo-elements and properties to platform accessibility application programming interfaces ( APIs ) . It leverages and extends the Core Accessibility API Mappings 1.2 and the Accessible Name and Description Computation 1.2 for use with the CSS language. 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.

Draft state: Editor's Draft

Expected completion: Q4 2028

Other Deliverables

Other non-normative documents may be created such as:

  • ARIA Practices, to demonstrate how WAI-ARIA features can be used to comply with WAI-ARIA specifications;
  • Use case and requirement documents;
  • Test suite and implementation report for the specification;
  • Primer or Best Practice documents to support web developers when designing applications.

Timeline

  • January 2027: First teleconference
  • June 2027: First face-to-face meeting
  • March 2027: Selection of new features to work on the main ARIA specification
  • June 2027: Assessment of how new features may impact API mappings
  • September 2027: Assessment of potential new ARIA Practices examples to illustrate how new ARIA features could be used
  • March 2028: Call for Review of ARIA proposed amendments
  • June 2028: Downstream updates based on ARIA Horizontal review comments, including mappings, ARIA Practices examples, and AT tests
  • December 2028: ARIA Recommendation with incorporated amendments

Success Criteria

The normative documents produced by this Working Group fall into two categories: ARIA specifications and Accessibility API Mapping specifications.

In order to advance beyond Candidate Recommendation , each normative specification is expected to have at least two independent interoperable implementations of every feature defined in the specification, where interoperability can be verified by passing open test suites. In order to advance beyond Candidate Recommendation, each normative specification must have an open test suite of every feature defined in the specification.

There should be testing plans for each specification, starting from the earliest drafts.

To promote interoperability, all changes made to specifications in Candidate Recommendation or to features that have deployed implementations should have tests . Testing efforts should be conducted via the Web Platform Tests project.

Each specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and users.

For specifications of technologies that directly impact user experience, such as content technologies, as well as protocols and APIs which impact content: Each specification should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and recommendations for maximising accessibility in implementations. Because the main purpose of the ARIA suite is to improve accessibility of rich applications and other complex widgets, the accessibility considerations are spread across the specification and a dedicated section is not necessary.

This group is expected to be guided by the following documents:

Coordination

For all specifications, this Working Group will seek horizontal review for accessibility, internationalization, privacy, and security with the relevant Working and Interest Groups, and with the TAG . Invitation for review must be issued during each major standards-track document transition, including FPWD . The Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of each specification. The Working Group is advised to seek a review at least 3 months before first entering CR and is encouraged to proactively notify the horizontal review groups when major changes occur in a specification following a review.

Additional technical coordination with the following Groups will be made, per the W3C Process Document :

W3C Groups

Accessibility Guidelines Working Group
Work on HTML 5 and ARIA Techniques for WCAG 2.2 .
Accessible Platform Architectures Working Group
Collaborate on overall accessibility architectural aspects of ARIA.
Cascading Style Sheets (CSS) Working Group
Coordinate media queries support for context awareness. Provide requirements for future WAI-ARIA support. Coordinate on general CSS accessibility topics. Include CSS-related requirements in the newly proposed CSS-AAM specification.
Publishing Maintenance Working Group
Coordinate development of digital publishing roles and EPUB Accessibility.
Internationalization Working Group
Coordinate how to address accessibility and internationalization in W3C specs.
Technical Architecture Group
Confirm the ARIA relationship to various host languages is interoperable and forwards-compatible.
Privacy Working Group
Identify and resolve privacy implications of features of the technology that capture user environment information, particularly specific assistive technology being used, in order to customize the user experience.
SVG Working Group
Coordinate on graphics role module and SVG Accessibility API Mappings.

External Organizations

DAISY Consortium
Coordinate on publishing and math accessibility API mappings.
Coordinate on features that impact e-learning and testing.
WHATWG
Coordinating on integration of ARIA in HTML and Web Components.

Participation

To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants.

The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in Communication . The group also welcomes non-participants to make technical contributions for ongoing work, provided they agree to the terms of the W3C Patent Policy .

The Chairs should periodically look through the non-W3C-Member contributors to the Working Group and consider whether each one should be invited to participate as an Invited Expert . If a non-W3C-Member contributor would like to participate in meetings, they are encouraged to apply to be an Invited Expert .

Participants in the group are required (by the W3C Process ) to follow the W3C Code of Conduct .

Communication

Technical discussions for this Working Group are conducted in public : the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests. The meetings themselves are not open to public participation, however.

Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the Accessible Rich Internet Applications Working Group home page.

Most Accessible Rich Internet Applications Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.

This group primarily conducts its technical work on GitHub issues . The public is invited to review, discuss and contribute to this work.

The group may use a Member-only mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.

Decision Policy

This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 5.2.1, Consensus) . Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.

However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.

To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional. A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period from four working days to one week , depending on the chair's evaluation of the group consensus on the issue. If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.

All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs.

This charter is written in accordance with the W3C Process Document (Section 5.2.3, Deciding by Vote) and includes no voting procedures beyond what the Process Document requires.

Patent Policy

This Working Group operates under the W3C Patent Policy (Version of 15 May 2025). To promote the widest adoption of Web standards, W3C seeks to issue Web specifications that can be implemented, according to this policy, on a Royalty-Free basis. For more information about disclosure obligations for this group, please see the licensing information .

Licensing

This Working Group will use the W3C Software and Document license for all its deliverables.

About this Charter

This charter has been created according to section 3.4 of the Process Document . In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.

Charter History

Note: Display this table and update it when appropriate. Requirements for charter extension history are documented in the Charter Guidebook (section 4) .

The following table lists details of all changes from the initial charter, per the W3C Process Document (section 4.3, Advisory Committee Review of a Charter) :

Charter Period Start Date End Date Changes
Initial Charter 22 October 2015 31 July 2018 none
Charter Extension 6 September 2018 31 October 2018 none
Rechartered 8 November 2018 31 October 2021
  • Clarified mission to focus exclusively on WAI-ARIA and Accessibility API Mappings (AAMs);
  • Clarified dependency on other groups for several ARIA modules;
  • Updated Success Criteria to describe successful testing procedure for ARIA and AAMs;
  • Removed User Context as a deliverable; the evolution of it, Personalization Semantics; is being transferred to the APA Working Group ;
  • Produced annual dot-release publications of ARIA and supporting specifications beginning Q4 2019, with features prioritized according to the roadmap ;
  • Adopted a concrete workflow for feature acceptance to add predictability to timelines;
  • Clarified participation and communication procedures;
  • Added licensing section to specify the W3C Document license for Recommendation-track deliverables and the W3C Software and Document license for others;
  • Staff effort increased from .25 FTE to .4 FTE to provide additional support for project management, inter-group coordination on related ARIA specifications, and publication.
Charter Extension 19 November 2021 31 January 2022 none
Rechartered 7 February 2022 31 January 2024 Changes from the previous charter ( diff from previous charter ):
  • Switch to Evergreen for certain specs.
New co-chair 13 April 2022 Valerie Young appointed as co-chair , replacing Joanmarie Diggs who stepped down in September 2021.
Charter extension 18 December 2023 31 July 2024
Charter Extension 1 August 2024 31 December 2024
Rechartered 12 December 2024 1 January 2027
  • All specifications marked as "Living Recommendations", except for Graphics-ARIA and Graphics-AAM, but all will be published at least once to REC during the new Charter period
  • Added PDF-AAM to the list of deliverables
  • Marked SVG-AAM as a joint deliverable with the SVG Working Group
  • Clarified scope for HTML-ARIA
Charter Refinement September 2026 October 2026
  • Restructure deliverables: normative (actively maintained) and tentative (only adopted if enough interest and implementation experience)
  • Added AT driver specification
  • Added CSS AAM specification
  • Clarified scope to better signal testing across the accessibility stack, including browser, accessibility platform APIs, and assistive technology

Change log

Changes to this document are documented in this section.