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
EAAC should ignore blocks that are display: none, visibility: hidden, and/or aria-hidden="true. It used to work that way, up to the Oct 1, 2024 deployment. But after that (starting with the Nov 6, 2024 ruleset), it scans those blocks.
This leads to spurious error messages such as:
Multiple elements with "region" landmarks within the same parent region are not distinguished from one another because they have the same "data table toolbar" label
Steps to reproduce
Unlike #2103 this happens in both Node and on Chrome. A minimal test case is:
<htmllang="en"><head><title>Test that display:none blocks are ignored</title></head><body><main><sectionaria-label="my section">
This section is visible.
</section><sectionaria-label="my section" style="display: none">
This section has the same label but is display:none, so there shouldn't be an error.
</section></main></body></html>
The problem also happens though with visibility: hidden and aria-hidden="true".
The text was updated successfully, but these errors were encountered:
wkeese
changed the title
[BUG]: Accessibility checker no longer ignores display:none blocks
[BUG]: Accessibility checker no longer ignores hidden blocks
Nov 25, 2024
wkeese
changed the title
[BUG]: Accessibility checker no longer ignores hidden blocks
[BUG]: Accessibility checker no longer ignores hidden blocks (regression)
Nov 26, 2024
Project
accessibility-checker-engine
Browser
Chrome
Operating system
MacOS
Description
EAAC should ignore blocks that are
display: none
,visibility: hidden
, and/oraria-hidden="true
. It used to work that way, up to the Oct 1, 2024 deployment. But after that (starting with the Nov 6, 2024 ruleset), it scans those blocks.This leads to spurious error messages such as:
Steps to reproduce
Unlike #2103 this happens in both Node and on Chrome. A minimal test case is:
The problem also happens though with
visibility: hidden
andaria-hidden="true"
.The text was updated successfully, but these errors were encountered: