Opened 10 years ago
Last modified 8 years ago
#12235 confirmed Bug
AVT: Keyboard selection of widgets don't behave as expected — at Version 6
Reported by: | Satya Minnekanti | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | Accessibility | Version: | 4.3 |
Keywords: | IBM | Cc: |
Description (last modified by )
To reproduce the defect:
- Open Sample widgets page http://ckeditor.com/demo#widgets
- Try to select any of widgets( Simple Box, Code Snippet, Enhanced Image, Mathematical Formulas) using keyboard
Issue: It's not possible, It's possible to select them using only with mouse not with keyboard, as a result we can not open widget properties dialog using keyboard. This is a failure of Accessibility Checkpoint 2.1a Keyboard.
Check comment:4 for more details.
Change History (6)
comment:1 Changed 10 years ago by
Status: | new → pending |
---|
comment:2 follow-up: 3 Changed 10 years ago by
It's not possible to select the Whole widget with just one keyboard shorcut or arrow keys like the way we do with mouse. This should be similar to an image. This needs to be fixed.
comment:3 follow-up: 4 Changed 10 years ago by
Replying to satya:
It's not possible to select the Whole widget with just one keyboard shorcut or arrow keys like the way we do with mouse. This should be similar to an image. This needs to be fixed.
Sorry, but I still don't understand this fully.
Right now, while navigating through the contents with the right/left arrow keys, widgets get selected when passing through their insertion point. This in fact has been introduced as the accessibility option for widgets selection.
Are you trying to propose a different way for it or even saying that the above is not true/right? If so, can you give a more precise example on how you see this done right? Thanks!
comment:4 Changed 10 years ago by
Replying to fredck:
Replying to satya:
It's not possible to select the Whole widget with just one keyboard shorcut or arrow keys like the way we do with mouse. This should be similar to an image. This needs to be fixed.
Sorry, but I still don't understand this fully.
Right now, while navigating through the contents with the right/left arrow keys, widgets get selected when passing through their insertion point. This in fact has been introduced as the accessibility option for widgets selection.
Are you trying to propose a different way for it or even saying that the above is not true/right? If so, can you give a more precise example on how you see this done right? Thanks!
Hi Fred, There are lot of keyboard & JAWS issues with widgets that i have mentioned below
Issue 1: when we use right/left arrow keys to select the widget
1) In High Contrast mode there is no indication that widget is selected
2) with JAWS on, JAWS just reads selected it won't say what's been selected
Issue 2: User can't use arrow keys to navigate in and out of widgets(which has editable content like Simple Box)
Issue 3: If you use Up/Down arrow keys to read the content in editor JAWS not reading the widget as part of content(That is normal way how JAWS users read content, JAWS reads the image if its part of paragraph) left/right arrow key is not normal way to read/navigate through content
Issue 4: There are no ARIA Roles & name for the widget, so JAWS not reading it as widget even when selected and also when navigated in and out of it.
Issue 5: There is no info for the JAWS or normal user that he has to press Enter to open Edit Properties dialog.
Issue 6: There is no info for normal or JAWS users about how to navigate in and our of widget
comment:5 Changed 10 years ago by
Ok, so your original report was misleading. There is a way to select widgets with keyboard. The real problem is how widgets selection behave in terms of accessibility.
I see that there is a lot of research to be done here and also to understand what is possible to do. We gonna plan this accordingly. Thanks.
comment:6 Changed 10 years ago by
Description: | modified (diff) |
---|---|
Status: | pending → confirmed |
Summary: | AVT: Not possible to select any of widgets using keyboard → AVT: Keyboard selection of widgets don't behave as expected |
Ticket changes: Made the ticket title and description more related to the real problem.
It should be possible to do so by navigating with the right and left arrow keys. Can you confirm this?