Test Case Summary

Test Case ID

TCID: TC05.1-all-pass-3

TC Version: 1

Baseline Version: 3.1

Applicable Standard:

Test Case Description

This page has a button and a paragraph describing when to press the button.

When the button is pressed, an error message appears at the top of the page saying that the user pressed the button too early.

When the error message appears, focus shifts to the error message container.

A successful test should identify a PASS against Baseline 5.1 Changing Content.

Applicable ICT Baseline Test

Baseline test procedure 5.1 was not found in the baseline data.

Test Instruction: all

Test Case Detail

Expected Baseline Result

Pass

After content change, notification of the change is provided by a focus shift to the changed content.

Test Data

Single-Page URL

Test Case Instruction

Test Instruction Instruction Detail Expected Test Case Result
IC-1 Identify changes in presented content (both user driven and automatic). Examples include changes to images, navigation trees, data table sort controls, automatic information updates, form elements, revealed content, etc. It may be necessary to use the mouse to determine whether state changes occur on hover or on click. Depending on the component, a change of state may be triggered by various actions, such as changing values or states of other components, toggling a function, entering data in the component, mouseover, etc. Identify that there is a button. Activate the button and observe for changes to content.
1 Check that the page provides a notification of the change in content programmatically. [SC 4.1.2] Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions. Pass: When the content changes, focus is shifted to the changed content.
2 For each change in content, check that the combination of name, role, state, and value of the changed content is accurate. [SC 4.1.2] Pass: The combination of name, role, state, and value of the changed content is accurate.