diff --git a/_baselines/05Changing.md b/_baselines/05Changing.md index a5a171a3..c8110c62 100644 --- a/_baselines/05Changing.md +++ b/_baselines/05Changing.md @@ -1,8 +1,8 @@ --- -title: "5. Changing Content" +title: "5. User Controls" order-number: 6 --- -## 5. Changing Content +## 5. User Controls ### Accessibility Requirements @@ -10,63 +10,95 @@ order-number: 6 ### Test Method Rationale -The purpose of this Baseline test is to identify visual changes to content and component states that occur without a page refresh and to correlate those changes with equivalent programmatic and/or textual information. Notification of such changes must be provided. -- Content changes could include component state changes (e.g., closed/open sections, sort order, collapsed/expanded menus), dynamic and/or calculated values (e.g., "34 characters remaining"), and automatically updating content (e.g., stock prices). -- Content that changes in the course of a user's interaction with the content (including, but not limited to changes in text, component states, structure, relationships, or functionality) must provide a means by which the change in content is programmatically determinable or is otherwise available in text. +The purpose of this Baseline test is to check the following accessibility properties of user controls: +- Name +- Role (test not yet available) +- State +- Value ### Limitations, Assumptions, or Exceptions -- The state of form elements (checked, unchecked, etc.) are included in this Baseline. -- User initiated changes and automatic updates are included in this test. -- If an ARIA live region is used to provide programmatic notification of changes in content, a value of `"off"` for an `aria-live` attribute is ***NOT*** sufficient to provide programmatic notification (whether implicitly or explicitly defined). +- [User interface component (as defined by WCAG)](https://www.w3.org/TR/WCAG21/#dfn-user-interface-components) is a part of the content that is perceived by users as a single control for a distinct function. User interface components include form elements and links as well as components generated by scripts. This test uses the term "user controls" for brevity. +- The accessibility properties of the user control must be correct if the user control changes. -### 5.1 Test Procedure for Changes in Content +### 5.1 Test Procedure for Control Name + +**Baseline Test ID:** 5.1-ChangedControlName -**Baseline Test ID:** 5.1-ChangeContent #### Identify Content -

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.

- +

Identify user controls for a distinct function. Exclude forms and links as these are covered by [Baseline 10. Forms](../10Forms), [Baseline 14. Links](../14Links), respectively.

+ #### Test Instructions
    -
  1. Check that the page provides a notification of the change in content programmatically. [SC 4.1.2] - +
  2. Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
    3. +
  3. Check that the non-empty combination of the accessible name and accessible description describes the control's purpose. [SC 4.1.2] For details on the computation of the accessible name and accessible description, references include: +
    4. -
  4. 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] -
      -
    1. Name: the name is accurate after a change. - -
      2. -
    2. Role: the role accurately describes the purpose of the element after a change, if applicable. -
        -
      • Consider ARIA role, element type, and other descriptive text.
        • -
      -
      3. -
    3. State: the state of the element is accurate after a change, if applicable. -
        -
      • Evaluate ARIA and element-specific attributes (e.g., <option selected=”true”>).
        • -
      -
      4. -
    4. Value: the value is updated after a change, if applicable.
      5. -
    +
  5. If the name of the user control changes with use of the application, repeat the previous test steps and check that the accessible name is correct after the change. +
#### Test Results -

If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.

+ +

If any of the above checks fail, then Baseline Test 5.1-ControlName fails.

+ +### 5.2 Test Procedure for Control Role (not available) + +### 5.3 Test Procedure for Control State + +**Baseline Test ID:** 5.2-ControlState +#### Identify Content +

Identify user controls for a distinct function. Examples include changes to forms, links, and toggle controls.

+ + +#### Test Instructions +
    +
  1. Check that the state of the user control is correct. Attributes such as hidden, disabled, and the use of ARIA to control component states must be used correctly.[SC 4.1.2]
    2. +
  2. If the state of the user control changes with use of the application, check that the state of the user control is correct after a change of state. [SC 4.1.2] + +
    3. +
+ +#### Test Results + +

If any of the above checks fail, then Baseline Test 5.2-ControlState fails.

+ +### 5.3 Test Procedure for Control Value + +**Baseline Test ID:** 5.3-ControlValue +#### Identify Content +

Identify controls that have a value that can be changed by a user. Examples include form fields and sliders.

+ +#### Test Instructions +
    +
  1. Check that the value of the user control is correct. [SC 4.1.2]
    2. +
  2. Modify the value of the user control. Depending on the control, a change of value may be performed by entering a number, selecting from a list of options, etc.
    3. +
  3. Check that the value of the user control is correct after a change of value. [SC 4.1.2]
    4. +
+ +#### Test Results + +

If any of the above checks fail, then Baseline Test 5.3-ControlValue fails.

### Advisory: Tips for streamlined test processes -- Changing content might also include changes in color to convey information. If so, this test should check that the information is programmatically determinable. If color is used as the only visual means of conveying information (or changes in information), then the content would fail to meet SC 1.4.1 Use of Color (addressed in [Baseline 7. Sensory Characteristics](../07Sensory). -- The number of event notifications can be very large; if the number of changes to an element is unknown or very large, a sampling approach may be necessary. -- Although an ARIA live region with an `aria-live` attribute set to `"off"` is not sufficient to provide programmatic notification of content changes, a web page may provide the user with an option to change the value of the `aria-live` politeness setting to provide desired level of notification. Such an option must meet all of the requirements defined in [20. Conforming Alternate Version](../20AlternateVersions) in order to be considered a "conforming alternate version". It would be helpful to provide instructions for the tester to change the aria-live from "off" before testing the page. +- Changes to controls may also include changes in color to convey information. If so, this test should check that the information is programmatically determinable. If color is used as the only visual means of conveying information (or changes in information), then the content would fail to meet SC 1.4.1 Use of Color (addressed in [Baseline 7. Sensory Characteristics](../07Sensory)). +- The accessible name and accessible description of some user controls are tested in other Baseline tests, such as [Baseline 10. Forms](../10Forms), [Baseline 14. Links](../14Links). For user controls that have dedicated Baseline Tests, please map to those tests for accessible name instead of 5.1-ControlName. +- This test may require interaction with controls to assess changes in name, role, state, value. Interaction instructions such as a test plan may be helpful. #### WCAG 2.0 Techniques - [F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur](https://www.w3.org/WAI/WCAG21/Techniques/failures/F20.html) diff --git a/_baselines/10Forms.md b/_baselines/10Forms.md index 7125fe54..d33e10a0 100644 --- a/_baselines/10Forms.md +++ b/_baselines/10Forms.md @@ -49,7 +49,7 @@ Review form instructions for completeness and programmatic association to their #### Test Instructions
  1. Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
    2. -
  2. Check that the non-empty combination of the accessible name and accessible description describes the form's purpose. [SC 1.1.1] For details on the computation of the accessible name and accessible description, references include: +
  3. Check that the non-empty combination of the accessible name and accessible description describes the form's purpose. [SC 4.1.2] [Form components that include non-text content should also map to SC 1.1.1.] For details on the computation of the accessible name and accessible description, references include: