A screen reader needs to know what a piece of a page is, not only what it looks like. The ARIA role none describes removes an element's presentational role where allowed.
What this role means
Removes an element's presentational role where allowed.
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 none in a real page
<ul role="none">
<li><a href="#one">One</a></li>
</ul>Read the example
Look for role="none" in the example. The role helps assistive technology classify the content. Read the surrounding text and labels too: those give the control or region its useful name.
Do not remove list semantics without a clear reason; role="none" and role="presentation" are synonyms.
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.
In an accessibility inspector, compare the accessible role and name with the visible content. The important goal is that both keyboard users and screen-reader users can understand the page.
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="none"without checking whether an ordinary HTML element already supplies the right semantics. - Do not remove list semantics without a clear reason; role="none" and role="presentation" are synonyms.
- Confusing the role announced by a screen reader with the behavior that the browser implements.
Key Takeaways
noneis related to removes an element's presentational role where allowed.- Do not remove list semantics without a clear reason; role="none" and role="presentation" are synonyms.
- Native HTML is the first choice; ARIA should clarify meaning, not replace working HTML.