F1 update - Updated procedure and clarified scope #4547
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
patrickhlauke
approved these changes
Aug 19, 2025
Contributor
|
Discussed on TF call 9/19/2025 and moved to Ready for Approval. |
bruce-usab
approved these changes
Sep 19, 2025
Contributor
bruce-usab
left a comment
bruce-usab
left a comment
There was a problem hiding this comment.
Preview diff for Technique F1: Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS
scottaohara
approved these changes
Oct 2, 2025
brianelton
reviewed
Oct 3, 2025
Changed "any options is" to "any option is"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #4215
With the goal of closing #4215 and prevent people from removing all styles, which can (and probably does) lead to invalid testing, I've clarified also the scope of the procedure.
The key clarification is that the content in scope (which was not clear if it was the single item or the whole page) must be checked in relation to the surrounding page or context. Previously, it could be interpreted that only the “component” or "specific content" needed to be checked in isolation. The intent is to ensure that the reading sequence is correct within the full context of surrounding elements, not just internally within the component.