Community
Participate
Working Groups
According to the Accessibility requirements, we need provide keyboard short-cuts or menu equivalents to all toolbar functionality. The four buttons in the Outline view do not meet this requirement. FYI: The Make Targets view is a good example of how this requirement is met as the context menu for this view contains all of the functionality found in the toolbar.
The following views have the same problem as indicated above: Navigator C/C++ Projects Tasks Properties Console Variables Expressions Registers Breakpoints
Oops, I guess CDT is not responsible for all of the views in the above list ;) Please correct me if I am wrong: Outline (Platform) Navigator (Platform) C/C++ Projects (CDT) Tasks (Platform) Properties (Platform) Console (Platform) Variables (Platform) Expressions (Platform) Registers (Platform) Breakpoints (Platform) Please address any views that do not appear in this list but do belong to CDT and have the indicated problem. Thanks
C/C++ Projects (CDT) Make target view Some other debug view Adding dinglis and Mikhailk on the cc for proper followup.
Raising priority since navigability is top accessibility concern.
Let's lower this priority as the requirement is actually to provide menu items for all toolbar actions OR provide keyboard access to toolbars. You can get to the views via Ctrl+F7, then shift+tab to get to the toolbar, and arrow keys to move along the toolbar, spacebar to operate the button. Going forward however, using the idea that toolbar icons are ways to get at frequently repeated operations quickly so providing shortcut keys for all items on the toolbar and documenting them in the pull-down menu is recommended to make the application more accessible. The documentation is just the key sequence for the shortcut (eg Ctrl+Space) and these are faster than mnemonics (the underlined letter in a menu item). It is a good design point as well to provide mnemonics for all non-dynamic menu items.
Ok, reducing priority to P3 to get it off the gating list for 2.0
PR was targeted to the 2.0 release but not resolved, moving target to 2.1
Vivian please take a look.
This bug was assigned and targeted at a now released milestone (or Future or Next that isn't being used by CDT). As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and mark the bug as resolved.
