UAAG 1.0 Test Suite for HTML 4.01

Disclaimers

This test suite does not represent a consensus of the working group.

This test suite attempts to represent all the accessibility features of HTML 4.01, but should not be considered as a definitive list. Comments on the current or additional tests should be sent to the editors.

This test suite maybe useful in conducting a conformance review of a user agent, but is not sufficient for determining if all requirements have been satisified for making a conformance claim. For instance, a test may illustrate that a functionality is implemented, but that test may be sufficient but not necessary to satisfy the checkpoint.

This test suite is considered an informative resource of the UAWG and may change at anytime without notice.

References

The following resources are used to represent the information for each test and convert the test to an HTML format. Each of the test in the following section includes a link to the XML test document. The TS.XSL transform is used to convert the XML representation to HTML.

Provision 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. For example, if there are 10 handlers associated with the onmousedown event type, the user must be able to activate the entire group of 10 through keyboard input alone, and must not be required to activate each handler separately.

Provision 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); and (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; and (3b) allow the user to follow a link in context to C.

Provision 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.

Provision 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.

Provision 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. generate repair as described in checkpoint 2.7.

Provision 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 provision two of checkpoint 2.3.

Provision 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.

Provision 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.

Provision 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.

Provision 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.

Provision 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.

Provision 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.

Provision 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).

Provision 3:
If the user can modify the state or value of a piece of HTML or XML content through the user interface (e.g., by checking a box or editing a text area), allow programmatic read access to the current state or value, and allow the same degree of write access programmatically as is available through the user interface.

Provision 1:
Provide access to the content required in checkpoint 6.1 by conforming 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

Provision 2:
As part of satisfying provision one of this checkpoint: In the Java and ECMAScript operating environments, export the normative bindings specified in the DOM Level 2 Core Specification [DOM2CORE], or In other operating environments, the exported bindings (e.g., C++) must be publicly documented.

Provision 1:
For content other than HTML and XML, provide structured programmatic read access to content.

Provision 2:
If the user can modify the state or value of a piece of non-HTML/XML content through the user interface (e.g., by checking a box or editing a text area), allow programmatic read access to the current state or value, and allow the same degree of write access programmatically as is available through the user interface.

Provision 3:
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.

Provision 1:
For graphical user agents, make available bounding dimensions and coordinates of rendered graphical objects. Coordinates must be relative to the point of origin in the graphical environment (e.g., with respect to the desktop), not the viewport.

Provision 2:
For graphical user agents, provide access to the following information about each piece of rendered text: font family, font size, and foreground and background colors.

Provision 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.

Provision 2:
If the user can modify the state or value of a user agent user interface control (e.g., by checking a box or editing a text area), allow programmatic read access to the current state or value, and allow the same degree of write access programmatically as is available through the user interface.

Provision 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.

Provision 2:
As part of satisfying provision one of this checkpoint: In the Java and ECMAScript operating environments, export the normative bindings specified in the CSS module of the DOM Level 2 Style Specification [DOM2STYLE], or In other operating environments, the exported bindings (e.g., C++) must be publicly documented.

Provision 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].

Provision 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.

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

Provision 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.

Provision 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.

Provision 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.

Provision 1:
Make available to the user an "outline" view of rendered 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).

Provision 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.

Provision 2:
For graphical viewports, as part of satisfying provision one of this checkpoint, provide at least one highlight mechanism that does not rely on rendered text foreground and background colors alone (e.g., use a thick outline).

Provision 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, allow global configuration and offer same ranges of values required by provision three of checkpoint 10.2.

Provision 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.

Provision 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.

Provision 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 9.3 and 9.7); activate the link designated by the content focus (checkpoints 1.1 and 9.1); search for text, search again for same text (checkpoint 9.8); 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); and stop, pause, resume, and navigate efficiently selected audio and animations, including video and animated images (checkpoint 4.5).

Provision 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 a URI for a new resource; add a URI to favorites (i.e., bookmarked resources); view favorites; reload a resource; interrupt a request to load or reload a resource; for graphical viewports: navigate forward and backward through rendered content by approximately the height of the viewport; and for user agents that render content in lines of (at least) text: move the point of regard to the next and previous line.