What is the WCAG definition of "component"?

[jha11y]

The word "component"/"components" is used 92 times in WCAG 2.2, but it does not seemed to be explicitly defined.

This makes the definition of User Interface Component a little unclear, specific note 3 under this term:

What is meant by "component" or "user interface component" here is also sometimes called "user interface element".

Is there a difference between user interface component (interactive control?) vs component (element?)

The word component is used in success criterion that include content that is not interactive such as Success Criterion 1.3.3 Sensory Characteristics:

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.

[jha11y]

related issue: #4234

[mbgower]

** Draft Working Group Response**
First, there is a definition for user interface component, so in any success criterion or paragraph of normative content where that defined term is used and the word "component" occurs within the same context, "component" is clearly intended to be a synonym. For instance:

User Interface Components
Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;

Second, although there are 92 occurrences of the word "component" in the specification, not all are used in the sense of a user interface component. Some are meant in the abstract non-technology sense. For example:

• For an overview of how these components of web development and interaction work together, see...
• Required Components of a Conformance Claim

A better way to assess a potential problem space is where the word "component" appears in normative text where it does not appear in association with the defined term "user interface component". There are 5 criteria where this occurs:

• 2.1.2 No Keyboard Trap
• 2.4.3 Focus Order
• 2.4.13 Focus Appearance
• 3.2.4 Consistent Identification
• 1.3.3 Sensory Characteristics

Given that No Keyboard Trap, Focus Order, and Focus Appearance are all about interaction, the context seems very clear, and does not seem to create a problem. The language of Consistent Identification states "Components that have the same functionality, which again makes it clear it is about something that can be operated. So the only one that is potentially unclear is the one you flagged, Sensory Characteristics.

As per your quote of its normative text, Sensory Characteristics covers both "understanding and operating". As well, the examples in the Understanding document cover both operation of buttons and a situation where a user is interpretting the information in a table. If "component" was used strictly in the sense of user interface component, it would actually restrict the scope of this requirement. It would only cover instructions about operation. The first example concerning interpreting colour on a non-operable schedule would no longer be valid.

If you think we should add additional context in this Understanding document to clarify it does not apply only to instructions for user interface components, please confirm. Also, feel free to provide suggestions.

There are also 6 definition where the word occurs without a link to the definition

• label
• minimum bounding box
• name
• role
• synchronized media
• viewport (uses "interface components" without linking to definition)

Almost all of the occurrences of these defined terms happen within the context of user interface components. Label could be considered an exception to this, since it also is used normatively in Headings and Labels, which are typically not operable. If you believe we should add additional context in this Understanding document, and where, please let us know.

.