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

Accessibility issue: ambiguous accessible label for previous and next button #1087

Open
scoutb-cogapp opened this issue Aug 13, 2024 · 0 comments

Comments

@scoutb-cogapp
Copy link

UV version: [email protected]

I'm submitting a: bug report => please fork one of these codesandbox examples with a repro of your issue and include a link to it below

Page area

previous and next button inside image controls

Issue description

These buttons have the title "Previous" and "Next" which is not as descriptive as it should be. A non-sighted user may not be aware that they are in an image viewer. It has never really been announced when the user entered the image viewer by tabbing. They would have to come to this conclusion by observing other buttons (like the zoom in and out buttons) and also conclude that the proximity to the other buttons means that the previous and next buttons also apply to an image. A lot of assumptions.

Steps to reproduce

  1. open this manifest
  2. use a screenreader to navigate to the previous and next buttons inside the image viewer and observe what is announced

Expected behaviour

Clear accessible labels that leave no doubt to users of assistive technology what they do.

Possible fix

change the title attribute to "Next button" and "Previous button"

WCAG criterion

4.1.2 Name, Role, Value (Level A)

Related code

<div class="paging btn prev" tabindex="0" title="Previous" style="position: relative; padding-left: 0px; padding-top: 0px; display: inline-block; top: 239px;"></div>

Other information

Note: This thinking could reasonably be applied to all the buttons in image controls but since something like zoom is usually assumed to apply to visuals, I have not raised it. It would not be a bad idea to go through the button names and labels and assess if their accessible lables can be improved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Accessibility Backlog
Development

No branches or pull requests

2 participants