Evaluation Form for UAAG

Can I use this form?
This form can be used to generate XML on the client side if your browser supports JavaScript and DOM 2 XML (see the box below).
It will generate XML on the server side otherwise.

Please use How to Evaluate a User Agent for Conformance to UAAG 1.0 for guidance.

User Agent Information





Reviewer Information











1.1: Full keyboard access. (Priority 1)

Show comments

1.1.1: Ensure that the user can operate through keyboard input alone any user agent functionality available through the user interface.
Show comments

HTML 4.01 UAAG Test Suite for ACCESSKEY attribute for BUTTON
Show comments

HTML 4.01 UAAG Test Suite for ACCESKEY attribute for TEXTAREA
Show comments

HTML 4.01 UAAG Test Suite for FRAME and FRAMESET
Show comments

HTML 4.01 UAAG Test Suite for TABINDEX
Show comments

HTML 4.01 UAAG Test Suite for ACCESSKEY attribute for CHECKBOX
Show comments

HTML 4.01 UAAG Test Suite for ACCESSKEY
Show comments

HTML 4.01 UAAG Test Suite for IFRAME
Show comments

HTML 4.01 UAAG Test Suite for TEXTAREA
Show comments

HTML 4.01 UAAG Test Suite for ACCESSKEY attribute for INPUT buttons
Show comments

HTML 4.01 UAAG Test Suite for BUTTON
Show comments

HTML 4.01 UAAG Test Suite for INPUT buttons
Show comments

HTML 4.01 UAAG Test Suite for ACCESSKEY attribute for RADIO buttons
Show comments

HTML 4.01 UAAG Test Suite for CHECKBOXES
Show comments

HTML 4.01 UAAG Test Suite for RADIO buttons
Show comments

1.2: Activate event handlers. (Priority 1)

Show comments

1.2.1: Allow the user to activate, through keyboard input alone, all event handlers that are explicitly associated with the element designated by the content focus.
Show comments

HTML 4.01 UAAG Test Suite for ONCHANGE attribute for INPUT elements
Show comments

HTML 4.01 UAAG Test Suite for ONCLICK and ONDBCLICK
Show comments

HTML 4.01 UAAG Test Suite for ONFOCUS and ONBLUR attributes for BUTTON elements
Show comments

HTML 4.01 UAAG Test Suite for ONCHANGE attribute for SELECT elements
Show comments

HTML 4.01 UAAG Test Suite for ONFOCUS and ONBLUR attributes for INPUT elements
Show comments

HTML 4.01 UAAG Test Suite for ONCHANGE attribute for TEXTAREA elements
Show comments

HTML 4.01 UAAG Test Suite for ONFOCUS and ONBLUR attributes for LABEL elements
Show comments

HTML 4.01 UAAG Test Suite for ONFOCUS and ONBLUR attributes for links
Show comments

1.2.2: In order to satisfy provision one of this checkpoint, the user must be able to activate as a group all event handlers of the same input device event type.
Show comments

HTML 4.01 UAAG Test Suite for Multiple Event Handlers for ONCHANGE Attribute for SELECT Elements
Show comments

HTML 4.01 UAAG Test Suite for ONFOCUS and ONBLUR attributes for MAP elements
Show comments

HTML 4.01 UAAG Test Suite for ONFOCUS and ONBLUR attributes for TEXTAREA elements
Show comments

HTML 4.01 UAAG Test Suite for Multiple Event Handlers for ONMOUSEOVER and ONMOUSEOUT
Show comments

HTML 4.01 UAAG Test Suite for Multiple Event Handlers for ONCLICK and ONDBCLICK
Show comments

HTML 4.01 UAAG Test Suite for ONFOCUS and ONBLUR attributes for links
Show comments

HTML 4.01 UAAG Test Suite for ONMOUSEOVER and ONMOUSEOUT
Show comments

1.3: Provide text messages. (Priority 1)

Show comments

1.3.1: Ensure that every message (e.g., prompt, alert, notification, etc.) that is a non-text element and is part of the user agent user interface has a text equivalent.
Show comments

2.1: Render content according to specification. (Priority 1)

Show comments

2.1.1: Render content according to format specification (e.g., for a markup language or style sheet language).
Show comments

2.2: Provide text view. (Priority 1)

Show comments

2.2.1: For content authored in text formats, provide a view of the text source. For the purposes of this checkpoint, a text format is any media object given an Internet media type of "text" (e.g., "text/plain", "text/html", or "text/*") as defined in RFC 2046 [RFC2046], section 4.1.
Show comments

2.3: Render conditional content. (Priority 1)

Show comments

2.3.1: Allow configuration to provide access to each piece of unrendered conditional content "C".
Show comments

HTML 4.01 UAAG Test Suite for ABBR elements
Show comments

HTML 4.01 UAAG Test Suite for ACRONYM elements
Show comments

HTML 4.01 UAAG Test Suite for ALT attribute for AREA elements
Show comments

HTML 4.01 UAAG Test Suite for ALT attribute for AREA elements
Show comments

HTML 4.01 UAAG Test Suite for LONGDESC attribute for FRAME elements
Show comments

HTML 4.01 UAAG Test Suite for TITLE attribute for FRAME elements
Show comments

HTML 4.01 UAAG Test Suite for IFRAME conditional content
Show comments

HTML 4.01 UAAG Test Suite for ALT, TITLE, and LONGDESC attributes for IMG element
Show comments

HTML 4.01 UAAG Test Suite for ALT attribute for INPUT elements
Show comments

HTML 4.01 UAAG Test Suite for TITLE attribute for MAP element
Show comments

HTML 4.01 UAAG Test Suite for NOFRAMES elements
Show comments

HTML 4.01 UAAG Test Suite for NOSCRIPT conditional content
Show comments

HTML 4.01 UAAG Test Suite for OBJECT element for audio
Show comments

HTML 4.01 UAAG Test Suite for OBJECT element for images
Show comments

HTML 4.01 UAAG Test Suite for OBJECT element for video
Show comments

HTML 4.01 UAAG Test Suite for TH elements and the SCOPE attribute for TH elements
Show comments

HTML 4.01 UAAG Test Suite for SUMMARY attribute for TABLE elements
Show comments

2.3.2: When a specification does not explain how to provide access to this content, do so as follows: If C is a summary, title, alternative, description, or expansion of another piece of content D, provide access through at least one of the following mechanisms: (1a) render C in place of D; (2a) render C in addition to D; (3a) provide access to C by allowing the user to query D. In this case, the user agent must also alert the user, on a per-element basis, to the existence of C (so that the user knows to query D); (4a) allow the user to follow a link to C from the context of D. Otherwise, provide access to C through at least one of the following mechanisms: (1b) render a placeholder for C, and allow the user to view the original author-supplied content associated with each placeholder; (2b) provide access to C by query (e.g., allow the user to query an element for its attributes). In this case, the user agent must also alert the user, on a per-element basis, to the existence of C; (3b) allow the user to follow a link in context to C.
Show comments

HTML 4.01 UAAG Test Suite for ABBR elements
Show comments

HTML 4.01 UAAG Test Suite for ACRONYM elements
Show comments

HTML 4.01 UAAG Test Suite for ALT attribute for AREA elements
Show comments

HTML 4.01 UAAG Test Suite for ALT attribute for AREA elements
Show comments

HTML 4.01 UAAG Test Suite for LONGDESC attribute for FRAME elements
Show comments

HTML 4.01 UAAG Test Suite for TITLE attribute for FRAME elements
Show comments

HTML 4.01 UAAG Test Suite for IFRAME conditional content
Show comments

HTML 4.01 UAAG Test Suite for ALT, TITLE, and LONGDESC attributes for IMG element
Show comments

HTML 4.01 UAAG Test Suite for ALT attribute for INPUT elements
Show comments

HTML 4.01 UAAG Test Suite for TITLE attribute for MAP element
Show comments

HTML 4.01 UAAG Test Suite for NOFRAMES elements
Show comments

HTML 4.01 UAAG Test Suite for NOSCRIPT conditional content
Show comments

HTML 4.01 UAAG Test Suite for OBJECT element for audio
Show comments

HTML 4.01 UAAG Test Suite for OBJECT element for images
Show comments

HTML 4.01 UAAG Test Suite for OBJECT element for video
Show comments

HTML 4.01 UAAG Test Suite for TH elements and the SCOPE attribute for TH elements
Show comments

HTML 4.01 UAAG Test Suite for SUMMARY attribute for TABLE elements
Show comments

2.4: Allow time-independent interaction. (Priority 1)

Show comments

2.4.1: For rendered content where user input is only possible within a finite time interval controlled by the user agent, allow configuration to provide a view where user interaction is time-independent.
Show comments

2.5: Make captions, transcripts, audio descriptions available. (Priority 1)

Show comments

2.5.1: Allow configuration or control to render text transcripts, collated text transcripts, captions, and audio descriptions in content at the same time as the associated audio tracks and visual tracks.
Show comments

2.6: Respect synchronization cues. (Priority 1)

Show comments

2.6.1: Respect synchronization cues (e.g., in markup) during rendering.
Show comments

2.7: Repair missing content. (Priority 2)

Show comments

2.7.1: Allow configuration to generate repair text when the user agent recognizes that the author has failed to provide conditional content that was required by the format specification.
Show comments

HTML 4.01 UAAG Test Suite for repairing missing ALT conditional content for AREA
Show comments

HTML 4.01 UAAG Test Suite for repair missing TITLE attribute for FRAME elements
Show comments

HTML 4.01 UAAG Test Suite for repairing missing IFRAME conditional content
Show comments

HTML 4.01 UAAG Test Suite for repairing missing ALT conditional content for images
Show comments

HTML 4.01 UAAG Test Suite for repairing missing ALT conditional content for INPUT
Show comments

HTML 4.01 UAAG Test Suite for repairing missing TITLE conditional content for MAP elements
Show comments

HTML 4.01 UAAG Test Suite for repairing missing NOFRAMES elements
Show comments

HTML 4.01 UAAG Test Suite for repairing missing OBJECT element conditional content for audio
Show comments

HTML 4.01 UAAG Test Suite for repairing missing OBJECT element conditional content for images
Show comments

HTML 4.01 UAAG Test Suite for repairing missing OBJECT element conditional content for video
Show comments

2.8: No repair text. (Priority 3)

Show comments

2.8.1: Allow at least two configurations for when the user agent recognizes that conditional content required by the format specification is present but empty content: generate no repair text, or generate repair as described in checkpoint 2.7.
Show comments

HTML 4.01 UAAG Test Suite for No Repair Text for the ALT attribute for AREA elements
Show comments

HTML 4.01 UAAG Test Suite for No Repair Text for the ALT attribute for IMG elements
Show comments

HTML 4.01 UAAG Test Suite for No Repair Text for the ALT attribute for INPUT elements
Show comments

2.9: Render conditional content automatically. (Priority 3)

Show comments

2.9.1: Allow configuration to render all conditional content automatically.
Show comments

2.9.2: As part of satisfying provision one of this checkpoint, provide access according to specification, or where unspecified, by applying one of the techniques 1a, 2a, or 1b defined in checkpoint 2.3.
Show comments

2.10: Don't render unsupported language. (Priority 3)

Show comments

2.10.1: Allow configuration not to render text in unsupported scripts (i.e., writing systems) when that text would otherwise be rendered.
Show comments

2.10.2: When configured per provision one of this checkpoint, indicate to the user in context that author-supplied content has not been rendered.
Show comments

3.1: Toggle background images. (Priority 1)

Show comments

3.1.1: Allow configuration not to render background image content.
Show comments

HTML 4.01 UAAG Test Suite for BACKGROUND images in the BODY element
Show comments

HTML 4.01 UAAG Test Suite for BACKGROUND-IMAGE in the STYLE element
Show comments

HTML 4.01 UAAG Test Suite for DIV BACKGROUND-IMAGE in the STYLE element
Show comments

3.2: Toggle audio, video, animated images. (Priority 1)

Show comments

3.2.1: Allow configuration not to render audio, video, or animated image content, except on explicit user request.
Show comments

3.3: Toggle animated or blinking text. (Priority 1)

Show comments

3.3.1: Allow configuration to render animated or blinking text content as motionless, unblinking text. Blinking text is text whose visual rendering alternates between visible and invisible, at any rate of change.
Show comments

HTML 4.01 UAAG Test Suite for BLINK
Show comments

HTML 4.01 UAAG Test Suite for TEXT-DECORATION:BLINK in the STYLE element
Show comments

HTML 4.01 UAAG Test Suite for MARQUEE
Show comments

3.4: Toggle scripts. (Priority 1)

Show comments

3.4.1: Allow configuration not to execute any executable content (e.g., scripts and applets).
Show comments

3.5: Toggle automatic content retrieval. (Priority 1)

Show comments

3.5.1: Allow configuration so that the user agent only retrieves content on explicit user request.
Show comments

HTML 4.01 UAAG Test Suite for META HTTP-EQUIV redirect
Show comments

HTML 4.01 UAAG Test Suite for META HTTP-EQUIV refresh
Show comments

3.6: Toggle images. (Priority 2)

Show comments

3.6.1: Allow configuration not to render image content.
Show comments

HTML 4.01 UAAG Test Suite for IMG toggle
Show comments

HTML 4.01 UAAG Test Suite for OBJECT images toggle
Show comments

4.1: Configure text scale. (Priority 1)

Show comments

4.1.1: Allow global configuration of the scale of visually rendered text content. Preserve distinctions in the size of rendered text as the user increases or decreases the scale.
Show comments

HTML 4.01 UAAG Test Suite for font-size
Show comments

4.1.2: As part of satisfying provision one of this checkpoint, provide a configuration option to override rendered text sizes specified by the author or user agent defaults.
Show comments

HTML 4.01 UAAG Test Suite for font-size
Show comments

4.1.3: As part of satisfying provision one of this checkpoint, offer a range of text sizes to the user that includes at least: the range offered by the conventional utility available in the operating environment that allows users to choose the text size (e.g., the font size), or if no such utility is available, the range of text sizes supported by the conventional APIs of the operating environment for drawing text.
Show comments

HTML 4.01 UAAG Test Suite for font-size
Show comments

4.2: Configure font family. (Priority 1)

Show comments

4.2.1: Allow global configuration of the font family of all visually rendered text content.
Show comments

HTML 4.01 UAAG Test Suite for font-family
Show comments

4.2.2: As part of satisfying provision one of this checkpoint, provide a configuration option to override font families specified by the author or by user agent defaults.
Show comments

HTML 4.01 UAAG Test Suite for font-family
Show comments

4.2.3: As part of satisfying provision one of this checkpoint, offer a range of font families to the user that includes at least: the range offered by the conventional utility available in the operating environment that allows users to choose the font family, or if no such utility is available, the range of font families supported by the conventional APIs of the operating environment for drawing text.
Show comments

4.3: Configure text colors. (Priority 1)

Show comments

4.3.1: Allow global configuration of the foreground and background color of all visually rendered text content.
Show comments

HTML 4.01 UAAG Test Suite for font colors and backgrounds
Show comments

4.3.2: As part of satisfying provision one of this checkpoint, provide a configuration option to override foreground and background colors specified by the author or user agent defaults.
Show comments

HTML 4.01 UAAG Test Suite for font colors and backgrounds
Show comments

4.3.3: As part of satisfying provision one of this checkpoint, offer a range of colors to the user that includes at least: the range offered by the conventional utility available in the operating environment that allows users to choose colors, or if no such utility is available, the range of colors supported by the conventional APIs of the operating environment for specifying colors.
Show comments

4.4: Slow multimedia. (Priority 1)

Show comments

4.4.1: Allow the user to slow the presentation rate of rendered audio and animation content (including video and animated images).
Show comments

4.4.2: As part of satisfying provision one of this checkpoint, for a visual track, provide at least one setting between 40% and 60% of the original speed.
Show comments

4.4.3: As part of satisfying provision one of this checkpoint, for a prerecorded audio track including audio-only presentations, provide at least one setting between 75% and 80% of the original speed.
Show comments

4.4.4: When the user agent allows the user to slow the visual track of a synchronized multimedia presentation to between 100% and 80% of its original speed, synchronize the visual and audio tracks (per checkpoint 2.6). Below 80%, the user agent is not required to render the audio track.
Show comments

4.5: Start, stop, pause, and navigate multimedia. (Priority 1)

Show comments

4.5.1: Allow the user to stop, pause, and resume rendered audio and animation content (including video and animated images) that last three or more seconds at their default playback rate.
Show comments

4.5.2: Allow the user to navigate efficiently within audio and animations (including video and animated images) that last three or more seconds at their default playback rate.
Show comments

4.6: Do not obscure captions. (Priority 1)

Show comments

4.6.1: For graphical viewports, allow configuration so that captions synchronized with a visual track in content are not obscured by it.
Show comments

4.7: Global volume control. (Priority 1)

Show comments

4.7.1: Allow global configuration of the volume of all rendered audio, with an option to override audio volumes specified by the author or user agent defaults.
Show comments

4.7.2: As part of satisfying provision one of this checkpoint, allow the user to choose zero volume (i.e., silent).
Show comments

4.8: Independent volume control. (Priority 1)

Show comments

4.8.1: Allow independent control of the volumes of rendered audio content synchronized to play simultaneously.
Show comments

4.9: Configure synthesized speech rate. (Priority 1)

Show comments

4.9.1: Allow configuration of the synthesized speech rate, according to the full range offered by the speech synthesizer.
Show comments

4.10: Configure synthesized speech volume. (Priority 1)

Show comments

4.10.1: Allow control of the synthesized speech volume, independent of other sources of audio.
Show comments

4.11: Configure synthesized speech characteristics. (Priority 1)

Show comments

4.11.1: Allow configuration of synthesized speech characteristics according to the full range of values offered by the speech synthesizer.
Show comments

4.12: Specific synthesized speech characteristics. (Priority 2)

Show comments

4.12.1: Allow configuration of synthesized speech pitch. Pitch refers to the average frequency of the speaking voice.
Show comments

4.12.2: Allow configuration of synthesized speech pitch range. Pitch range specifies a variation in average frequency.
Show comments

4.12.3: Allow configuration of synthesized speech stress. Stress refers to the height of "local peaks" in the intonation contour of the voice.
Show comments

4.12.4: Allow configuration of synthesized speech richness. Richness refers to the richness or brightness of the voice.
Show comments

4.13: Configure synthesized speech features. (Priority 2)

Show comments

4.13.1: Provide support for user-defined extensions to the synthesized speech dictionary.
Show comments

4.13.2: Provide support for spell-out: where text is spelled one character at a time, or according to language-dependent pronunciation rules.
Show comments

4.13.3: Allow at least two configurations for speaking numerals: one where numerals are spoken as individual digits, and one where full numbers are spoken.
Show comments

4.13.4: Allow at least two configurations for speaking punctuation: one where punctuation is spoken literally, and one where punctuation is rendered as natural pauses.
Show comments

4.14: Choose style sheets. (Priority 1)

Show comments

4.14.1: Allow the user to choose from and apply alternative author style sheets (such as linked style sheets).
Show comments

4.14.2: Allow the user to choose from and apply at least one user style sheet.
Show comments

4.14.3: Allow the user to ignore author and user style sheets.
Show comments

5.1: No automatic content focus change. (Priority 2)

Show comments

5.1.1: Allow configuration so that if a viewport opens without explicit user request, neither its content focus nor its user interface focus automatically becomes the current focus.
Show comments

5.2: Keep viewport on top. (Priority 2)

Show comments

5.2.1: For graphical user interfaces, allow configuration so that the viewport with the current focus remains "on top" of all other viewports with which it overlaps.
Show comments

5.3: Manual viewport open only. (Priority 2)

Show comments

5.3.1: Allow configuration so that viewports only open on explicit user request.
Show comments

5.3.2: When configured per provision one of this checkpoint, instead of opening a viewport automatically, alert the user and allow the user to open it with an explicit request (e.g., by confirming a prompt or following a link generated by the user agent).
Show comments

5.3.3: Allow the user to close viewports.
Show comments

5.4: Selection and focus in viewport. (Priority 2)

Show comments

5.4.1: Ensure that when a viewport's selection or content focus changes, it is at least partially in the viewport after the change.
Show comments

5.5: Confirm form submission. (Priority 2)

Show comments

5.5.1: Allow configuration to prompt the user to confirm (or cancel) any form submission.
Show comments

6.1: Programmatic access to HTML/XML infoset. (Priority 1)

Show comments

6.1.1: Provide programmatic read access to XML content by making available all of the information items defined by the W3C XML Infoset [INFOSET].
Show comments

6.1.2: Provide programmatic read access to HTML content by making available all of the following information items defined by the W3C XML Infoset [INFOSET]: Document Information item: children, document element, base URI, charset Element Information items: element-type name, children, attributes, parent Attribute Information items: attribute-type name, normalized value, specified, attribute type, references, owner element Character Information items: character code, parent element Comment Information items: content, parent
Show comments

6.1.3: If the user can modify HTML and XML content through the user interface (e.g., through form controls), allow for the same modifications programmatically.
Show comments

6.2: DOM access to HTML/XML content. (Priority 1)

Show comments

6.2.1: As part of satisfying checkpoint , conform to the following modules of the W3C Document Object Model DOM Level 2 Core Specification [DOM2CORE] and exporting bindings for the interfaces they define: for HTML: the Core module. for XML: the Core and XML modules.
Show comments

6.2.2: As part of satisfying provision one of this checkpoint, Export the normative bindings specified in the DOM Level 2 Core Specification [DOM2CORE] (namely, for Java [JAVA] and ECMAScript [ECMASCRIPT] operating environments). For other environments, the bindings exported to satisfy provision one of this checkpoint (e.g., C++ bindings) must be publicly documented.
Show comments

6.3: Programmatic access to non-HTML/XML content. (Priority 1)

Show comments

6.3.1: For content other than HTML and XML, provide structured programmatic read access to content, and write access to those parts of content that the user can modify through the user interface.
Show comments

6.3.2: As part of satisfying provision one of this checkpoint, implement at least one API according to this API cascade: The API is defined by a W3C Recommendation, or the API is publicly documented and designed to enable interoperability with assistive technologies. If no such API is available, or if available APIs do not enable the user agent to satisfy the requirements, implement at least one publicly documented API to satisfy the requirements, and follow operating environment conventions for the use of input and output APIs.
Show comments

6.4: Programmatic access to rendering structure. (Priority 1)

Show comments

6.4.1: For graphical user agents, provide programmatic read access to visually rendered information.
Show comments

6.4.2: As part of satisfying provision one of this checkpoint, implement at least one API according to the API cascade described in provision two of checkpoint 6.3.
Show comments

6.5: Programmatic operation of user agent user interface. (Priority 1)

Show comments

6.5.1: Provide programmatic read access to user agent user interface controls.
Show comments

6.5.2: Provide programmatic write access for those user agent user interface controls that the user can modify through the user interface.
Show comments

6.5.3: As part of satisfying provisions one and two of this checkpoint, implement at least one API according to the API cascade described in provision two of checkpoint 6.3.
Show comments

6.6: Programmatic notification of changes. (Priority 1)

Show comments

6.6.1: Provide programmatic notification of changes to content, user interface controls, selection, content focus, and user interface focus.
Show comments

6.6.2: As part of satisfying provision one of this checkpoint, implement at least one API according to the API cascade of provision two of checkpoint .
Show comments

6.7: Conventional keyboard APIs. (Priority 1)

Show comments

6.7.1: Implement APIs for the keyboard as follows: Follow operating environment conventions. If no conventions exist, implement publicly documented APIs.
Show comments

6.8: API character encodings. (Priority 1)

Show comments

6.8.1: For an API implemented to satisfy requirements of this document, support the character encodings required for that API.
Show comments

6.9: DOM access to CSS style sheets. (Priority 2)

Show comments

6.9.1: For user agents that implement Cascading Style Sheets (CSS), provide programmatic access to style sheets by conforming to the CSS module of the W3C Document Object Model (DOM) Level 2 Style Specification [DOM2STYLE] and exporting bindings for the interfaces it defines.
Show comments

6.9.2: As part of satisfying provision one of this checkpoint: Export the normative bindings specified in the CSS module of the DOM) Level 2 Style Specification [DOM2STYLE] (namely, for Java [JAVA] and ECMAScript [ECMASCRIPT] operating environments). For other environments, the bindings exported to satisfy provision one of this checkpoint must be publicly documented.
Show comments

6.10: Timely exchanges through APIs. (Priority 2)

Show comments

6.10.1: For APIs implemented to satisfy the requirements of this document, ensure that programmatic exchanges proceed in a timely manner.
Show comments

7.1: Respect focus and selection conventions. (Priority 1)

Show comments

7.1.1: Follow operating environment conventions that benefit accessibility when implementing the selection, content focus, and user interface focus.
Show comments

7.2: Respect input configuration conventions. (Priority 1)

Show comments

7.2.1: Ensure that default input configurations of the user agent do not interfere with operating environment accessibility conventions (e.g., for keyboard accessibility).
Show comments

7.3: Respect operating environment conventions. (Priority 2)

Show comments

7.3.1: Follow operating environment conventions that benefit accessibility. In particular, follow conventions that benefit accessibility for user interface design, keyboard configuration, product installation, and documentation.
Show comments

7.4: Provide input configuration indications. (Priority 2)

Show comments

7.4.1: Follow operating environment conventions to indicate the input configuration.
Show comments

8.1: Implement accessibility features. (Priority 1)

Show comments

8.1.1: Implement the accessibility features of specifications (markup languages, style sheet languages, metadata languages, graphics formats, etc.).
Show comments

8.2: Conform to specifications. (Priority 2)

Show comments

8.2.1: Use and conform to either W3C Recommendations when they are available and appropriate for a task, or non-W3C specifications that enable the creation of content that conforms at level A or better to the Web Content Accessibility Guidelines 1.0 [WCAG10].
Show comments

9.1: Provide content focus. (Priority 1)

Show comments

9.1.1: Provide at least one content focus for each viewport (including frames) where enabled elements are part of the rendered content.
Show comments

9.1.2: Allow the user to make the content focus of each viewport the current focus.
Show comments

9.2: Provide user interface focus. (Priority 1)

Show comments

9.2.1: Provide a user interface focus.
Show comments

9.3: Move content focus. (Priority 1)

Show comments

9.3.1: Allow the user to move the content focus to any enabled element in the viewport.
Show comments

9.3.2: Allow configuration so that the content focus of a viewport only changes on explicit user request.
Show comments

9.3.3: If the author has not specified a navigation order, allow at least forward sequential navigation, in document order, to each element in the set established by provision one of this checkpoint.
Show comments

9.4: Restore viewport state history. (Priority 1)

Show comments

9.4.1: For user agents that implement a viewport history mechanism, for each state in a viewport's browsing history, maintain information about the point of regard, content focus, and selection.
Show comments

9.4.2: When the user returns to any state in the viewport history (e.g., via the "back button"), restore the saved values for the point of regard, content focus, and selection.
Show comments

9.5: No events on focus change. (Priority 2)

Show comments

9.5.1: Allow configuration so that moving the content focus to or from an enabled element does not automatically activate any explicitly associated event handlers of any event type.
Show comments

9.6: Show event handlers. (Priority 2)

Show comments

9.6.1: For the element with content focus, make available the list of input device event types for which there are event handlers explicitly associated with the element.
Show comments

HTML 4.01 UAAG Test Suite for Listing Element Event Handlers
Show comments

9.7: Move content focus in reverse. (Priority 2)

Show comments

9.7.1: Extend the functionality required in provision three of checkpoint 9.3 by allowing the same sequential navigation in reverse document order.
Show comments

9.7.2: As part of satisfying provision one of this checkpoint, the user agent must not include disabled elements in the navigation order.
Show comments

9.8: Provide text search. (Priority 2)

Show comments

9.8.1: Allow the user to search within rendered text content for a sequence of characters from the document character set.
Show comments

9.8.2: Allow the user to start a forward search (in document order) from any selected or focused location in content.
Show comments

9.8.3: When there is a match, do both of the following: move the viewport so that the matched text content is within it, and allow the user to search for the next instance of the text from the location of the match.
Show comments

9.8.4: Alert the user when there is no match or after the last match in content (i.e., prior to starting the search over from the beginning of content).
Show comments

9.8.5: Provide a case-insensitive search option for text in scripts (i.e., writing systems) where case is significant.
Show comments

9.9: Allow structured navigation. (Priority 2)

Show comments

9.9.1: Allow the user to navigate efficiently to and among important structural elements in rendered content.
Show comments

HTML 4.01 UAAG Test Suite for Form navigation
Show comments

HTML 4.01 UAAG Test Suite for Heading navigation
Show comments

HTML 4.01 UAAG Test Suite for Anchor navigation
Show comments

HTML 4.01 UAAG Test Suite for LIST ITEM navigation
Show comments

HTML 4.01 UAAG Test Suite for TABLE CAPTION navigation
Show comments

HTML 4.01 UAAG Test Suite for TABLE HEADER navigation
Show comments

9.9.2: As part of satisfying provision one of this checkpoint, allow forward and backward sequential navigation.
Show comments

HTML 4.01 UAAG Test Suite for Form navigation
Show comments

HTML 4.01 UAAG Test Suite for Heading navigation
Show comments

HTML 4.01 UAAG Test Suite for Anchor navigation
Show comments

HTML 4.01 UAAG Test Suite for LIST ITEM navigation
Show comments

HTML 4.01 UAAG Test Suite for TABLE CAPTION navigation
Show comments

HTML 4.01 UAAG Test Suite for TABLE HEADER navigation
Show comments

9.10: Configure important elements. (Priority 3)

Show comments

9.10.1: Allow configuration of the set of important elements and attributes identified in checkpoints and .
Show comments

9.10.2: As part of satisfying provision one of this checkpoint, allow the user to include and exclude element types in the set.
Show comments

10.1: Associate table cells and headers. (Priority 1)

Show comments

10.1.1: For graphical user agents that render tables, for each table cell, allow the user to view associated header information.
Show comments

HTML 4.01 UAAG Test Suite for the ABBR attribute for TH elements
Show comments

HTML 4.01 UAAG Test Suite for AXIS attribute for table cells
Show comments

HTML 4.01 UAAG Test Suite for CAPTION
Show comments

HTML 4.01 UAAG Test Suite for COL and COLGROUP
Show comments

HTML 4.01 UAAG Test Suite for SCOPE
Show comments

HTML 4.01 UAAG Test Suite for SUMMARY attribute for TABLE element
Show comments

HTML 4.01 UAAG Test Suite for TD headers attribute
Show comments

HTML 4.01 UAAG Test Suite for navigating THEAD, TBODY, TFOOT with CSS overflow styling
Show comments

10.2: Highlight selection, content focus, enabled elements, visited links. (Priority 1)

Show comments

10.2.1: Allow global configuration to highlight the following four classes of information in each viewport: the selection, content focus, enabled elements, and recently visited links.
Show comments

HTML 4.01 UAAG Test Suite for Highlight Styles
Show comments

10.2.2: For graphical user interfaces, as part of satisfying provision one of this checkpoint, allow at least one configuration where the highlight mechanisms for the four classes of information: differ from each other, and do not rely on rendered text foreground and background colors alone.
Show comments

HTML 4.01 UAAG Test Suite for Highlight Styles
Show comments

10.2.3: For graphical user interfaces, as part of satisfying provision one of this checkpoint, if a highlight mechanism involves text size, font family, rendered text foreground and background colors, or text decorations, offer at least the following range of values: for text size, the range required by provision three of checkpoint 4.1. for font family, the range required by provision three of checkpoint 4.2. for text foreground and background colors and decorations, the range offered by the conventional utility available in the operating environment for users to choose rendered text colors or decorations (e.g., the standard font and color dialog box resources supported by the operating system). If no such utility is available, the range supported by the conventional APIs of the operating environment for specifying text colors or drawing text.
Show comments

10.2.4: Highlight enabled elements according to the granularity specified in the format. For example, an HTML user agent rendering a PNG image as part of a client-side image map is only required to highlight the image as a whole, not each enabled region. An SVG user agent rendering an SVG image with embedded graphical links is required to highlight each (enabled) link that may be rendered independently according to the SVG specification.
Show comments

10.3: Single highlight configuration. (Priority 2)

Show comments

10.3.1: Extend the functionality required by provision two of checkpoint 10.2 by allowing configuration through a single setting.
Show comments

10.4: Provide outline view. (Priority 2)

Show comments

10.4.1: Make available to the user an "outline" view of content, composed of labels for important structural elements (e.g., heading text, table titles, form titles, and other labels that are part of the content).
Show comments

HTML 4.01 UAAG Test Suite for Outline View of the CAPTION attribute for TABLE elements
Show comments

HTML 4.01 UAAG Test Suite for Outline View of the TITLE attribute for FORM elements
Show comments

HTML 4.01 UAAG Test Suite for Outline View of Headings
Show comments

HTML 4.01 UAAG Test Suite for Outline View of Mixed Structural Elements
Show comments

10.5: Provide link information. (Priority 3)

Show comments

10.5.1: To help the user decide whether to traverse a link in content, make available the following information about it: link element content, link title, whether the link is internal to the resource (e.g., the link is to a target in the same Web page), whether the user has traversed the link recently, and information about the type, size, and natural language of linked Web resources.
Show comments

10.6: Highlight current viewport. (Priority 1)

Show comments

10.6.1: Allow global configuration to highlight the viewport with the current focus (including any frame that takes current focus).
Show comments

10.6.2: For graphical viewports, as part of satisfying provision one of this checkpoint, allow at least one configuration where the highlight mechanism does not rely on rendered text foreground and background colors alone (e.g., use a thick outline).
Show comments

10.6.3: If the techniques used to satisfy provision one of this checkpoint involve rendered text size, font family, rendered text foreground and background colors, or text decorations, offer the same ranges of values required by provision three of checkpoint .
Show comments

10.7: Indicate viewport position. (Priority 3)

Show comments

10.7.1: Indicate the viewport's position relative to rendered content (e.g., the proportion of an audio or video clip that has been played, the proportion of a Web page that has been viewed, etc.).
Show comments

11.1: Current user input configuration. (Priority 1)

Show comments

11.1.1: Provide information to the user about current user preferences for input configurations.
Show comments

11.2: Current author input configuration. (Priority 2)

Show comments

11.2.1: Provide a centralized view of the current author-specified input configuration.
Show comments

11.3: Allow override of bindings. (Priority 2)

Show comments

11.3.1: Allow the user to override any binding that is part of the user agent default input configuration.
Show comments

11.4: Single-key access. (Priority 2)

Show comments

11.4.1: Allow the user to override any binding in the user agent default keyboard configuration with a binding to either a key plus modifier keys or to a single key.
Show comments

11.4.2: For each functionality in the set required by checkpoint 11.5, allow the user to configure a single-key binding. A single-key binding is one where a single key press performs the task, with zero modifier keys.
Show comments

11.5: Default input configuration. (Priority 2)

Show comments

11.5.1: Ensure that the user agent default input configuration includes bindings for the following functionalities required by other checkpoints in this document: move content focus to the next enabled element in document order, and move content focus to the previous enabled element in document order (checkpoints and ); activate the link designed by the content focus (checkpoints and ); search for text, search again for same text (checkpoint ); increase the scale of rendered text, and decrease the scale of rendered text (checkpoint 4.1); increase global volume, and decrease global volume (checkpoint 4.7); stop, pause, resume, and navigate efficiently selected audio and animations, including video and animated images (checkpoint 4.5).
Show comments

User Agent Bindings for Activating Links
Show comments

User Agent Bindings for Moving Focus to Enabled Elements
Show comments

User Agent Bindings for Searching for Text
Show comments

User Agent Bindings for Changing Text Size
Show comments

11.5.2: If the user agent supports the following functionalities, the default input configuration must also include bindings for them: next history state (forward), and previous history state (back); enter URI for a new resource; add a URI to favorites (i.e., bookmarked resources); view favorites; reload a resource; interrupt a request to reload a resource; for graphical viewports: navigation forward and backward through rendered content by approximately the height of the viewport; for user agents that render content in lines of (at least) text: move point of regard to next line, and previous line.
Show comments

11.6: User profiles. (Priority 2)

Show comments

11.6.1: For the configuration requirements of this document, allow the user to save user preferences in at least one user profile.
Show comments

11.6.2: Allow the user to choose from among available user agent default profiles, profiles created by the same user, and no profile (i.e., the user agent default settings).
Show comments

11.7: Tool bar configuration. (Priority 3)

Show comments

11.7.1: For graphical user agent user interfaces with tool bars, allow the user to configure the position of controls on those tool bars.
Show comments

11.7.2: Offer a predefined set of controls that may be added to or removed from tool bars.
Show comments

11.7.3: Allow the user to restore the default tool bar configuration.
Show comments

12.1: Provide accessible documentation. (Priority 1)

Show comments

12.1.1: Ensure that at least one version of the user agent documentation conforms to at least level Double-A of the Web Content Accessibility Guidelines 1.0 [WCAG10].
Show comments

12.2: Document accessibility features. (Priority 1)

Show comments

12.2.1: Document all user agent features that benefit accessibility.
Show comments

12.3: Document default bindings. (Priority 1)

Show comments

12.3.1: Document the default user agent input configuration (e.g., the default keyboard bindings).
Show comments

12.4: Document changes between versions. (Priority 2)

Show comments

12.4.1: Document changes from the previous version of the user agent to features that benefit accessibility, including features of the user interface.
Show comments

12.5: Provide dedicated accessibility section. (Priority 2)

Show comments

12.5.1: Provide a centralized view of all features of the user agent that benefit accessibility, in a dedicated section of the documentation.
Show comments

Submit optionsClick on the submit button to send your results to us via email.
Click on "Generate Report" to render the XML into the textarea.
(Uses mailto: link; server-based parser coming soon [as of 8 Aug 02])
Generate Report (appears in textarea below)