REACH
Practical accessibility engineering.
Learn how semantics, names, keyboard behavior, and the accessibility tree fit together. Build, inspect, and verify interfaces—not sprinkle attributes.
Engineering, not checklists
Every chapter treats accessibility as a quality attribute of the interface: meaning, interaction, and what assistive technologies actually receive.
Prefer native HTML when it already provides the required semantics and behavior. Use WAI-ARIA only when native HTML cannot express what you need—and verify the result.
Introduction
Conceptual grounding for accessibility engineering.
WCAG
Conformance model and practical success-criteria interpretation.
Accessibility Tree
How browsers expose semantics to assistive technologies.
- Accessibility TreeHow browsers transform DOM semantics into AT-consumable data.
- DOM vs Accessibility TreeWhat is preserved, ignored, or remapped between trees.
- Roles, Names & StatesCore accessibility node properties and how they are computed.
- Browser & Accessibility APIsPlatform APIs that connect browsers to assistive technologies.
WAI-ARIA
Roles, states, properties, and naming when native HTML is insufficient.
- WAI-ARIA FundamentalsWhen ARIA is necessary and how to apply it without damaging accessibility.
- Accessible NamesName computation and labeling strategies.
- RolesARIA roles and when they should override or supplement native semantics.
- States & PropertiesKeeping ARIA state synchronized with UI behavior.
- Authoring PracticesAPG guidance for correct ARIA widget patterns.
Accessibility in Practice
Practical barriers and engineering responses across interaction surfaces.
- VisualContrast, alternatives, magnification, and visual presentation.
- KeyboardKeyboard operability, focus order, visibility, and management.
- AudioCaptions, transcripts, and equivalents for auditory information.
- MobilityTarget size, pointer alternatives, and motor-access patterns.
- Cognitive & OtherClarity, consistency, and barriers beyond vision, hearing, and motor input.
Screen Readers
Operational models and practical screen-reader testing.
- Screen Reader FundamentalsBrowse mode, forms mode, and announcement patterns.
- VoiceOverVoiceOver expectations on macOS and iOS for web content.
- NVDANVDA expectations for Windows web testing.
- JAWSJAWS expectations and differences from other screen readers.
- Screen Reader TestingPractical SR smoke tests in engineering workflows.
Testing & Engineering
Testing strategy, audits, debugging, and engineering process.
- Accessibility TestingLayered accessibility testing in engineering workflows.
- Automated TestingWhat automation catches and what it cannot.
- Keyboard TestingManual keyboard validation techniques.
- Accessibility AuditsPlanning and executing accessibility audits.
- Debugging AccessibilityUsing accessibility trees and AT to diagnose defects.
- Accessibility in Code ReviewReview checklists and ownership in pull requests.
- Accessibility in CI/CDQuality gates and continuous accessibility checks.
See, understand, inspect
Pages combine short fundamentals with visual anatomy, interactive demos, and accessibility-tree inspection—so you can scan the idea, then dig into the engineering contract.
Verify the fix
Keyboard behavior, exposed names and roles, and assistive-technology smoke tests are part of the curriculum—not an afterthought at the end of a release.