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

Make screen-read locations less repetitive #1775

Merged
merged 1 commit into from
Mar 7, 2022

Conversation

tigt
Copy link
Contributor

@tigt tigt commented Mar 5, 2022

The previous markup looked like:

<span class="test_presets_tag">
  <img src="/images/test_icons/flags/US.svg" alt="Virginia, USA " title="Virginia, USA ">
  Virginia, USA 
</span>

While alt and title are normally helpful for solitary icons, in this case the location is displayed as plain text next to the flag. Screen readers would repeat the location name at least twice, and up to 3 times depending on verbosity settings.

The tooltip functionality of title was also suppressed by the wrapping <label> and/or the custom hover bubbles, so removing it should change nothing.

The previous markup looked like:

```html
<span class="test_presets_tag"><img src="/images/test_icons/flags/US.svg" alt="Virginia, USA " title="Virginia, USA ">Virginia, USA </span>
```

While `alt` and `title` are normally helpful for solitary icons, in this case the location is displayed as plain text next to the flag. Screen readers would repeat the location name at least twice, and up to 3 times depending on verbosity settings.

The tooltip functionality of `title` was also suppressed by the wrapping `<label>` and/or the custom hover bubbles, so removing it should change nothing.
@tkadlec tkadlec requested a review from scottjehl March 7, 2022 15:10
@scottjehl
Copy link
Contributor

Agreed! Thanks.

@scottjehl scottjehl merged commit 911109e into catchpoint:master Mar 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants