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

[scottaohara]

@mbgower it looks like the thread over in the apg was about tablist - which does not require a name. tab does require a name though. i think the last paragraph in your previous comment might accidently be confusing the naming required for tab for the not-required naming of tablist?

[mbgower]

Oops, yes, absolutely! Thanks.

[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.