cubicweb #1368841 Remove access keys [open]
Apparently they are has-been and not useful since they can conflict with other keyboard shortcuts the user has. | |
| priority | normal |
|---|---|
| type | enhancement |
| done in | <not specified> |
| closed by | <not specified> |
similar entities
- cubicweb #1368827 Increase padding between paragraphs
- cubicweb #343392 unit testing accessibility (web pages)
- cubicweb-forge #1368883 Project page doesn't work without javascript
- cubicweb #1368838 Have quicklinks on top of the page
- cubicweb #1368829 Check contrast on greyish links in CubicWeb
[see all]
Comments
-
2010/10/29 09:34
-
2010/10/29 10:22, written by alutz
-
2010/10/29 09:42
-
2010/10/29 10:02, written by nchauvat
-
2010/10/29 10:21, written by alutz
add commentSince, web apps are more and more desktop oriented, I'm quite sure of
the opposite... (just see gmail keywords shortcuts for example).
I'm not sure gmail is accessible ;-) But I agree that I find them usefull.
I want more keybord shortcuts.
I want to be able to "validate" and to "apply" any form without having to scroll to the bottom of the page. I want to be able to "edit" any entity without having to use my mouse. I want to be able to easily navigate in the actions box with the keyboard... Don't make me use the mouse goddam!
Let any user have a preference to "disable all access keys" if they want.
I do not want the app to define shortcuts for me. I do not mind the app to provide default shortcuts (not too many, thank you), but it must let me configure the actual key combination.
Maybe we can have access keys defined (and configurable?) when the user is logged in ?