Which accessible name requirements in WAI-ARIA are also WCAG requirements? #355
Description
According to WAI-ARIA, a bunch of things has to have accessible names, which could result in all of these rules, that are not yet otherwise covered:
- Alertdialog has name
- Application has name
- Columnheader has name
- Dialog has name
- Grid has name
- Gridcell has name
- Heading has name
- Log has name
- Marquee has name
- Option has name
- Progressbar has name
- Radiogroup has name
- Region has name
- Rowheader has name
- Table has name
- Tabpanel has name
- Timer has name
- Tooltip has name
- Tree has name
- Treegrid has name
- Treeitem has name
(look for "Accessible Name Required" marked as "True" in https://www.w3.org/TR/wai-aria-1.1/)
... but success criterion 4.1.2 Name, Role, Value is limited to "user interface components":
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
I have at least these three questions for this:
- Which of the above can be considered user interface components and falls under 4.1.2?
- And does any of them fall under another success criterion too/instead?
- If some of them are required in WCAG terms, can they then be grouped into bigger rules in a meaningful way? (like e.g. the "form field has name" rule)