Graphic Version 800x600
- ARIA and Web 2.0 Accessibility
- Web 2.0 Paradigm Shift
- What is W3C ARIA (Accessible Rich Internet Applications)?
- Accessibility API defines a standard contract between an application component and an assistive technology
- In any object-based accessibility architecture, Assistive Technologies (AT)'s communicate with all objects to render an accessible view
- Problem Analysis shows opportunity for richer accessibility
- Repurposed HTML lacks semantics and ability to give focus example: menu wanna be
- Information as seen by Assistive Technology today (if the user could get to Top Stories)
- Dependence on excessive tabbing makes keyboard access unusable
- Filling the Gaps
- Full ARIA Role Taxonomy – UML
- W3C ARIA States and Properties
- Role navigation Landmarks Facilitate Portal Navigation
- New Information as seen by Assistive Technology
- Web 2.0/ARIA Navigation Paradigm Shift Navigation
- New ARIA landmarks from XHTML 1.X
- Web application roles and regional landmarks
- Tab container with expandable tab panels to hide real estate
- Challenges for ATs, Developers, and Users
- Yahoo Web 2.0 Style Mail beta
- Keyboard Navigation (managing focus) basics
- Author-managed arrow key navigation within widgets
- Menu created using active descendent for focus
- General steps for building an accessible ARIA widget
- Changes in ARIA – easier for developers
- Tree Widget Usability Comparison
- Demo
- Business reason for using ARIA over basic Web accessibility compliance
- JavaScript/CSS adoption impacts compliance strategy while standards/legislation adapt
- CSS and Compliance Issues
- CSS and Compliance Solution
- Dojo - An Accessible JavaScript Toolkit
- Dojo 1.0 Core Widget Set (dijit) Accessibility
- Dojo Keyboard Implementation
- Dojo Low Vision Implementation
- Assembling the Parts to Help Developer and User
- Mashups – the Next Challenge
- Summary
- Thank you
- References (1 of 2)
- References (2 of 2)
- References
- Demo
- Use ARIA States and Properties to trigger CSS visualizations