A11Y [fix]: Ensure customer support form errors notify screen readers#3227
Merged
Conversation
…tra logic since we don't control the HTML inside of it.
joshlarson
approved these changes
Jun 5, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Scope
Asana Ticket: ♿ Ensure customer support form errors notify screen readers
Implementation
Added error indicators for the recaptcha input. It needed a bit of extra logic since we don't control the HTML inside of it.
I also noticed that our JS scripts do not attach themselves until the document is fully loaded. On local the recaptcha takes a few seconds to load, and if the form is submitted during that time it will fail to properly validate with javascript.
Screenshots
Prod
Local
How to test
http://localhost:4001/customer-support
Leave the Recaptcha blank and try to submit the form