Skip to main content
RAWEBA

7.1 Is each script, if necessary, compatible with assistive technologies?

WCAG references
  • 2.5.3 Label in Name (A)
  • 4.1.2 Name, Role, Value (A)
Techniques
  • ARIA4
  • ARIA5
  • ARIA18
  • ARIA19
  • F15
  • F19
  • F20
  • F42
  • F59
  • F79
  • F96
  • G10
  • G135
  • G136
  • G208
  • G211
  • SCR21

Official methodology to test criterion 7.1

Test 1 (7.1.1)

  1. Find all the user interface components generated or controlled using JavaScript in the document.
  2. Check that
    • The component has a role consistent with its use (generally a button or a link).
    • The component has an explicit name.
    • The name of the component is consistent with the state of the feature or controlled content (for example, for a feature that displays or hides a content block).
  3. If not, check that there is an accessible user interface component providing access to the same feature.
  4. If not, check for the presence of an accessible alternative providing access to the same feature.
  5. If this is the case, the test is validated.

Test 2 (7.1.2)

  1. For each user interface component that has passed test 7.1.1, check that the user interface component is correctly rendered (by assistive technologies).
  2. If not, check that an accessible alternative to the user interface component provides access to the same feature.
  3. If this is the case, the test is validated.

Test 3 (7.1.3)

  1. For each user interface component that has passed test 7.1.1, check that the user interface component has
    • a relevant name;
    • a relevant role.
  2. If the user interface component has an accessible name, check that this name is relevant and contains at least the visible label.
  3. If this is the case, the test is validated.