Web Accessibility and 508 compliance
Resources of the "Accessible Web Mapping Apps: ARIA, WCAG and 508 Compliance" presentation given at the Esri Developer Summit 2016.
Introduction
Page | Description |
---|---|
sample-1.01.html | Default behavior |
sample-1.02.html | Using the tabindex attribute |
sample-1.03.html | Using the tabindex attribute for lists: ko |
sample-1.04.html | Using the tabindex attribute for lists: ok |
sample-1.05.html | Using the tabindex attribute to exclude elements |
sample-1.06.html | Using the tabindex attribute to specify unnatural order (not recommended) |
sample-1.07.html | Tabindex is not inherited |
sample-2.01.html | Alternative text for images is mandatory and can take multiple forms |
sample-2.02.html | Accessible actions |
sample-3.01.html | Using JavaScript to make content accessible |
sample-3.02.html | Using JavaScript to capture navigation event |
sample-3.03.html | Using JavaScript to choose the next element to be focused |
sample-3.04.html | Using JavaScript to make content accessible and choose the next element to be focused |
sample-4.01.html | Removing the focus outline when using the mouse |
sample-5.01.html | Capturing navigation using JavaScript focus event |
sample-6.01.html | Using WAI-ARIA |
sample-7.01.html | Setting a map alternative text |
Example of accessible apps
Tools
- ChromeVox
- Chrome Accessibility Developer Tools
- web accessibility evaluation tool
- AChecker: Web Accessibility Checker
- W3C Markup Validation Service
Checklist
Articles
- Wikipedia page about Web accessibility
- Web accessibility in mind: Introduction
- Web accessibility in mind: Keyboard Accessibility
- Web accessibility in mind: Designing for Screen Reader Compatibility
- Web accessibility in mind: Alternative Text
- W3C WAI-ARIA Overview
- Introduction to WAI-ARIA
- How I Audit a Website for Accessibility
- Reframing Accessibility for the Web
- The web accessibility basics
- The A11Y Project
- ARIA Examples
- ally.js