Repository navigation
Add Accessible Name Required row to each role's characteristics table where it is missing #2411
Description
Describe the change
As per comments in w3c/aria-practices#3211, currently only roles where an accessible name is required have an Accessible Name Required row, with a value pair set to "True".
Roles where accessible name is not required do not have a matching row. Users are left to understand that a role without this value pair have an inferred row of "false".
For those who are not intimately familiar with such a convention, I believe each role's characteristics table should contain an Accessible Name Required row, with either a true/false or less binary value.
Link to the version of the specification or documentation you were looking at
Link to documentation: https://www.w3.org/TR/wai-aria-1.3/ and https://www.w3.org/TR/wai-aria-1.2/
Does the issue exists in the editors draft (the editors draft is the most recent draft of the specification)?
Yes
Activity
scottaohara commentedon Jan 14, 2025
mbgower commentedon Jan 15, 2025
jnurthen commentedon Jan 22, 2025
IMO this is missing from section 5.2 where
"Accessible Name Required" should be listed as one of the Characteristics of Roles.
This should make it clear that if it is not listed then it is not required.
We should also check all the other characteristics are present and clean them up at the same time.
pkra commentedon Feb 11, 2025
Related: #1263 and its stale PR #1733.
smockle commentedon Feb 13, 2025
§5.2.8.4 “Roles Supporting Name from Author” and §5.2.8.5 “Roles Supporting Name from Content” sort of address this now, by placing “(name required)” beside roles that require an accessible name.
Adding a new “Accessible Name Required” section would make those parentheticals redundant, so we should consider removing them at the same time.
smockle commentedon Feb 13, 2025
“Accessible Name Required” rows used to list “False”. This changed in 2021 via #1477, which implemented #1466:
mbgower commentedon Mar 10, 2025
There's not much of a rationale for why it was removed listed there, and I think there is demonstrated benefit to returning to the pre-2021 version where each role indicates it (i.e., people were confused enough by the missing name required row that they implemented/interpreted incorrectly)
jnurthen commentedon Mar 10, 2025
@mbgower It wasn't removed - it was made consistent. Most roles have never had false specified. It was erroneously specified on 5 roles as False which were removed to make the spec consistent.