| CARVIEW |
[contents]
Accessible Rich Internet Applications (WAI-ARIA) 1.0
W3C Recommendation 20 March 2014
- This version:
- https://www.w3.org/TR/2014/REC-wai-aria-20140320/
- Latest version:
- https://www.w3.org/TR/wai-aria/
- Previous version:
- https://www.w3.org/TR/2014/PR-wai-aria-20140206/
- Editors:
- James Craig, Apple Inc.
Michael Cooper, W3C - Previous Editors:
- Lisa Pappas, Society for Technical Communication
Rich Schwerdtfeger, IBM
Lisa Seeman, UB Access
Please check the errata for any errors or issues reported since publication.
This document is also available as a single page version.
See also translations.
Copyright © 2008-2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.
Abstract
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 document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.
Status of this Document
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.
This is the WAI-ARIA 1.0 W3C Recommendation from the Protocols & Formats Working Group of the Web Accessibility Initiative. The Working Group created an implementation report that shows the exit criteria have been met. The Director approved transition to Recommendation after reviewing this report and after Advisory Committee vote which unanimously supported publication. Some editorial changes have been made since the Proposed Recommendation: removing suggestions of "RDF ID reference", changing the spelling of "programming" to "programing", correcting the spelling of "assistive", and updating some references to latest versions.
This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.
To comment on this document, send email to public-pfwg-comments@w3.org (comment archive). Comments received on the WAI-ARIA 1.0 Recommendation cannot result in changes to this version of the specification, but may be addressed in errata or future versions of WAI-ARIA. The Working Group may not make formal responses to comments but future work undertaken by the Working Group may address comments received on this document.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
The disclosure obligations of the Participants of this group are described in the charter.
Table of Contents
- Abstract
- Status of This Document
- 1. Introduction
- 2. Using WAI-ARIA
- 2.1. WAI-ARIA Roles
- 2.2. WAI-ARIA States and Properties
- 2.3. Managing Focus
- 3. Normative Requirements for WAI-ARIA
- 4. Important Terms
- 5. The Roles Model
- 5.1. Relationships Between Concepts
- 5.1.1. Superclass Role
- 5.1.2. Subclass Roles
- 5.1.3. Related Concepts
- 5.1.4. Base Concept
- 5.2. Characteristics of Roles
- 5.2.1. Abstract Roles
- 5.2.2. Required States and Properties
- 5.2.3. Supported States and Properties
- 5.2.4. Inherited States and Properties
- 5.2.5. Required Owned Elements
- 5.2.6. Required Context Role
- 5.2.7. Accessible Name Calculation
- 5.2.8. Presentational Children
- 5.2.9. Implicit Value for Role
- 5.3. Categorization of Roles
- 5.3.1. Abstract Roles
- 5.3.2. Widget Roles
- 5.3.3. Document Structure
- 5.3.4. Landmark Roles
- 5.4. Definition of Roles
- 5.1. Relationships Between Concepts
- 6. Supported States and Properties
- 6.1. Clarification of States versus Properties
- 6.2. Characteristics of States and Properties
- 6.2.1. Related Concepts
- 6.2.2. Used in Roles
- 6.2.3. Inherits into Roles
- 6.2.4. Value
- 6.3. Values for States and Properties
- 6.4. Global States and Properties
- 6.5. Taxonomy of WAI-ARIA States and Properties
- 6.5.1. Widget Attributes
- 6.5.2. Live Region Attributes
- 6.5.3. Drag-and-Drop Attributes
- 6.5.4. Relationship Attributes
- 6.6. Definitions of States and Properties (all aria-* attributes)
- 7. Implementation in Host Languages
- 8. Conformance
- 9. References
- 10. Appendices
- 10.1. Schemata
- 10.1.1. Roles Implementation
- 10.1.2. WAI-ARIA Attributes Module
- 10.1.3. XHTML plus WAI-ARIA DTD
- 10.1.4. SGML Open Catalog Entry for XHTML+ARIA
- 10.1.5. WAI-ARIA Attributes XML Schema Module
- 10.1.6. HTML 4.01 plus WAI-ARIA DTD
- 10.2. Mapping WAI-ARIA Value types to languages
- 10.3. WAI-ARIA Role, State, and Property Quick Reference
- 10.4. Acknowledgments
- 10.1. Schemata