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

Improve screen reader accessibility #70

Open
schulle4u opened this issue Apr 10, 2020 · 3 comments
Open

Improve screen reader accessibility #70

schulle4u opened this issue Apr 10, 2020 · 3 comments

Comments

@schulle4u
Copy link

Describe the bug
OnlyR doesn't correctly report button labels and other UI elements to screen readers, e. g. Windows Narrator and NVDA. When navigating the UI elements, Narrator only speaks control names and internal UI names, but not the labels or values. Using the opensource NVDA screen reader brings a little more accessibility to the UI, however the dropdowns in the settings page still are very tricky to use.

To Reproduce
Steps to reproduce the behavior:

  1. Start Windows Narrator by pressing Control+Win+Enter.
  2. Open OnlyR
  3. Press the tab key to navigate between UI elements. Windows Narrators speech output only will report the word "button", but not the labels.

Expected behavior
When navigating with a screen reader, OnlyR should provide correct labels for each button, checkbox and dropdown, otherwise the software is mostly useless for visually impaired users.

Screenshots
An audio demostration can be provided if needed.

Desktop (please complete the following information):

  • Windows 10 home 64, version 1909
@Blann
Copy link

Blann commented Apr 14, 2020

Just corroborating this – I’ve discovered the issue recently too, but from the perspective of UI automation. For most of the controls the Name property value is just “Button”. For UIA purposes one can get around it (in OnlyR, at least) by using the Help Text property to identify a specific control but that obviously isn’t how most screen readers work, and the thought did occur that accessibility would be somewhat limited as a result.

@AntonyCorbett
Copy link
Owner

@schulle4u @Blann I've completed some work on this, but there is plenty still to do on the Settings page.

@schulle4u
Copy link
Author

@AntonyCorbett Thank you, the main window already looks good so far. One more thing I've noticed is the missing keyboard focus upon launching the application. I have to press the tab key a few times to get to the buttons. It would be nice to set initial keyboard focus to the "start recording" button for even quicker application usage.

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

No branches or pull requests

3 participants