Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: aria-label in calendar block controls #620

Merged
merged 2 commits into from
Mar 27, 2024

Conversation

deodorhunter
Copy link

No description provided.

@deodorhunter deodorhunter added the a11y-accessibility Fixes accessibility issues or adds accessibility features label Mar 27, 2024
@deodorhunter deodorhunter requested a review from pnicolli March 27, 2024 15:35
@deodorhunter deodorhunter self-assigned this Mar 27, 2024
@pnicolli pnicolli merged commit 1c7bd5c into main Mar 27, 2024
3 checks passed
@pnicolli pnicolli deleted the us_50673_calendar_form_controls_a11y branch March 27, 2024 16:03
icon={['fas', 'chevron-left']}
title={intl.formatMessage(messages.calendar_next_arrow)}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Siamo sicuri di aver bisogno di questo title dentro al pulsante? Non basta l'aria-label su button? Ho fatto un test veloce e lo SR legge solo l'aria-label
  2. Se il title è giusto, il corretto qui sarebbe "_prev_arrow"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hai ragione sul punto 2, bisogna che lo correggiamo @deodorhunter, mi è sfuggito.

Per il punto 1, ahimè dobbiamo metterlo. Non serve a niente per lo screen reader ma il tool che usiamo per il test (MAUVE++) vuole le aria-label in tutte le icone, anche se hanno aria-hidden. È inutile, ma non possiamo farci niente.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a11y-accessibility Fixes accessibility issues or adds accessibility features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants