Implementation Tests for User Agent Accessibility Guidelines 1.0

Priority 1 Tests | Priority 2 Tests | Priority 3 Tests

Note: This is a placeholder index for the Implementation Tests for User Agent Accessibility Guidelines 1.0. It is expected to be replaced by an index containing the text of each checkpoint. This index exists solely to allow members of the User Agent Accessibility Guidelines Working Group (UAWG), and other interested parties, the opportunity to review, comment upon, and contribute to individual test documents as they are constructed. A proposed test template is also available.

The following ACCESSKEYS have been defined for this page:
Priority One Tests: 1
Priority Two Tests: 2
Priority Three Tests: 3

Tests of Priority 1 Checkpoints

Checkpoint 2.1 Render by specification. Render content according to specification. When a rendering requirement of another specification explicitly contradicts a requirement of the current document, the user agent may disregard the rendering requirement of the other specification and still satisfy this checkpoint. Content only (Techniques for 2.1)
Checkpoints Contained in IFRAME

Checkpoint 3.3 Toggle animated/blinking text. Allow configuration to render animated or blinking text as motionless, unblinking text. Content only (Techniques for 3.3)
Labels: VisualText
Blinking Test 1: Blinking Controlled by Proprietary Markup
Blinking Test 2: Blinking Controlled by CSS
Scrolling Test 1: Scrolling Controlled by the Proprietary Element MARQUEE
Scrolling Test 2: Scrolling Controlled by JavaScript

Checkpoint 9.1 Provide content focus. Provide at least one content focus for each viewport (including frames) where enabled elements are part of the rendered content. Allow the user to make the content focus of each viewport the current focus. Content only (Techniques for 9.1)
Checkpoints Contained in IFRAME


Tests of Priority 2 Checkpoints

Checkpoint 3.6 Toggle redirects. Allow configuration so that a "client-side redirect" (i.e., one initiated by the user agent, not the server) does not change content except on explicit user request. Allow the user to access the new content on demand (e.g., by following a link or confirming a prompt). The user agent is not required to provide these functionalities for client-side redirects that occur instantaneously (i.e., when there is no delay before the new content is retrieved). Content only (Techniques for 3.6)
Redirect Test 1: Client-Side Redirection Using HTTP-EQUIV="refresh"
Redirect Test 2: Instant Redirection Using HTTP-EQUIV="refresh"

Checkpoint 5.1 No automatic content focus change. Allow configuration so that if a viewport opens without explicit user request, its content focus does not automatically become the current focus. Configuration is not required if the content focus can only ever be moved by explicit user request. Both (Techniques for 5.1)
NEW! New Viewport Caused by target="new"

Checkpoint 5.2 Keep viewport on top. 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. Both (Techniques for 5.2)
NEW! New Viewport Caused by target="new"

Checkpoint 5.3 Manual viewport open only. Allow configuration so that viewports only open on explicit user request. In this configuration, instead of opening a viewport automatically, alert the user and allow the user to open it on demand (e.g., by following a link or confirming a prompt). Allow the user to close viewports. If a viewport (e.g., a frame set) contains other viewports, these requirements only apply to the outermost container viewport. Both (Techniques for 5.3)
OnChange Attached to SELECT Opens New Viewport (Form Test C of N)
OnFocus Event Handler Opens New Viewport (Form Test F of N)
NEW! New Viewport Caused by target="new"

Checkpoint 5.4 Selection and focus in viewport. Ensure that when a viewport's selection or content focus changes, it is at least partially in the viewport after the change. Both (Techniques for 5.4)
NEW! New Viewport Caused by target="new"

Checkpoint 5.5 Confirm form submission. Allow configuration to prompt the user to confirm (or cancel) any form submission that is not caused by an explicit user request to activate a form submit control. Content only (Techniques for 5.5)
Form Test A of N: Single-Field Form with OnChange Event Handler, No Submit Mechanism
Form Test B of N: Single-Field Form with OnChange Event Handler & Submit Mechanism
Form Test C of N: OnChange Attached to SELECT Opens New Viewport
Form Test D of N: Single-Field Form with OnFocus Event Handler
Form Test E of N: Single-Field Form with OnFocus Event Handler & SUBMIT Mechanism
Form Test F of N: OnFocus Event Handler Opens New Viewport

Checkpoint 9.5 Move focus without activation. Allow configuration so that moving the content focus to an enabled element does not automatically activate any explicitly associated input device event handlers. Content only (Techniques for 9.5)
Form Test A of N: Single-Field Form with OnChange Event Handler, No Submit Mechanism
Form Test B of N: Single-Field Form with OnChange Event Handler & Submit Mechanism
Form Test C of N: OnChange Attached to SELECT Opens New Viewport
Form Test D of N: Single-Field Form with OnFocus Event Handler
Form Test E of N: Single-Field Form with OnFocus Event Handler & SUBMIT Mechanism
Form Test F of N: OnFocus Event Handler Opens New Viewport

Checkpoint 9.6 Show event handlers. For the element with content focus, make available the list of input device event handlers explicitly associated with the element. Content only (Techniques for 9.6)
Form Test A of N: Single-Field Form with OnChange Event Handler, No Submit Mechanism
Form Test B of N: Single-Field Form with OnChange Event Handler & Submit Mechanism
Form Test C of N: OnChange Attached to SELECT Opens New Viewport
Form Test D of N: Single-Field Form with OnFocus Event Handler
Form Test E of N: Single-Field Form with OnFocus Event Handler & SUBMIT Mechanism
Form Test F of N: OnFocus Event Handler Opens New Viewport


Tests of Priority 3 Checkpoints

Checkpoint 2.10 Alert unsupported language. Allow configuration not to render content in unsupported natural languages (including scripts, i.e., writing systems). Indicate to the user in context that author-supplied content has not been rendered. Content only (Techniques for 2.10)
Indicating Changes in Natural Language With CSS


Terminal Index
1) User Agent Accessibility Guidelines Working Group (UAWG)
2) Web Accessibility Initiative (WAI)
3) World Wide Web Consortium (W3C)
4) send comments and observations to w3c-wai-ua@w3.org

W3C Validated XHTML 1.0!     W3C Validated CSS!


last updated at 4:05 AM 5/31/2001 by Gregory J. Rosmaita; target="new" tests added 3:14 AM 5/31/2001

Copyright ©  2001 W3C (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.