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

Form overview page: Up, Down and Edit buttons don't have useful accessible names #63

Closed
DavidBiddle opened this issue May 23, 2022 · 2 comments · Fixed by #77
Closed
Labels
accessibility This issue affects the accessibility of the prototype

Comments

@DavidBiddle
Copy link
Contributor

The 'Up', 'Down' and 'Edit' buttons on the form overview page don't have any additional visually hidden text, so for a screen reader user they will appear as identical buttons and it won't be clear what they do or which items they affect.

@DavidBiddle DavidBiddle added the accessibility This issue affects the accessibility of the prototype label May 23, 2022
@christophercameron-ixd
Copy link
Contributor

christophercameron-ixd commented May 23, 2022

Is there a way we could have sr-only text say something like:

Move above [question above name]

Move below [question below name]

Edit [current question name]

@DavidBiddle
Copy link
Contributor Author

We can do something like that, and I think that text would work for the Edit button, but ideally we'd want the text to refer to the question it operates on rather than the ones around it (I appreciate this creates a tricky content design challenge).

Depending on what journeys we want to test in our accessibility research, we could also consider removing the reordering buttons if necessary - we already have some indications from the usability sessions that this feature might need reworking, so it might be more valuable to do that before testing this again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility This issue affects the accessibility of the prototype
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants