New Failure Technique for 1.4.13 Content on hover or focus when the pointer cannot be moved over the new popup content without that content closing #4771
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. |
detlevhfischer
changed the title
detlevhfischer
changed the title
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.
Attempt to create a new Failure for 1.4.13 Content on hover or focus to cover the situation when the pointer cannot be moved over the new popup content without that content closing.
One issue to check may be the situation where keyboard focussing causes a popup to appear and then the pointer (mouse) is used to make popup contents visible by changing the viewport section. I would expect that the same applies as when the content appears on pointer hover, but may have missed something here.