Roles, values, states, properties available

foundational

Normative Text

Accurate names, roles, values, and states are available for interactive elements.

Methods & best practices

Method (HTML): use HTML elements according to specification.
Method (ARIA): add roles, values, states, and properties according to specification.

Tests

This section is non-normative.

Procedure

For each interactive element:

Inspect the code and accessibility tree (when available) to confirm that the role, value, state, and properties (when applicable) are indicated.

Expected results

#1 is true.

Tests

This content needs to be written.

Key Terms

accessibility support set: group of user agents and assistive technologies you test with

The AGWG is considering defining a default set of user agents and assistive technologies that they use when validating guidelines.
Accessibility support sets may vary based on language, region, or situation.
If you are not using the default accessibility set, the conformance report should indicate what set is being used.
accessibility supported: available and working in the user agents and assistive technology in the accessibility support set

The working group intended to include a default accessibility support set. See Default accessibility support set #277.
interactive element: element that responds to user input and has a distinct programmatically determinable name

Buttons, controls, input fields.

In contrast to non-interactive elements. For example, headings or paragraphs.
non-interactive element: element that does not respond to user input and does not include sub-parts

Text, an image, a video, and if they have no sub-elements: a paragraph, list item, and table cell.

If a paragraph included a link, the text either side of the link would be considered a static element, but not the paragraph as a whole.

Letters within text do not constitute a “smaller part”.
programmatically determinable: meaning of the content and all its important attributes can be determined by software functionality that is accessibility supported
state: dynamic property expressing characteristics of a user interface component that may change in response to user action or automated processes

States represent data associated with the component or user interaction possibilities. They do not affect the nature of the component. Examples include focus, hover, select, press, check, visited/unvisited, and expand/collapse.
user interface component: To be defined.