Fix screenreader-only button #492
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
Member
|
Lookin' good. I re-run the test-integration in the hope the CPD shim mirror is back up.. 🤞 |
MKodde
approved these changes
Dec 4, 2025
Prior to this change, the screenreader only button expanded the html page beyond its bounds and created a horizontal scrollbar which upon scrolling revealed the submit button. This change applies a common fix for this issue by using a more robust way of app See https://stackoverflow.com/a/62109988/7540890
johanib
force-pushed
the
feature/fix-screenreader-button
branch
from
ad9116c to
6f7e34a
Compare
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.
Prior to this change, the screenreader only button expanded the html page beyond its bounds and created a horizontal scrollbar which upon scrolling revealed the submit button.
This change applies a common fix for this issue by using a more robust way of app
See #433 (comment)
See https://stackoverflow.com/a/62109988/7540890