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

Accessibility: Screen reader no longer reads text in Paragraph block when editing #51408

Open
jamiepalatnik opened this issue Mar 25, 2021 · 3 comments
Labels
Accessibility (a11y) Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Pri] Normal Schedule for the next available opportuinity. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. [Type] Bug

Comments

@jamiepalatnik
Copy link

Steps to reproduce the behavior

  1. Using JAWS screen reader, go to a Paragraph block with text to edit.
  2. Edit text.

What I expected to happen

Screen reader should read out text letter by letter so that user can edit. This allows the user to correct typos and make other changes.

What actually happened

The cursor moves as expected but the screen reader only reads the first letter and does not read the other letters.

Context

3853396-zd-woothemes
#user-report

Wondering if this issue could be related: WordPress/gutenberg#29526

@daria2303
Copy link

3964395-zd-woothemes

@youbrokesomething youbrokesomething added the [Pri] Normal Schedule for the next available opportuinity. label Apr 7, 2023
@autumnfjeld
Copy link
Contributor

See Editable blocks have inconsistent ARIA role: sometimes textbox, sometimes document

It looks like this is a Gutenberg issue.

@github-actions
Copy link

Support References

This comment is automatically generated. Please do not edit it.

  • 3853396-zen
  • 3964395-zen

@cometgrrl cometgrrl added the [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. label Oct 31, 2023
@cometgrrl cometgrrl moved this from Needs Triage to Needs Core/3rd Party Fix in Automattic Prioritization: The One Board ™ Oct 31, 2023
@cuemarie cuemarie added the [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. label Nov 2, 2023
@mrfoxtalbot mrfoxtalbot moved this to To triage in Dotcom Core Fix Needed Sep 2, 2024
@jeherve jeherve added Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". and removed User Report labels Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility (a11y) Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Pri] Normal Schedule for the next available opportuinity. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. [Type] Bug
Projects
Status: Needs Core/3rd Party Fix
Development

No branches or pull requests

7 participants