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

Gutenberg is extremely unreliable with JAWS and Internet Explorer 11 #8429

Sorintata opened this issue Aug 3, 2018 · 5 comments

Gutenberg is extremely unreliable with JAWS and Internet Explorer 11 #8429

Sorintata opened this issue Aug 3, 2018 · 5 comments


Copy link

@Sorintata Sorintata commented Aug 3, 2018

I tried to do all the steps from the Gutenberg accessibility testing( but I got stuck several times.

To start with, I am using the folowing programs:

Windows 10
Internet Explorer 11
Wordpress 4.9.8
Gutenberg 3.4.0


Overal,the gutenberg experience is clumsy and unreliable with Jaws and IE. To be more precise:

  • The focus jumps randomly when using tab and shift tab;
  • Using the virtual cursor is almost impossible to add a new block that is not in the favorite(or most used) list;
  • Using the virtual cursor, sometimes the edit options to edit the block is not opening. You can't move, change font, change color, heading level etc.
  • With the virtual cursor off, it is tedious to add a new block. For instance, you tap on add new block, and you can't type in the name of the block, because it brings you back to editing the previous block. Using the arrow keys have the same behavior, your only chance is to browse the block categories by the tab key;
  • I was completely unable to create the table from the accessibility test. I can add the table block, I can add and delete before and after rows and colums, but I have no edit box to populate the table with text

These are my findings from a 2 hours test in which time I was able to do about 8 tasks from the list in the article provided at the beginning of this report.

Copy link

@designsimply designsimply commented Aug 4, 2018

Thank you for testing! In order to make this issue more actionable, we'll want to go through and check to see if each item you've raised has already been reported and if it has not then decide if a new issue is needed. This is something anyone volunteering can help with and I've added the Needs Testing label for that purpose.

Copy link

@nerrad nerrad commented Jun 3, 2019

This will need tested to see if this is still an issue with the changes since the original post.

Copy link

@afercia afercia commented Jun 7, 2019

Discussed during today's accessibility team bug-scrub, agreed this needs to be tested (extensively) again.

Copy link

@getsource getsource commented Mar 19, 2020

We discussed this during today's triage session.

@Sorintata, would you mind testing to see if this is still an issue, since there have been a lot of changes and fixes since this issue was created?

Thanks so much!

Copy link

@karmatosed karmatosed commented Apr 6, 2020

I am for now going to close this as there have been some improvements to this over time. We can always reopen if needed.

@karmatosed karmatosed closed this Apr 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants