-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Labels
Needs DevReady for, and needs developer effortsReady for, and needs developer efforts[Focus] Accessibility (a11y)Changes that impact accessibility and need corresponding review (e.g. markup changes).Changes that impact accessibility and need corresponding review (e.g. markup changes).[Priority] HighUsed to indicate top priority items that need quick attentionUsed to indicate top priority items that need quick attention[Status] In ProgressTracking issues with work in progressTracking issues with work in progress[Type] BugAn existing feature does not function as intendedAn existing feature does not function as intended[Type] RegressionRelated to a regression in the latest releaseRelated to a regression in the latest release
Description
Description
When trying to insert a block with the /block name syntax, the list box is no longer read to screen readers. This is because the aria-owns
and aria-activedescendent
attributes contain IDs out of the current iFrame scope causing a null error.
Step-by-step reproduction instructions
- Open a post or page.
- Go to insert a block by typing in the empty paragraph field. Something like /ima should do.
- Arrow up and down.
- Check to see the field now has the 2 ARIA attributes as mentioned in the description above.
- Try to do a
document.getElementByID()
ordocument.querySelector()
using the IDs from the ARIA attributes. The commands will return null.
6.I believe this is because the Autocomplete component renders outside the iFrame. Needs a fix as this feature is completely broken for screen reader users.
Screenshots, screen recording, code snippet
No response
Environment info
WordPress: 6.2-alpha-54678
Browser: Firefox
Screen reader: NVDA
OS: Windows 10 Professional
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
Metadata
Metadata
Labels
Needs DevReady for, and needs developer effortsReady for, and needs developer efforts[Focus] Accessibility (a11y)Changes that impact accessibility and need corresponding review (e.g. markup changes).Changes that impact accessibility and need corresponding review (e.g. markup changes).[Priority] HighUsed to indicate top priority items that need quick attentionUsed to indicate top priority items that need quick attention[Status] In ProgressTracking issues with work in progressTracking issues with work in progress[Type] BugAn existing feature does not function as intendedAn existing feature does not function as intended[Type] RegressionRelated to a regression in the latest releaseRelated to a regression in the latest release
Type
Projects
Status
Done 🎉