Introduction to ARIA Specification and Practices
Jon Gunderson, Ph.D.
Division of Disability Resources and Educational Services
College of Applied Health Sciences
Slides
- Goals
- The Problem of Custom Widgets
- ARIA Contract with Browsers and Assistive Technologies
- Purpose of ARIA is Describe Semantics and Behavior
- Accessibility APIs and Browsers
- Accessible Rich Internet Applications (ARIA) 1.1
- HTML Living Standard
- HTML: main element
- HTML Accessibility API Mappings: roles and role restrictions
- Core Accessibility API Mappings for ARIA
- Accessible Name and Description Computation
- Summary of W3C Documents
- Tabindex and Keyboard Focus
- Accessible Name Calculation
- Accessible Description Calculation
- Other Descriptions: aria-details property
- Other Description: aria-invalid and aria-errormessage properties
- Checkbox Example: Overview
- Checkbox Example: Inaccessible
- Basic Screen Reader Commands
- Checkbox Example: Responding to the keyboard
- Checkbox Example: Adding ARIA role, checked state and accessible name
- Checkbox Example: Keyboard Focus and hover styling
- Checkbox Example: Synchronization of ARIA and visual states
- Checkbox Example: Summary of Accessibility Features
- Menu Button: ARIA Design Pattern
- Menu Button: Overview
- Menu Button: Inaccessible
- Menu Button: Keyboard Support
- Menu Button: Add ARIA roles, properties and states
- Menu Button: Keyboard Focus Styling
- Menu Button: High Contrast Support
- Navigation Links: Disclosure Pattern
- Using ARIA in HTML (Best Practices)
- None/Presentation Role
- Hiding Content Techniques
- Live Region Roles
- Live Region Attributes
- ARIA Authoring Practices 1.2
- ARIA Assistive Technology (AT) Community Group
- Open Source Tools
- Functional Accessibility Evaluator (FAE) 2.0
- AInspector Sidebar for Firefox
- Bookmarklets for Visualizing Accessibility Features
- Questions and Discussion