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

Screen reader with keyboard shortcuts #6573

Open
clapierre opened this issue Jun 14, 2019 · 1 comment
Open

Screen reader with keyboard shortcuts #6573

clapierre opened this issue Jun 14, 2019 · 1 comment
Labels
tag:Accessibility tag:Keyboard Compatibility issues with keyboards, including locale-specific and layout-specific issues
Milestone

Comments

@clapierre
Copy link

@ivanov commented on May 15
Using NVDA - we can confirm that

Ctrl-Shift-] and Ctrl-Shift-[ work for switching tab navigation, but no announcement of the tab name is made - so the user has no idea what tab they switched to.

Ctrl-B works to toggle the left pane, but again, does not announce.

Ctrl-Shift-B to toggle the single document mode works, but again does not announce.

Ctrl-Shift-C to focus the command palette works, but again does not announce.

Tab completion behavior - work, not announcing when initially invoked, and improperly repeating the text already typed, and not announcing the options themselves as they are navigated through.

Ctrl-S works to save, but does not announce the status. It should use an aria-live region.

Additionally, after discussing with James and Neil - you might want to enable that behavior to be customizable, to allow screen reader users to opt in and out of this behavior.

Ctrl-Shift-S brings up a non-real-dialog, but Tab behavior does allow navigation between those buttons.

Ctrl-F and Ctrl-G work - but no announcement of navigation. The default browser behavior announces the number of the result, at least.

Ctrl-Shift-L works - but again, no announcement (feedback) about a new panel having been created.

@tonyfast
Copy link
Contributor

tonyfast commented Dec 4, 2020

these descriptions relate the lack of status messages referenced in #9399

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tag:Accessibility tag:Keyboard Compatibility issues with keyboards, including locale-specific and layout-specific issues
Projects
Accessibility
Keyboard/Gestures
Development

No branches or pull requests

4 participants