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

Inserting a link doesn't work with speech recognition software #6011

Closed
afercia opened this issue Apr 5, 2018 · 5 comments
Closed

Inserting a link doesn't work with speech recognition software #6011

afercia opened this issue Apr 5, 2018 · 5 comments
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes).

Comments

@afercia
Copy link
Contributor

afercia commented Apr 5, 2018

Breaking this down from Eric Wright (@ewaccess) testing session with Dragon NaturallySpeaking (speech recognition software). Please refer to the videorecorded session posted here:
https://make.wordpress.org/accessibility/2018/03/28/accessibility-of-gutenberg-the-state-of-play/

Please refer to the video above, starting from about min. 23:40

When inserting a link and the link field is focused, voicing the command "Press enter key" triggers browser validation, as if the field was empty. Seems this is not the only case when using speech recognition software, the UI doesn't get an input field is actually populated with some text. See also #6010 and #5468.

@afercia afercia added the [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). label Apr 5, 2018
@afercia
Copy link
Contributor Author

afercia commented Jun 20, 2018

See also #5468 when this issue was first noticed on the Title field.

@afercia afercia removed this from the Merge Proposal: Accessibility milestone Jun 20, 2018
@afercia
Copy link
Contributor Author

afercia commented Jun 20, 2018

Removing from the Merge Proposal milestone, as right now it's unclear how to solve this and it should be solved together with the similar issues anyways.

@afercia
Copy link
Contributor Author

afercia commented Sep 10, 2018

See #5468 (comment)
We have now a clue why this is happening. Still unclear how to solve it in a proper way.

@paaljoachim
Copy link
Contributor

@joedolson Joe. Is this issue still valid?

@annezazu
Copy link
Contributor

annezazu commented Sep 6, 2024

Closing this out as we haven't had an update in three years on a six year old issue and the link editing experience has greatly changed. As of now, I think this issue takes precedence on the experience: #60901

If that's wrong, let's reopen!

@annezazu annezazu closed this as completed Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes).
Projects
None yet
Development

No branches or pull requests

4 participants