WAI-ARIA

This repository maintains specifications and related publications for the Accessible Rich Internet Applications suite of technologies. This is developed by the ARIA Working Group. The W3C staff contact is Daniel Montalvo. Please do not provide commit access to this repository without coordination. This repository contains the main deliverable of the ARIA Working Group, Accessible Rich Internet Applications (ARIA), and should be used for issues related to the ARIA spec as well as issues that involve both the ARIA spec in conjunction with other specifications maintained by the ARIA working group. All other specifications maintained by ARIA can be found in this repository as well, however, we have separate issue tracking repos for these separate specifications. In addition to these specifications, there are other deliverables as specified in the ARIA Charter. Please file issues in the repository specific to the specification or deliverable to which the issue applies. Running list of browser accessibility heuristics that are not specified or are partially specified. Please review the ARIA Process Document for information about how the working group tracks issues and pull request. Only formally designated editors have commit access to this repository. Editors are designated by the Working Group Chair and make the following commitments: Execute the consensus of the Working Group regardless of personal opinion; Seek Working Group review of substantive technical issues; In good faith separate editorial issues, which may be addressed without explicit review requests, from substantive issues which require review; Follow the W3C Manual of Style and the Chicago Manual of Style; Follow W3C Editors guidelines. Issues can be assigned to people who are members of the ARIA Contributors team. If you are an ARIA Working Group participant and need access, ask Daniel Montalvo. When a pull request is accepted by the Working Group, an editor will integrate changes. Pull requests and issues that are accepted by the working group will be merged into the source documents and the commenter will receive a notification from GitHub that the pull request was accepted. The ARIA spec allows easy generation of links to roles, states, and properties, with the right link and styling. Simply enclose the name of the role, state, or property in the following elements: Note: this only works in the ARIA spec. Other specs must use cross references as defined below. Links with special class attributes allow cross references into other specs in the suite, which are transformed by the script to be the appropriate target for the given publication, so editors' drafts point to other editors' drafts, and TR publications point to other TR publications. This requires some configuration options in the respecConfig and use of special class attributes. First, for each document that might be referenced, a set of URLs is provided. The URLs are indexed by values of the respec spec status, which ensures the target at the same level of maturity as the current version is used. A typical set of values for the main ARIA spec is: Note that even though some of these URIs are redundant, they must all be defined to work in all circumstances. If a document is a First Public Working Draft but the FPWD variant isn't defined, there won't be a match with the specStatus and the links won't work. If you want to target the main spec, leave the href blank (but present). If you want other classes on the link, e.g., for styling, provide them after the script-hooking class, for instance class="specref role-reference" . When referencing other W3C specifications such as HTML and DOM , we can take advantage of ReSpec’s xref feature to automatically generate canonical links in context. If you wish to reference a spec that is not included in ARIA’s default xref configuration, you must specify it with a data-cite attribute. For example, the following markup references “nullable type” and “DOMS