Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
thetaPC
reviewed
Jan 13, 2026
Contributor
thetaPC
left a comment
thetaPC
left a comment
There was a problem hiding this comment.
Where are we getting the expectation for this behavior? When I tested the native inputs from W3 examples to verify that we match, but the screen reader is reading the labels first. Based on this, I would expect that the labels are focused first then the input.
Member
Author
AAA had an ADA audit that flagged this behavior as unexpected |
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.
Issue number: resolves internal
What is the current behavior?
When using
ion-inputwith a label on Android, TalkBack treats the visual label text as a separate focusable element. This causes the initial focus to land on the label instead of the input field, creating a confusing experience for screen reader users.What is the new behavior?
The label text wrapper is now hidden from the accessibility tree via
aria-hidden="true", while the native input maintains proper labeling througharia-labelledby. This ensures Android TalkBack focuses directly on the input field while still announcing the label correctly.Does this introduce a breaking change?
Other information
Current dev build: