Task 1 - Proposed Modifications to ATAG2.0 Oct 31 2003 Techniques for Checkpoint 1.1 (considering ISO16071)

Techniques

• opening paragraph - add the following sentence after current third sentence: "ISO16071:2002 has guidelines organized into three priority levels (accessibility impact): core, primary and secondary; in addition, two kinds of implementation responsibility are defined: OS(operating system), and application(productivity applications, ,development tools, web browsers, etc.)." Delete all current sentences after third sentence.
• following standards - add the following Guidelines from ISO16071:2002: 7.8.2, 7.9.4, 7.10.1
• configurability add the following Guidelines from ISO16071:2002: 7.2.11, 7.5.6, 7.5.7, 7.8.3, 7.8.4, 7.9.2, 7.9.3, 7.12.4
• input device independence add the following Guidelines from ISO16071:2002: 7.4.5, 7.4.6, 7.4.8, 7.4.12, 7.5.9
• icons, graphics, sounds add the following Guideline from ISO16071:2002: 7.7.2
• layout add the following Guidelines from ISO16071:2002: 7.5.3, 7.6.1, 7.6.2, 7.7.1, 7.7.4
• user focus - add the following Guidelines from ISO16071:2002: 7.2.10, 7.8.6, 7.13.3, 7.13.4
• documentation add the following Guidelines from ISO16071:2002: 7.2.13, 7.11.1

References-

• new heading "Guidelines for Authoring Tool Accessibility" (only heading)
• have a single entry under this heading which would be the ISO16071:2002 reference
• delete everything else under "References"

Task 2 - Mapping of ISO16071:2002(E) Guidelines Part 7 To the ATAG2.0 Oct 31 2003 Techniques for Checkpoint1.1

• 7.2 General Guidelines
  • 7.2.1.1: enable user input/output choice - TO251
  • 7.2.1.2: enable switching of input/output alternatives - TO256
  • 7.2.2: enable user to perform task effectively with any single input device - TO258
  • 7.2.3: provide user-preference profiles - TO255
  • 7.2.4: enable user setting of timed responses - TO278
  • 7.2.5: provide object descriptions - TO266 and TO272
  • 7.2.6: accessibility features should be easy to turn on and off - TO256 and TO257
  • 7.2.7: safeguard against inadvertent activation or deactivation of accessibility features - TO277 and TO254
  • 7.2.8: inform user of accessibility feature on/off status - TO251
  • 7.2.9: enable persistent activation - TO279
  • 7.2.10: avoid seizure-inducing blink rates - no mapping
  • 7.2.11: provide undo functionality - no mapping
  • 7.2.12: enable user control of time-sensitive presentation of information - TO278
  • 7.2.13: clarify natural language usage - no mapping
• 7.3 Assistive Technologies
  • 7.3.1 use system-standard input/output - TO252
  • 7.3.2 provide object labels - TO272
  • 7.3.3 make event notification available to assistive technologies - TO250
  • 7.3.4 make object attributes available to assistive technologies - no mapping (maybe a little of TO249?)
  • 7.3.5 present user notificaiton in a relevant manner - TO250
• 7.4 Keyboard-Input Configuration
  • 7.4.2 enable sequential entry of multiple keystrokes - TO260, TO262
  • 7.4.3 provide customization of delay before key acceptance - TO278
  • 7.4.4 provide customization of same-key double-strike acceptance - TO278
  • 7.4.5 provide customization of key repeat rate - no mapping
  • 7.4.6 provide customization of post-key-press delay of repeat onset - no mapping
  • 7.4.7 provide keyboard control of pointer functions - TO258
  • 7.4.8 provide notification about toggle key status - no mapping
  • 7.4.9 provide accelerator keys - TO260
  • 7.4.10 provide implicit designators - TO260
  • 7.4.11 reserve accessibility key-mappings - TO259
  • 7.4.12 enable remapping of keyboard functions - no mapping
  • 7.4.13 separate keyboard navigation and activation - TO261?
• 7.5 Software control of pointing devices
  • 7.5.2 enable the adjustment of the location of button functions - TO257
  • 7.5.3 enable multiple clicks with a single key press and release - TO273
  • 7.5.4 enable button hold with a single button press and release - TO278
  • 7.5.5 enable delay of pointer-button-press acceptance - TO278
  • 7.5.6 enable delay of pointer movement acceptance after mouse-down event - no mapping except for TO256?
  • 7.5.7 enable customization of multiple-click interval and target area - TO278
  • 7.5.8 enable pointer speed and ratio adjustment - TO256
  • 7.5.9 provide alternatives to chorded key presses - no mapping except for TO261?
• 7.6 Display Fonts
  • 7.6.1 enable font customization and legibility - no mapping
  • 7.6.2 adjust the scale and layout of objects as font-size changes - TO275
• 7.7 Displays
  • 7.7.1 enable users to customize viewing attributes - no mapping
  • 7.7.2 use text characters as text, not as drawing elements - no mapping
  • 7.7.3 provide access to information displayed in "virtual" screen regions - TO274
  • 7.7.4 enable appropriate presentation of tables - no mapping
• 7.8 Color
  • 7.8.1 provide alternatives to the use of color as the sole source of information - TO271
  • 7.8.2 provide color palettes designed for people who have visual impairments - no mapping
  • 7.8.3 allow users to create color palettes - no mapping
  • 7.8.4 use user-determined color settings - no mapping
  • 7.8.5 allow users to customize color-coding - TO256
  • 7.8.6 provide alternatives to coding by hue - no mapping
• 7.9 Audio output
  • 7.9.2 enable audio customization - no mapping except maybe for TO256?
  • 7.9.3 default frequency range for non-speech audio - no mapping except for TO256?
  • 7.9.4 provide specified frequency components for audio warnings and alerts - no mapping except for TO256?
  • 7.9.5 allow users to choose visual indication of audio output - TO264
• 7.10 errors and user notification
  • 7.10.1 allow task-relevant warning or error information to persist - no mapping
• 7.11 Onlne documentation and help
  • 7.11.1 provide alternative methods for accessing on-line documentation and help - no maping
  • 7.11.2 provide generic-help content - TO281
  • 7.11.3 provide on-line documentation and help on accessibility features - TO280
• 7.12 customization of user preferences
  • 7.12.1 enable customization of user preferences - TO257
  • 7.12.2 enable customization of common interface elements - TO257
  • 7.12.3 enable cursor and pointer customization - TO257
  • 7.12.4 provide capability to use preferences across locations - TO255?
• 7.13 Window appearance and behavior
  • 7.13.1 enable non-pointer navigation directly to windows - TO276
  • 7.13.2 enable "always on top" windows - TO277 and TO279
  • 7.13.3 provide user control of multiple "always on top" windows - no mapping
  • 7.13.4 enable user choice of effect of input focus on window stacking order - no mapping
• 7.14 keyboard input focus
  • 7.14.1 provide focus cursor - TO276
  • 7.14.2 provide keyboard navigation - TO258
  • 7.14.3 provide navigation to task-appropriate groups of controls - TO261
  • 7.14.4 retain input-focus location - TO261

Additional Information (thanks to Karen Mardahl):

Technically, it seems appropriate for ATAG Techniques to reference ISO TS 16071: 2002; however,the document is copywrited and people would have to purchase the document (via ISO or ANSI). This standard, now published, is not available online; it would have to be purchased in printed form from ISO or ANSI as mentioned above. Also, work is already underway in ISO/TC 159/SC 4/WG 5 to update ISO16071 in relation to current accessibility legislation (.e.g, US Section 508), ISO and European accessibility standards guidelines together with input from disability organizations. The new standard (renamed Ergonomics of Human System Interaction - Guidance on Software Accessibility) will be a full standard, rather than a Technical Specification, and is planned for publication in early 2006. Richard Hodgkinson is the project editor. The published verions of ISO TS 16071 is based upon a set of US Human Factors Society guidelines (HFES 200?). Are there any W3C process/other issues with referencing an ISO document like this?

NOTE: In terms of techniques for Checkpoints 1.2 to 1.5, the current text looks fine - no major changes.