#5919 closed Bug (invalid)
Table tab behavior and accessibility
| Reported by: | Lynne Kues | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | Accessibility | Version: | |
| Keywords: | IBM | Cc: |
Description
3.4 Beta
Currently in the table there is no way to get out of it. ctrl-tab and ctrl-shift tab should take the user out of the editor while in a table.
Overall, I think tab should keep focus in the editor and ctrl-tab/ctrl-shift-tab should navigate out of the editor. This is typical editor behavior and would give the user the ability to customize the tab keystroke without also having to deal with customizing navigation out of the editor. I thought this was the implemented behavior in the 3.4 zip, since I was seeing this behavior, but that was due to our plugin. I would like to discuss this further with the Lotus CKEditor folks, but at a minimum, there must be a way to navigate out of the table.
Change History (5)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
You're probably right about the crazy part. Then maybe some other keystroke can take the user out of the table. Or some other keystroke could be used for cell navigation (tab really does makes the most sense for cell navigation though). Any suggestions?
comment:3 Changed 14 years ago by
Another option would be to force the user to navigate out of the table and into the editor in order to navigate out of the editor. I am actually okay with this solution, but I would want to run it by the Lotus community to make sure it is okay with them from an accessibility standpoint.
comment:4 Changed 14 years ago by
| Milestone: | CKEditor 3.4 |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
The code already includes ALT+ARROW-DOWN and ALT+ARROW-UP as alternatives for TAB and SHIFT-TAB on cell navigation.
The alternative to move out of tables is simply using the ARROW-DOWN key. It should navigate through the table rows, leaving it when the last row is reached.
One can set the enableTabKeyTools to false, to disable the TAB behavior on tables (right because of this usability aspect), keeping the arrow options, but I would not recommend it. I still think people expect TAB to be used to navigate inside tables.
I think this combination of features is already sufficient. Please feel free to reopen the ticket if you have any concrete proposition that could help enhancing it.
comment:5 Changed 14 years ago by
Thanks Fred. I was unaware of the other key sequence and the enableTabKeyTools option. I agree that the combination of features is sufficient.
Ctrl+Tab (& Shift) is used in all the browser to switch between tabs. If that combo is restricted to some behavior in the editor I think that people will become crazy about it.