presentation-role-conflict
Web validation
role="none" or role="presentation" should not regain semantics in the accessibility tree.The role="none" and role="presentation" values tell browsers to remove an element's semantics from the accessibility tree, so it is treated as plain layout.
If the element is focusable or carries a non-empty global ARIA attribute, the override is ignored. The element's original role returns to the tree, which can confuse assistive technology and mislead users.
Pass Patterns
List item with a presentational role
The role="none" removes the item's semantics, and with no focus or global ARIA it stays out of the tree.
<li role="none"></li>List item using role presentation
The role="presentation" value does the same, keeping a layout-only item out of the tree.
<li role="presentation"></li>Fail Patterns
Global ARIA attribute on a presentational element
The non-empty aria-label is a global ARIA attribute, so the element returns to the tree with its original role.
<li role="none" aria-label="Item one"></li>Focusable element with a presentational role
A <button> is natively focusable, so it keeps its button role despite role="none".
<button role="none"></button>ACT Rules
Try It Yourself
Inspecting the browser dev-tools
- Right-click the element and choose Inspect.
- Open the Accessibility panel.
- Check how the element is exposed in the accessibility tree.
Expected results: The element is absent from the accessibility tree, or shown as ignored.
Actual results: The element appears in the tree with its original role.
Using a screen reader
New to screen reader testing, or need a refresher?
Review this article first: Practical guides for using screen readers
- Turn on a screen reader.
- Navigate through the content, including with the Tab key.
- Check whether the presentational element is announced or focused.
Expected results: The element is skipped entirely.
Actual results: The element is announced or receives focus.
FAQ
Why is this rule considered a best practice?
Using role="none" or role="presentation" is a reliable way to keep decorative or structural elements out of the accessibility tree. No single WCAG success criterion governs this conflict, but honoring the override keeps the tree clean and stops screen readers from announcing content with no user benefit.
Why is this issue marked as Minor?
When the conflict happens, users may hear or focus an unexpected element, but core functionality usually stays intact. The impact is noticeable yet limited, so the issue is minor rather than serious or critical.