You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Native semantic HTML elements currently have redundant ARIA roles. For example, the <nav> element has role="navigation, the <footer> element has role="contentinfo", and so on.
If you can use a native HTML element or attribute with the semantics and behaviour you require already built in, instead of re-purposing an element and adding an ARIA role, state or property to make it accessible, then do so.
Reported by SODA
Violation: Avoid inappropriate use of ARIA roles, states, and properties
Severity: Minor
[Issue]
There are elements on the page that have assigned roles but already have implicit ARIA roles. These are redundant and should be removed.
The navigation role is unnecessary for element nav.
The form role is unnecessary for element form.
The banner role is unnecessary for element header.
The main role is unnecessary for element main.
The contentinfo role is unnecessary for element footer.
[User Impact]
When ARIA attributes (state, roles, and properties) are inappropriately used, assistive technology may not correctly function as expected.
[Recommendation]
Remove the role="navigation" from the nav element, and the role="contentinfo" from the footer element. Be sure and also remove any other redundant roles from other pages.
Current behavior
Native semantic HTML elements currently have redundant ARIA roles. For example, the
<nav>
element hasrole="navigation
, the<footer>
element hasrole="contentinfo"
, and so on.Steps to reproduce
Example page: Spotlight Accessibility for SODA.
Possible solution
WCAG Level A: See First rule of ARIA use.
Reported by SODA
The text was updated successfully, but these errors were encountered: