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
Remove the explicit role attribute on HTML elements that have the same role implicitly, including:
the <header> element in the Header component, which has a banner role
the <footer> element in the Footer component, which has a contentinfo role
the <nav> element in the Pagination component, which has a navigation role
In some places we include an explicit group role on <fieldset> elements (e.g. the date input) to ensure that JAWS announces the accessible description – we should leave this in place unless we're able to do further investigation and understand whether this is still needed.
What
Remove the explicit
role
attribute on HTML elements that have the same role implicitly, including:<header>
element in the Header component, which has abanner
role<footer>
element in the Footer component, which has acontentinfo
role<nav>
element in the Pagination component, which has anavigation
roleIn some places we include an explicit
group
role on<fieldset>
elements (e.g. the date input) to ensure that JAWS announces the accessible description – we should leave this in place unless we're able to do further investigation and understand whether this is still needed.Update our HTML validation rules accordingly.
Why
These have historically been set because older browsers (noteably Internet Explorer) do not map these implicit roles correctly.
As our browser support model has evolved, we can now remove these implicit roles.
Who needs to work on this
Developers
Who needs to review this
Developers, Accessibility Specialist
Done when
<fieldset>
)The text was updated successfully, but these errors were encountered: