Feature roadmap/Keyboard navigability: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (fix link to User:Homunq) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 2: | Line 2: | ||
|Name=Keyboard navigability |
|Name=Keyboard navigability |
||
|Feature subcategory=GUI and usability |
|Feature subcategory=GUI and usability |
||
|Requesters=Homunq |
|Requesters=User:Homunq |
||
|Requirements=All options in the menu and frame should be accessible from the keyboard (ctrl-xxx). There should be some way to see what key is associated with a given option, both when using it and when "looking for the key". This should require a minimum (ideally, zero) programming from activity developers. This is a key part of the strategy for improving the situation of bad trackpads; it is unrealistic to expect the trackpad problem to be 100% resolved. |
|Requirements=All options in the menu and frame should be accessible from the keyboard (ctrl-xxx). There should be some way to see what key is associated with a given option, both when using it and when "looking for the key". This should require a minimum (ideally, zero) programming from activity developers. This is a key part of the strategy for improving the situation of bad trackpads; it is unrealistic to expect the trackpad problem to be 100% resolved. |
||
|Specification=Holding the control (or frame) key should show semitransparent letters/numbers over any menu (or frame) gadget visible. These letters should also appear for ~150 ms when an option is chosen. Default letters should be chosen by the relevant python classes if not specified by developer. Any specification should be localizable. Ideally, contextual menu options should be accessible with multiple keystrokes. |
|Specification=Holding the control (or frame) key should show semitransparent letters/numbers over any menu (or frame) gadget visible. These letters should also appear for ~150 ms when an option is chosen. Default letters should be chosen by the relevant python classes if not specified by developer. Any specification should be localizable. Ideally, contextual menu options should be accessible with multiple keystrokes. |
||
|Owners=Homunq |
|Owners=Homunq |
||
|Priority=3 |
|||
|Helps deployability=no |
|||
|Target for 9.1=no |
|||
}} |
}} |
||
Latest revision as of 05:14, 21 December 2008
| Feature subcategory | Is part of::Category:GUI and usability | |
| Requesters | {{#arraymap:User:Homunq|,|x|Requested by::x}} | |
| Requirements | All options in the menu and frame should be accessible from the keyboard (ctrl-xxx). There should be some way to see what key is associated with a given option, both when using it and when "looking for the key". This should require a minimum (ideally, zero) programming from activity developers. This is a key part of the strategy for improving the situation of bad trackpads; it is unrealistic to expect the trackpad problem to be 100% resolved. | |
| Specification | Holding the control (or frame) key should show semitransparent letters/numbers over any menu (or frame) gadget visible. These letters should also appear for ~150 ms when an option is chosen. Default letters should be chosen by the relevant python classes if not specified by developer. Any specification should be localizable. Ideally, contextual menu options should be accessible with multiple keystrokes. | |
| Owners | {{#arraymap:Homunq|,|x|Contact person::User:x}} | |
| Priority | Priority::3 | |
| Helps deployability? | Helps deployability::no | |
| Target for 9.1? | Target for 9.1::no |