- From: Al Gilman <asgilman@iamdigex.net>
- Date: Wed, 06 Oct 1999 13:56:08 -0500
- To: w3c-wai-ua@w3.org
At 10:21 AM 10/4/99 -0700, Jon Gunderson wrote: >Discussion > > 1.Issue #96: Issues related to Checkpoint 2.1: Mapping of user agent >functions to control mechanisms and memory demands related to > sequential/direct access to functionalities > http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#96 > In addition to cognititve demands that turn into failure modes, there are motor demands that may also be a failure mode if there are not enough shortcuts. Guideline: The keystroke-only command protocol of the UA UI should be efficient enough to support production use. Guideline: The user has to understand the choices availble to them at any time. Technique: Provide overlapping coverage of frequently used actions by dialogs which cover a range in aspect ratio, i.e. how short-wide or tall-narrow they are. Technique: Make the most used commands things that are easy to do. Technique: Make the safety net that reaches all end states depend only on things that are easy to do. Definition: Shortcuts represent short-wide dialogs. Phone menus represent tall-narrow dialogs. Dependency: some motor-impaired users depend on shortcuts to a P2 level of severity. Dependency: short-wide choice trees can get too slow (P2) for eyes-free users. Dependency: tall-narrow choice trees tax people's vocabulary/memory (P3).
Received on Wednesday, 6 October 1999 13:57:20 UTC