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
Unable to Focus Error Log with Screen Reader/Keyboard #3509
Comments
Could you give this version a try? Windows 64-bit ZIP This adds a |
Works on W7.
That confused me for a while, I thought after Window/Error-log, press Enter to go to Editor... :| No, Window-Error-log, scroll through the list of errors (with Up/Down keys) press Enter to go to the line with that error. Thought-bubble, listing all the Editor tabs on the bottom of the 'Window' menu would also aid navigation... |
Add window menu to allow keyboard access to all docked windows (fixes #3509).
I wanted to keep things minimal so we can include as accessibility fix for the release. It would be great to collect more ideas for improving accessibility. |
Using OpenSCAD 2020.11.30.ci6340
With a screen Reader (I am using NVDA), there seems to be no way to bring keyboard focus to the error log, and potentially other windows.
From the main window, create code that causes an error and press F6.
Expected result: The error is displayed, and either focus would jump straight to the error or there would be a way to move focus manually.
Current result: The error is displayed, but screen reader-specific navigation commands are needed to read the text.
There are a couple of possible ideas. First, adding Ctrl+Tab and Ctrl+Shift+Tab to move between windows would allow for keyboard access. Additional shortcuts to jump to specific windows would also be helpful.
Once in an additional window, such as the error log, it is possible to use the arrow keys to move through the list of errors. It would be good to allow for pressing enter to move focus to the line of the error, if an equivalent feature is available with the mouse.
The text was updated successfully, but these errors were encountered: