Replies: 1 comment
-
|
I close this discussion as this is already addressed in #4252 and #4234 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am seeking clarification on the exact scope of the terms "control" and "user interface component" within the WCAG 2.2 definitions.
In 4.1.2, the link to the "user interface component" definition states:
And in 1.1.1 (Non-text Content) says:
Without this definition, my usual interpretation would have been that a UI component includes anything with a non-presentational role (even if not interactive), whereas a control would imply something actionable (buttons, links, form fields, etc.). But since the definition of 'UI component' itself uses the word 'control', the terminology in 1.1.1 would feel ambiguous if control had a broader sense.
Could you confirm if my understanding aligns with the W3C intent : is a UI component equivalent to a widget as defined in ARIA? And so is a "control"?
See also 2.4.10 Section Headings
Here the use of user interface components for receiving "headings" is quite ambiguous with the definition...
Beta Was this translation helpful? Give feedback.
All reactions