A screen reader needs to know what a piece of a page is, not only what it looks like. The ARIA role tab describes one selectable tab in a tabbed interface.
What this role means
One selectable tab in a tabbed interface.
ARIA roles add meaning to the accessibility tree. They do not automatically make something clickable, move keyboard focus or build an interface. Those behaviors come from native HTML controls or from correctly implemented JavaScript.
See tab in a real page
<nav aria-label="Lesson sections">
<a href="#overview">Overview</a>
<a href="#examples">Examples</a>
</nav>Read the example
You may notice that the snippet does not write role="tab" explicitly. That is intentional: the native element already communicates this meaning, so repeating the role would add unnecessary markup.
A true tab widget requires tablist/tabpanel relationships and arrow-key interaction; links are not equivalent tabs.
When to use it
Start with native HTML whenever possible. Add ARIA only when it provides missing meaning for an interface that you cannot build with the appropriate native element.
For custom interactive widgets, test with the keyboard and a screen reader. Depending on the pattern, you may need Enter or Space activation, arrow-key handling, state changes, focus movement and a clear accessible name. Assigning the role alone implements none of these.
Try it yourself
Put the example on a practice page and inspect it using your browser accessibility panel. If it includes interactive controls, reach them with Tab and check whether they work without a mouse. Explain whether the semantics come from native HTML or an explicit ARIA role.
Common Beginner Mistakes
- Adding
role="tab"without checking whether an ordinary HTML element already supplies the right semantics. - A true tab widget requires tablist/tabpanel relationships and arrow-key interaction; links are not equivalent tabs.
- Confusing the role announced by a screen reader with the behavior that the browser implements.
Key Takeaways
tabis related to one selectable tab in a tabbed interface.- A true tab widget requires tablist/tabpanel relationships and arrow-key interaction; links are not equivalent tabs.
- Native HTML is the first choice; ARIA should clarify meaning, not replace working HTML.