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

New cursors not always announced via screenreader Command + Option + Up/Down #119654

Closed
sana-ajani opened this issue Mar 23, 2021 · 1 comment
Closed
Assignees
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues *as-designed Described behavior is as designed

Comments

@sana-ajani
Copy link
Contributor

Testing #119082

Testing on Mac with Voiceover. When I use command + option + up/down to set multiple cursors quickly, it seems that the screenreader swallows up the middle cursors and only ends up announcing the last one. I think I expected the screenreader to announce all of them after the keyboard operation is completed, but I am not totally sure if this is just how screenreaders read actions when they happen so quickly.

recording (9)

@sana-ajani sana-ajani changed the title Command + Option + Up/Down New cursors not always announced via screenreader Command + Option + Up/Down Mar 23, 2021
@sana-ajani sana-ajani assigned isidorn and unassigned rebornix Mar 24, 2021
@isidorn
Copy link
Contributor

isidorn commented Mar 25, 2021

Thanks for filling this, however this is just how Screen Readers read things.
We are sending the correct data to be read, just VoiceOver decides to act like this.
For example NVDA reads both - you can see it if you turn on Tools > Speech Viewer

Thus closing as designed

@isidorn isidorn closed this as completed Mar 25, 2021
@isidorn isidorn added *as-designed Described behavior is as designed accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues labels Mar 25, 2021
@github-actions github-actions bot locked and limited conversation to collaborators May 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues *as-designed Described behavior is as designed
Projects
None yet
Development

No branches or pull requests

3 participants