ISSUE-152: A.3 do we want to include the use of non-conventional keys if documented?

A.3 do we want to include the use of non-conventional keys if documented?

State:

CLOSED

Product:

ATAG Part A

Raised by:

Michael Squillace

Opened on:

2008-07-28

Description:

PRINCIPLE A.3: Authoring tool user interface must be operable
- A.3.1.5 "Chrome" Navigation - " Authors can use the keyboard to traverse
forwards/backwards all of the components, including those in floating
toolbars, panels, etc. using conventions of the platform (e.g., via "tab",
"shift-tab", "ctrl-tab", "ctrl-shift-tab")."
<MAS>As in A.3.1.2, do we want to include the use of non-conventional keys
if documented? This would definitely be a practice of the Eclipse platform
(eg CTRL-F7 to cycle through views). How is this criterion related to
A.3.1.8, inter-group navigation?</MAS>
- A.3.5.1 Text Search
<MAS>Given that most screen-readers have their own text search function and
that most IDEs today provide this, can we make it a level A
criterion?</MAS>

Related Actions Items:

No related actions

Related emails:

No related emails

Related notes:

Display change log