According to the Headers test guidance in Assessment, "If the page uses headings, an automated check will fail if the page does not have exactly one top-level heading."
However, a page that doesn't have exactly 1 top-level heading when it uses headings isn't failing a corresponding automated check.
To Reproduce
Steps to reproduce the behavior:
Please provide a reproduction of the bug in a codepen, if possible. Here鈥檚 how
https://codepen.io/anon/pen/eovjqJ
One of two:
If applicable, add screenshots to help explain your problem.
If asked, will you be willing to submit a PR to fix this bug? Yes
Did you search for similar issues in our github issues or on stackoverflow Yes
Add any other context about the problem here.
This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!
to fix: need to remove the note in headings test guidance. the rule mentioned is best practice.
Fixed.
Thanks, @Shobhit1!
The sentence, "If the page uses headings, an automated check will fail if the page does not have exactly one top-level heading.", is no longer in the Assessment section for Headings.
But, this sentence, "Use exactly one top-level heading. (WCAG 1.3.1)" is still on the "Guidance for Headings" page. Shouldn't the "WCAG 1.3.1" in parentheses be replaced with "best practice"?
Accessibility Insights for Web
Version 2.16.0 | Powered by axe-core 3.5.1
hi @gatosocal great point! we have filed a bug #2444 to track this change.
Most helpful comment
Fixed.