Fix/accessibility labels#127
Merged
Macacoazul01 merged 3 commits intoMacacoazul01:masterfrom Feb 26, 2026
Merged
Conversation
Owner
|
Tks for the PR. Just gonna check something about the semantics widget and then merge |
Owner
|
@gabrielezereik im gonna add it to the library without changing the default fallback for now ( |
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
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.
Add semantics support for header navigation arrows
This PR adds accessibility support to the header navigation arrows by introducing two new optional parameters in PickerHeaderSettings:
previousButtonSemanticsLabel — semantic label for the "previous" arrow button
nextButtonSemanticsLabel — semantic label for the "next" arrow button
These labels are passed down to a Semantics widget wrapping each IconButton in HeaderArrows, with button: true and excludeSemantics: true to ensure screen readers announce the custom label instead of the default "icon" description.
Motivation
Without explicit semantics, screen readers (e.g. TalkBack, VoiceOver) would announce the arrows as "icon", providing no meaningful context to visually impaired users. With this change, developers can provide localized, descriptive labels for these controls.
Usage