-
Notifications
You must be signed in to change notification settings - Fork 742
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
WCAG SC 2.5.3 failures not identified by axe DevTools #4381
Comments
Thanks for the issue. So the |
I can see from the docs that we claim it's enabled in the browser extension, but this is both correct and incorrect. It was enabled in the axe coconut extension (when that was still a thing), but it is not enabled in the devtools extension. We'll update the docs to make that more clear. |
Thank you @straker! That makes much more sense now. |
Product
axe Extension
Product Version
Extension: v4.77.1 axe-core: v4.8.4
Latest Version
Issue Description
I was testing some content for WCAG 2.1 SC 2.5.3 and noticed that my example wasn't being flagged by axe DevTools. To confirm the issue, I created a page to test this in a CodeSandbox using all the Fail examples for the rule. I ran the extension on the example page and got 0 issues, except for 2 issues caused by the CodeSandbox injected button.
To make sure the button wasn't the cause, I created a page locally to test it and got the same result, no issues with the page.
Expectation
label-content-name-mismatch rule fails on 3 separate elements
Actual
0 issues found
How to Reproduce
For future context, in case the CodeSandbox gets deleted, here is the used code:
Sample page that should produce WCAG 2.5.3 failures
Additional context
Below are 2 screenshots, with alt text, of the 0 issues in axe DevTools and a successful failure identification by a different accessibility checker:
The text was updated successfully, but these errors were encountered: