liveBook · Manning

WAI-ARIA

As explained in Architecting Accessibility

ARIA is a W3C standard for adding accessibility semantics and interaction-state information to web content and user interface widgets.

A custom tab interface can become a barrier when assistive technologies cannot identify its structure or state. WAI-ARIA adds roles, states, and properties to HTML so assistive technologies can interpret custom components. section 2.5.2

Start with semantic HTML: it provides substantial accessibility without extra attributes. Use ARIA when native semantics fall short, and remember that describing a component does not implement its expected behavior. section 2.0 section 2.5.2

Tabbed interface

A tablist can contain tabs with selection states and links to their panels. The implementation must also manage expected keyboard interaction and focus; test it with a keyboard and screen reader. section 2.5.2

How Architecting Accessibility covers it

How deep it goes
Defines roles, states, and properties, then demonstrates tab relationships and selection; it does not supply component behavior.
Examples
Uses tabbed interfaces and names modal dialogs, menubars, data grids, and carousels as custom-widget examples.
What you can do after
Build custom components by following APG patterns, implementing expected behavior, and testing with a keyboard and screen reader.
How it connects
Connects semantic HTML, assistive technologies, screen readers, JavaScript, and keyboard interaction.

Also explained in

Compare how 4 books explain WAI-ARIA →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting Accessibility. The section links point to the parts of the book it draws on.