[19580] fix: Remove hardcoded aria-labels in date picker#19582
Open
fkwq34 wants to merge 1 commit into
Open
Conversation
4 tasks
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
1 participant
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.
fixes: #19580
Fixes an accessibility label-content-name-mismatch issue in Datepicker header navigation.
The month and year switch buttons were using static aria-label values (chooseMonth / chooseYear) that could differ from their visible labels (e.g. January, 2026). This caused a mismatch between visible text and accessible name, impacting speech-input users and triggering axe violations.
This PR removes those explicit aria-label bindings so the buttons use their visible text as the accessible name, aligning behavior with WCAG/axe expectations while keeping existing Datepicker functionality unchanged.