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.

Sign up for GitHub

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

Jump to bottom

Confusing voice commands when using a screen reader with the Access Plan UI #2785

Open
4 tasks
brianhogg opened this issue Oct 29, 2024 · 0 comments
Open
4 tasks

Confusing voice commands when using a screen reader with the Access Plan UI #2785

brianhogg opened this issue Oct 29, 2024 · 0 comments
Assignees
@brianhogg
Labels
Accessibility good first issue If you're a first time contributor this is a good issue for you! Status: Needs Code This issue needs code to be fixed

Comments

@brianhogg
Copy link
Contributor

Reproduction Steps

  1. Begin to create or edit an access plan for a course
  2. Start at "Plan Title" and continue tabbing past the "Visibility" dropdown until you get to the "Visual" tab of the "Plan Description" TinyMCE editor

Expected Behavior

An introduction that you have entered the Plan Description part of the Access Plan UI

Actual Behavior

Just "Visual button" voice command with no context as to what that is for, even when you get to the textarea part

CleanShot.2024-10-29.at.10.26.50.mp4

This issue has be recreated:

  • Locally
  • On a staging site
  • On a production website
  • With only LifterLMS and a default theme

Browser, Device, and Operating System Information

Chrome, macOS
@ideadude ideadude moved this to Awaiting Triage in Development Oct 29, 2024
@ideadude ideadude self-assigned this Oct 29, 2024
@brianhogg brianhogg assigned brianhogg and unassigned ideadude Oct 29, 2024
@brianhogg brianhogg added Accessibility good first issue If you're a first time contributor this is a good issue for you! Status: Needs Code This issue needs code to be fixed labels Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brianhogg brianhogg

Labels
Accessibility good first issue If you're a first time contributor this is a good issue for you! Status: Needs Code This issue needs code to be fixed
Projects
Development
Status: Awaiting Triage
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brianhogg @ideadude