presentation-role-conflict

Ensure that elements marked for removal from the accessibility tree are indeed removed.

Description

When role="none" or role="presentation" are used, they should interfere with an element’s implicit functionality or with other specified global ARIA attributes.

Why is it important?

When utilizing the role="presentation" or role="none" attributes, it is intended for assistive technologies to disregard the default role of an element while keeping its content visible to users. Nonetheless, there are situations where HTML elements may not adhere to the role="none" or role="presentation" instructions. This typically arises when an element possesses inherent behaviors or explicit properties that hold significance for accessibility and clash with the specified presentational roles. Consequently, the roles are overlooked, allowing users to interact with the element as if the specified role was absent.

Examples

• Success:

  • An ordered list with role="presentation" attribute and no tabindex or global ARIA attributes.

• Failure:

  • An ordered list with role="presentation" and tabindex="0" attributes.

How to fix?

For every element with role="none" or role="presentation" attribute, ensure -

1. It does not have a global ARIA attribute
2. It is not focusable

Tags

cat.aria, best-practice

References

• Deque University: presentation-role-conflict