-
Notifications
You must be signed in to change notification settings - Fork 345
Scope
Matt King edited this page Sep 23, 2019
·
1 revision
The primary deliverable of the ARIA Practices project is a W3C Note that serves as a guide for using ARIA to build accessible rich internet applications. The Note is also known as the "APG," which stands for either "ARIA Practices Guide" or "Authoring Practices Guide."
The planned scope of the APG includes:
- Examples: Cannonical reference implementations of common web GUI components that employ ARIA.
- Guidance: Explanations of the purposes and limitations of ARIA roles, states, and properties.
- How-to's: Approaches to specific aspects of designing and developing accessible rich internet applications, such as using ARIA landmarks and developing keyboard interfaces.
- A regression testing framework for the reference examples included in the APG.
- A framework for assessing and web site for reporting on how well assistive technologies support APG reference implementations of web GUI components.
Role Category | Count | Coverage |
---|---|---|
Widget | 20 | 20: Explained in design patterns and demonstrated in examples. See Design Patterns Development Status |
Document Structure | 26 | TBD |
Landmark | 8 | 8: Explained and demonstrated in Landmark Regions section. |
Live Region | 5 | 5: Explained in guidance section on live region attributes. See issue 78. |
Window | 2 | 2: Explained and demonstrated in design patterns. See Design Patterns Development Status |
Total | 69 | 35 + TBD in Structure |
Note: The 12 ARIA 1.1 abstract roles are omitted because they MUST not be used by authors.
ARIA 1.1 includes 48 states and properties, 46 of which are included in the initial release scope. See the development status of guidance sections.
Two excluded attributes:
- aria-dropeffect property (deprecated)
- aria-grabbed state (deprecated)
- ARIA basics: quick start section covering must-know basics.
- Accessible name calculation in the labeling and describing guidance section.
- How-to Section: Developing Keyboard Interfaces (Issue 220)
- How-to Section: Developing Custom Widgets (Issue 73)
- How-to section: Displaying Images and Symbols That Represent Widget States and Properties (Issue 274)
- Appendix explaining screen reader modes (Issue 193)
- Appendix describing ARIA background topics, e.g., why ARIA is necessary. (Issue 84)
- Home
- About the APG TF Work
- Contributing
- Meetings
- Management and Operations Documentation
- Publication Change Logs