|

DRAFT: Detailed information for UAAG 1.0 evaluations

Editors:

Jon Gunderson, Ian Jacobs

Nearby How to evaluate a user agent for conformance | Implementation Report

Status of this Document

This is a draft document produced as part of work for the User Agent Accessibility Guidelines Working Group. It does not represent consensus within the Working Group.

Last revised: $Date: 2002/03/28 23:36:15 $

Introduction

This document is designed to help people perform implementation reviews of user agent technologies. For each UAAG checkpoint information is provided on how to evelaute the user agent for the checkpoint requirements and the markup for specific specifications that should be implemented and available through the user interface. An evaluation by or in cooperation with a developer greatly facilitates an evaluation and for some UAAG requirements is necessary.

Priority 1 checkpoints

• Checkpoint 1.1 Full keyboard access. (P1) 
  1. Check in the documentation for keyboard short cuts or hot keys
     • Use key word "keyboard" or "short cut" if a documentation search feature is available
     • Check to see if the index or table of contents for keyboard or short cut references
  2. Try Operating System keyboard features for keyboard support (i.e. Using the Alt key to access menu items or tab to navigate dialog box controls in Microsoft Windows)
  3. Identify features of the user agent and check to see if they can be accessed by the keyboard
  4. Ask developer if they designed user agent to have keyboard access to all functionalities
  For both content and user agent. (Techniques for 1.1)
• Checkpoint 1.2 Activate event handlers. (P1) 
  1. On a web resource with know pointer based event handlers, test to see if the pointer based event handlers can be activated through the keyboard commands alone.
     HTML pointer based event handlers typically include:
     • onMouseOver
     • onMouseDown
     • onMouseUp
     • onMouseMove
     • onClick
     • onDBClick
     • onChange
     
     HTML keyboard event handlers typically include:
     • onFocus
     • onBlur
  2. Ask the developer if they designed the user agent to include this functionality
    (Techniques for 1.2)
• Checkpoint 1.3 Provide text messages. (P1) 
  1. Identify a set of user agent events that generate auditory or visual messages to the user.
  2. When an auditory or visual message is generated by the user agent, test to see if it is available in a text format.
  3. Ask the developer if they designed the user agent to include this functionality
    (Techniques for 1.3)
• Checkpoint 2.1 Render content according to specification. (P1) 
  1. Ask the developer if they designed the user agent to include this functionality
    (Techniques for 2.1)
• Checkpoint 2.2 Provide text view. (P1) 
  1. Determine if the user agent supports a text format, based on the type of information it renders or information in its documentation
  2. Ask the developer if they designed the user agent to include this functionality
    (Techniques for 2.2)
• Checkpoint 2.3 Render conditional content. (P1) 
  1. Idenitfy conditional content for the specifications supported by the user agent. For HTML 4.0 a list of conditional content includes:
     • ALT attribute for IMG element
     • TITLE attribute for IMG element
     • LONGDESC attribute for IMG element
     • Content of OBJECT element: not supported Comment 5:
     • ALT attribute for AREA element
     • ALT attribute for INPUT element with type equal "image"
     • ACRONYM element
     • TITLE attribute of ABBR element
     • TITLE attribute of ACRONYM element
     • SUMMARY attribute for TABLE element
     • TITLE attribute for FRAME element: not supported?? Comment 11:
     • LONGDESC attribute for FRAME element
     • NOFRAME
     • NOSCRIPT
  2. Ask the developer if they designed the user agent if they support access through the user interface for each type of conditional content a specification supports and in what conditions the content will be rendered.
  For all content. (Techniques for 2.3)
• Checkpoint 2.4 Allow time-independent interaction. (P1) 
  1. Determine the markup the user agent supports that can be used to limit the time a user has to react to information.
  2. If there is no specific markup (i.e. scripting of a non-specific markup) to time user interaction, the user agent does
  3. Ask the developer if they support this functionality
    (Techniques for 2.4)
• Checkpoint 2.5 Make captions, transcripts available. (P1) 
  1. Ask the developer if they support this functionality
  For all content.
  Content type labels: Video, Audio. (Techniques for 2.5)
• Checkpoint 2.6 Respect synchronization cues. (P1) 
  1. Ask the developer if they support this functionality
   
  Content type labels: Video, Audio. (Techniques for 2.6)
• Checkpoint 3.1 Toggle background images. (P1) 
  1. Ask the developer if they support this functionality
   
  Content type labels: Image. (Techniques for 3.1)
• Checkpoint 3.2 Toggle audio, video, animated images. (P1) 
  1. Ask the developer if they support this functionality
   
  Content type labels: Animation, Video, Audio. (Techniques for 3.2)
• Checkpoint 3.3 Toggle animated/blinking text. (P1) 
  1. Ask the developer if they support this functionality
   
  Content type labels: VisualText. (Techniques for 3.3)
• Checkpoint 3.4 Toggle scripts. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 3.4)
• Checkpoint 3.5 Toggle content refresh. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 3.5)
• Checkpoint 4.1 Configure text size. (P1) 
  1. Ask the developer if they support this functionality
   
  Content type labels: VisualText. (Techniques for 4.1)
• Checkpoint 4.2 Configure font family. (P1) 
  1. Ask the developer if they support this functionality
   
  Content type labels: VisualText. (Techniques for 4.2)
• Checkpoint 4.3 Configure text colors. (P1) 
  1. Ask the developer if they support this functionality
   
  Content type labels: ColorText. (Techniques for 4.3)
• Checkpoint 4.4 Slow multimedia. (P1) 
  1. Ask the developer if they support this functionality
   
  Content type labels: Animation, Audio. (Techniques for 4.4)
• Checkpoint 4.5 Start, stop, pause, and navigate multimedia. (P1) 
  1. Ask the developer if they support this functionality
   
  Content type labels: Animation, Audio. (Techniques for 4.5)
• Checkpoint 4.6 Position captions. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 4.6)
• Checkpoint 4.9 Global volume control. (P1) 
  1. Ask the developer if they support this functionality
   
  Content type labels: Audio. (Techniques for 4.9)
• Checkpoint 4.10 Independent volume control. (P1) 
  1. Ask the developer if they support this functionality
   
  Content type labels: Audio. (Techniques for 4.10)
• Checkpoint 4.12 Configure synthesized speech rate. (P1) 
  1. Allow configuration of the synthesized speech rate, according to the full range offered by the speech synthesizer.
   
  Content type labels: Speech. (Techniques for 4.12)
• Checkpoint 4.13 Configure synthesized speech volume. (P1) 
  1. Ask the developer if they support this functionality
   
  Content type labels: Speech. (Techniques for 4.13)
• Checkpoint 4.14 Configure synthesized speech characteristics. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 4.14)
• Checkpoint 4.17 Choose style sheets. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 4.17)
• Checkpoint 6.1 DOM read access. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 6.1)
• Checkpoint 6.2 DOM write access. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 6.2)
• Checkpoint 6.3 Programmatic access to non-HTML/XML content. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 6.3)
• Checkpoint 6.4 Programmatic operation. (P1) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 6.4)
• Checkpoint 6.5 Programmatic alert of changes. (P1) 
  1. Ask the developer if they support this functionality
  For both content and user agent. (Techniques for 6.5)
• Checkpoint 6.6 Conventional keyboard APIs. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 6.6)
• Checkpoint 6.7 API character encodings. (P1) 
  1. For an API implemented to satisfy requirements of this document, support the character encodings required for that API.
  For both content and user agent. (Techniques for 6.7)
• Checkpoint 7.1 Focus and selection conventions. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 7.1)
• Checkpoint 7.2 Respect input configuration conventions. (P1) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 7.2)
• Checkpoint 8.1 Implement accessibility features. (P1) 
  1. Ask the developer if they support this functionality
  For all content. (Techniques for 8.1)
• Checkpoint 9.1 Provide content focus. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 9.1)
• Checkpoint 9.2 Provide user interface focus. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 9.2)
• Checkpoint 9.3 Move content focus. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 9.3)
• Checkpoint 9.4 Restore history. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 9.4)
• Checkpoint 10.1 Table orientation. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 10.1)
• Checkpoint 10.2 Highlight selection and content focus. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 10.2)
• Checkpoint 10.3 Distinct default highlight styles. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 10.3)
• Checkpoint 10.7 Highlight current viewport. (P1) 
  1. Ask the developer if they support this functionality
    (Techniques for 10.7)
• Checkpoint 11.1 Current user bindings. (P1) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 11.1)
• Checkpoint 12.1 Accessible documentation. (P1) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 12.1)
• Checkpoint 12.2 Document accessibility features. (P1) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 12.2)
• Checkpoint 12.3 Document default bindings. (P1) 
  1. Document the default user agent input configuration (e.g., the default keyboard bindings).
  For user agent features. (Techniques for 12.3)

Priority 2 checkpoints

• Checkpoint 2.7 Repair missing content. (P2) 
  1. Ask the developer if they support this functionality
  For all content. (Techniques for 2.7)
• Checkpoint 3.6 Toggle redirects. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 3.6)
• Checkpoint 3.7 Toggle images. (P2) 
  1. Allow configuration not to render image content.
  2. The user agent may satisfy this checkpoint by making images invisible, but this technique is not recommended.
   
  Content type labels: Image. (Techniques for 3.7)
• Checkpoint 4.7 Slow other multimedia. (P2) 
  1. Ask the developer if they support this functionality
   
  Content type labels: Animation, Audio. (Techniques for 4.7)
• Checkpoint 4.8 Control other multimedia. (P2) 
  1. Ask the developer if they support this functionality
   
  Content type labels: Animation, Audio. (Techniques for 4.8)
• Checkpoint 4.11 Control other volume. (P2) 
  1. Ask the developer if they support this functionality
   
  Content type labels: Audio. (Techniques for 4.11)
• Checkpoint 4.15 Specific synthesized speech characteristics. (P2) 
  1. Ask the developer if they support this functionality
   
  Content type labels: Speech. (Techniques for 4.15)
• Checkpoint 4.16 Configure synthesized speech features. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 4.16)
• Checkpoint 5.1 No automatic content focus change. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 5.1)
• Checkpoint 5.2 Keep viewport on top. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 5.2)
• Checkpoint 5.3 Manual viewport open only. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 5.3)
• Checkpoint 5.4 Selection and focus in viewport. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 5.4)
• Checkpoint 5.5 Confirm form submission. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 5.5)
• Checkpoint 5.6 Confirm fee links. (P2) 
  1. Allow configuration to prompt the user to confirm (or cancel) any payment that results from activation of a fee link.
  2. Configuration is preferred, but is not required if fee links can only ever be activated on explicit user request.
    (Techniques for 5.6)
• Checkpoint 6.8 DOM CSS access. (P2) 
  1. For user agents that implement Cascading Style Sheets (CSS), provide programmatic access to those style sheets in content by conforming to the CSS module of the W3C Document Object Model (DOM) Level 2 Style Specification [DOM2STYLE] and exporting the interfaces it defines.
  2. For the purposes of satisfying this checkpoint, Cascading Style Sheets (CSS) are defined by either CSS Level 1 [CSS1] or CSS Level 2 [CSS2].
    (Techniques for 6.8)
• Checkpoint 6.9 Timely access. (P2) 
  1. Ask the developer if they support this functionality
  For both content and user agent. (Techniques for 6.9)
• Checkpoint 7.3 Operating environment conventions. (P2) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 7.3)
• Checkpoint 7.4 Input configuration indications. (P2) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 7.4)
• Checkpoint 8.2 Conform to specifications. (P2) 
  1. Ask the developer if they support this functionality
  For all content. (Techniques for 8.2)
• Checkpoint 9.5 No events on focus change. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 9.5)
• Checkpoint 9.6 Show event handlers. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 9.6)
• Checkpoint 9.7 Move content focus optimally. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 9.7)
• Checkpoint 9.8 Text search. (P2) 
  1. Ask the developer if they support this functionality
  For all rendered content. (Techniques for 9.8)
• Checkpoint 9.9 Structured navigation. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 9.9)
• Checkpoint 10.4 Highlight special elements. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 10.4)
• Checkpoint 10.5 Outline view. (P2) 
  1. Ask the developer if they support this functionality
    (Techniques for 10.5)
• Checkpoint 11.2 Current author bindings. (P2) 
  1. Ask the developer if they support this functionality
  For all content. (Techniques for 11.2)
• Checkpoint 11.3 Override bindings. (P2) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 11.3)
• Checkpoint 11.4 Single key access. (P2) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 11.4)
• Checkpoint 11.5 Default binding requirements. (P2) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 11.5)
• Checkpoint 11.6 User profiles. (P2) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 11.6)
• Checkpoint 12.4 Document changes. (P2) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 12.4)
• Checkpoint 12.5 Dedicated section on accessibility. (P2) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 12.5)

Priority 3 checkpoints

• Checkpoint 2.8 No repair text. (P3) 
  1. Ask the developer if they support this functionality
  For all content. (Techniques for 2.8)
• Checkpoint 2.9 Render conditional content automatically. (P3) 
  1. Ask the developer if they support this functionality
  For all content. (Techniques for 2.9)
• Checkpoint 2.10 Toggle placeholders. (P3) 
  1. Ask the developer if they support this functionality
    (Techniques for 2.10)
• Checkpoint 2.11 Alert unsupported language. (P3) 
  1. Ask the developer if they support this functionality
    (Techniques for 2.11)
• Checkpoint 5.7 Manual viewport close only. (P3) 
  1. Ask the developer if they support this functionality
    (Techniques for 5.7)
• Checkpoint 9.10 Configure important elements. (P3) 
  1. Ask the developer if they support this functionality
    (Techniques for 9.10)
• Checkpoint 10.6 Provide link information. (P3) 
  1. Ask the developer if they support this functionality
    (Techniques for 10.6)
• Checkpoint 10.8 Indicate rendering progress. (P3) 
  1. Ask the developer if they support this functionality
    (Techniques for 10.8)
• Checkpoint 11.7 Configure tool bars. (P3) 
  1. Ask the developer if they support this functionality
  For user agent features. (Techniques for 11.7)

|

Copyright© 2000 W3C^® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document useand software licensingrules apply.