JAWS not reading label for Toolbar menu & we can't navigate through options using keyboard

[Satya Minnekanti]

To reproduce the defect:

1. With JAWS on, open any CK Editor sample

2. Navigate to SCAYT menu in the toolbar and press Enter

Expected Result: SCAYT menu opens and JAWS read aria-label for SCAYT menu which is Options

Actual Result: JAWS just reads menu & says use arrow keys to navigate through options.

Press Down arrow key once.

Expected Result: Focus goes to first option & JAWS read that option.

Actual Result: Focus not going to first option, JAWS reading next button in the toolbar group or sometimes it reads elements path bar when we use down arrow key few times.

We are using FF22 & JAWS14

[Jakub Ś]

I was able to reproduce this problem on Windows 7/8 with JAWS 14 and FF23 but there was a catch.

I have found two issues here:

1st issue

1. Navigate to SCAYT menu and press Enter
2. You will get message about navigation with up and down arrows and if you press arrow you will be moved to next button.

2nd issue

1. Clean browsers cache and refresh page. Impornant for point 3
2. Navigate to SCAYT menu and press Enter
3. Just like in #10707 and #10705 to focus menu you need to press TAB before pressing arrow but the first time you do that (after cleaning cache) TAB will behave the same as arrows moving you to next button. Only after second attempt TAB will focus menu as it should.

I was able to reproduce this problem from CKEditor 3.5.

[Satya Minnekanti]

Replying to j.swiderski:

I was able to reproduce this problem on Windows 7/8 with JAWS 14 and FF23 but there was a catch.

I have found two issues here:

1st issue

1. Navigate to SCAYT menu and press Enter
2. You will get message about navigation with up and down arrows and if you press arrow you will be moved to next button.

2nd issue

1. Clean browsers cache and refresh page. Impornant for point 3
2. Navigate to SCAYT menu and press Enter
3. Just like in #10707 and #10705 to focus menu you need to press TAB before pressing arrow but the first time you do that (after cleaning cache) TAB will behave the same as arrows moving you to next button. Only after second attempt TAB will focus menu as it should.

I was able to reproduce this problem from CKEditor 3.5.

For the second issue.. Users should not have to press Tab to focus on the menu, the menu should already be focused when it's opened & pressing up/down arrow keys should visibly navigate menu options.. You can see this behavior at CK Editor 3.6.6 at ​​http://rev.ckeditor.com/ckeditor/trunk/7695/_samples/replacebyclass.html

[Jakub Ś]

@satya thank you for clarification.

The link you have pointed out didn't work for me either with JAWS. When JAWS is disabled there is no problem with pressing down arrow and focusing menu of any kind but if JAWS 14 is used then you can only focus menu(s) with tab.

My guess is that JAWS 14 has introduced some change that has broken editor all the way back.

[Satya Minnekanti]

Replying to j.swiderski:

@satya thank you for clarification.

The link you have pointed out didn't work for me either with JAWS. When JAWS is disabled there is no problem with pressing down arrow and focusing menu of any kind but if JAWS 14 is used then you can only focus menu(s) with tab.

My guess is that JAWS 14 has introduced some change that has broken editor all the way back.

@j.swiderski, The issue with focus not going to Context menu even with out JAWS is only happening in Firefox 23 on CK Editor 4.x builds, it works fine for 3.6.x builds, Where as with Firefox 17 ESR focus goes properly to context menu in both 4.x & 3.6.x builds.

with JAWS 14 & FF17 ESR navigating context menu items works corectly in both CK Editor 4.x & 3.6.x

[Frederico Caldeira Knabben]

Reduced TC

[Frederico Caldeira Knabben]

I've just attached a reduced TC for this case. It tries to emulate the CKEditor UI markup with as little as possible HTML. It also emulates the code execution flow for the menu button panel rendering.

Comments:

• I've found a limitation in Firefox, which has been worked around in the TC (the focus loop code).
• Things work very well with Firefox when JAWS is not enabled.
• When JAWS is active, things stop working.
• The DOM structure and ARIA attributes seem to be implemented properly.

I believe that the fix I did in point 1 could be useful for CKEditor, but still it doesn't solve the ticket problem (as the TC shows).

It would be interesting to have a position from FS, as it looks like JAWS is bringing these troubles. Feedback is welcome!

[Teresa Monahan]

Replying to fredck:

It would be interesting to have a position from FS, as it looks like JAWS is bringing these troubles. Feedback is welcome!

Thanks for the reduced testcase! We have asked Freedom Scientific to take a look at this so will let you know their feedback once they get back to us. Tickets #10707 and #10705 are probably both related to this too.

[Alexander Surkov]

I can't unarchive the zip file, it says error in packed. Ideas?

[Frederico Caldeira Knabben]

Supposed to be fixed by #10951.

[Frederico Caldeira Knabben]

Fixed by #10951.