-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Try ARIA role application on the writing flow area. #5807
Conversation
Adding in progress so it's not merged by mistake. |
8896083
to
2f40ecb
Compare
Rebased on latest master. |
I've just tested again this PR with Firefox and NVDA and the It is expected that What I wasn't expecting is that, when inside the element with For example, when invoking the Elements List in NVDA there are no landmarks any longer. No headings at all. Navigation through headings and landmarks doesn't work. Potentially, any other screen-reader specific shortcut to navigate through content doesn't work at all. Screenshot without Screenshot with Basically (and considering just these two side-effects) there wouldn't be no way for screen reader users to jump from the blocks to the top bar or to the sidebar, which is essential to be able to operate on the blocks. I haven't tested other potential side-effects but potentially there's a lot of them that could break interaction in a so severe way to make impossible to use the editor. |
Is there still a relevancy / desire to continue the work here? |
This PR was mainly for testing purposes, the accessibility team wanted to test the behavior of assistive technologies when switching everything to |
Please don't merge :)
As discussed during today's accessibility meeting on Slack, this PR aims to try the ARIA
role="application"
on the post content area for a series of A/B testing with assistive technologies users.The role is set on the Gutenberg "writing flow" area (which includes the post title) to make sure the writing flow keyboard events work as expected with screen readers.
The
role="application"
could solve a series of issues (see for example #5709 ) but also introduce new ones, so some actual testing is definitely necessary.