On this page
Browser & Accessibility APIs
Browser responsibility#
Interactive demo
Accessibility stack
Accessibility stack
Authors define structure, meaning, and behavior in markup and script.
Native elements already carry roles and interaction contracts.
<button type="button">Save</button>A conceptual model—not a claim that every browser implements an identical pipeline.
AT generally does not consume arbitrary pixels as the primary interface model. It receives structured accessibility information.
Platform APIs#
Flow
Conceptual path
- Web semantics (HTML / ARIA)
- Browser accessibility tree
- OS accessibility API
- Assistive technology
- User
API names differ by platform (for example UI Automation, AXAPI, AT-SPI).
Engineer takeaway
- Correct HTML/ARIA is how you feed the API chain
- Broken names/roles/states fail before any screen reader setting
- Platform details vary; the authoring contract stays the same