Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
mbgower opened this issue Jan 14, 2025 · 2 comments
Assignees
Labels
Agenda-Editors editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo

Comments

@mbgower
Copy link

mbgower commented Jan 14, 2025

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.

Note that in the editor's draft, the row has been added to tab, but the value given is incorrect.

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

@mbgower mbgower added the editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo label Jan 14, 2025
@scottaohara
Copy link
Member

@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?

@pkra pkra self-assigned this Jan 14, 2025
@mbgower
Copy link
Author

mbgower commented Jan 15, 2025

Oops, yes, absolutely! Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Agenda-Editors editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo
Projects
None yet
Development

No branches or pull requests

3 participants