-
Notifications
You must be signed in to change notification settings - Fork 779
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aria-roles standards object contains many roles that are classified as widgets but are not #4371
Comments
An example where this is creating a false positive is on https://www.hep.ca/horse-insurance/. The close button the cookie banner is 15x15. Axe is failing this for being too close to the to the cookie banner, which has tabindex=0 and role=alert. |
I'm playing with getting everything synced to the spec now to see where that gets us |
Too many aria roles were set to widget or otherwise were incorrect, added a comment source for where I got my information for which abstract roles were the type of which roles Refs: #4371
- learned sometimes we intentionally spec change - added `window` as a supported type, and `composite` which was missing from the readme - undid my change to `isWidgetType` Refs: #4371
test change was only for data tables, but we didn't want to keep that type change Refs: #4371
add `window` to has-widget-role, renamed Refs: #4371
better pass/fail english message, removed outdated translations Refs: #4371
Too many aria roles were set to widget or otherwise were incorrect, added a comment source for where I got my information for which abstract roles were the type of other aria roles Fix: #4371
Role such as
tabpanel
,timer
,alert
, etc. are marked as widgets but they shouldn't be. This problem is contributing to #4360 as each example uses a tabpanel with many overlapping child nodes.We'll need to investigate the ramifications of changing these to their correct types before we make the change.
The text was updated successfully, but these errors were encountered: