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



