Add Accessible Name Required row to each role's characteristics table where it is missing

[mbgower]

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

[jnurthen]

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]

Related: #1263 and its stale PR #1733.

[smockle]

IMO this is missing from section 5.2 where "Accessible Name Required" should be listed as one of the Characteristics of Roles.

§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]

“Accessible Name Required” rows used to list “False”. This changed in 2021 via #1477, which implemented #1466:

name true, false, n/a

In the characteristics table, "Accessible Name Required" is marked as "true", "false" and also not at all for some roles which can be named. I would expect that it be "true" for all instances of roles which require a name. False for all roles which can be named, but do not require a name. Roles which prohibit naming would not need this table row

action item

All roles which require names need to be marked as "Accessible name required: true". All roles which can be named but do not require a name either need to be consistently marked as "Accessible name required: false" or not have that row displayed.