fix(input): improve error text accessibility #30635
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
brandyscarney
requested changes
Aug 29, 2025
...gular/test/base/src/app/standalone/validation/input-validation/input-validation.component.ts
Outdated
Show resolved
Hide resolved
...test/base/src/app/standalone/validation/textarea-validation/textarea-validation.component.ts
Outdated
Show resolved
Hide resolved
...test/base/src/app/standalone/validation/textarea-validation/textarea-validation.component.ts
Outdated
Show resolved
Hide resolved
...gular/test/base/src/app/standalone/validation/input-validation/input-validation.component.ts
Outdated
Show resolved
Hide resolved
...lar/test/base/src/app/standalone/validation/input-validation/input-validation.component.html
Outdated
Show resolved
Hide resolved
brandyscarney
approved these changes
Sep 3, 2025
...lar/test/base/src/app/standalone/validation/input-validation/input-validation.component.scss
Outdated
Show resolved
Hide resolved
...st/base/src/app/standalone/validation/textarea-validation/textarea-validation.component.scss
Outdated
Show resolved
Hide resolved
...lar/test/base/src/app/standalone/validation/input-validation/input-validation.component.html
Outdated
Show resolved
Hide resolved
...st/base/src/app/standalone/validation/textarea-validation/textarea-validation.component.html
Outdated
Show resolved
Hide resolved
...test/base/src/app/standalone/validation/textarea-validation/textarea-validation.component.ts
Outdated
Show resolved
Hide resolved
...test/base/src/app/standalone/validation/textarea-validation/textarea-validation.component.ts
Outdated
Show resolved
Hide resolved
...gular/test/base/src/app/standalone/validation/input-validation/input-validation.component.ts
Outdated
Show resolved
Hide resolved
…-validation/input-validation.component.scss Co-authored-by: Brandy Smith <[email protected]>
Co-authored-by: Brandy Smith <[email protected]>
Co-authored-by: Brandy Smith <[email protected]>
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.
Issue number: resolves internal
What is the current behavior?
Currently, when an error text is shown, it may not announce itself to voice assistants. This is because the way error text currently works is by always existing in the DOM, but being hidden when there is no error. When the error state changes, the error text is shown, but as far as the voice assistant can tell it's always been there and nothing has changed.
What is the new behavior?
With these changes, both input and textarea have been updated so they'll properly announce error text when it shows up. We had to do this with a mutation observer and state because it's important in some frameworks, like Angular, that state changes to cause a re-render. This, combined with some minor aria changes, makes it so that when a field is declared invalid, it immediately announces the invalid state instead of waiting for the user to go back to the invalid field.
Does this introduce a breaking change?
Other information
Current dev build:
Screens
Textarea
Input