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
There's a small remaining a11y issue on the current /about/leadership page. We should not be using role="button" on a landmark like <article> content - instead it should just be a regular <div>. It seems OK that all descendants are declared as presentational when the role is applied, as only the person's name is read aloud which seems OK.
We should also add aria-controls and aria-expanded, to associate control with the modal element.
Description
There's a small remaining a11y issue on the current
/about/leadership
page. We should not be usingrole="button"
on a landmark like<article>
content - instead it should just be a regular<div>
. It seems OK that all descendants are declared as presentational when the role is applied, as only the person's name is read aloud which seems OK.We should also add
aria-controls
andaria-expanded
, to associate control with the modal element.axe-core found 1 violation
Failed
Learn more
aria-allowed-role
Best practice
Ensure role attribute has an appropriate value for the element
minor
Issue Tags: cat.aria best-practice
<br>#laura-chambers<br>
Element source
<br><article id="laura-chambers" class="vcard has-bio" itemscope="" itemtype="http://schema.org/Person" role="button" tabindex="0"><br>
* ARIA role button is not allowed for given element
The text was updated successfully, but these errors were encountered: