-
Notifications
You must be signed in to change notification settings - Fork 125
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
Missing role=presentation for "Name from prohibited" #2073
Comments
Note from the call: check other synonyms (img/image) as well. Related: #2076 |
As Rahim already indicated, we need to enable aria.js (in aria-common) to pick up on synonyms. Would it be enough to look up synonyms and add their links parenthetically? E.g., "image (synonyms: img)" or some better wording along those lines. |
This should probably transfer to aria-common but it might be more sensible to preview the changes in a PR here first. |
Describe your concern
While reviewing 5.2.8.6 Roles which cannot be named (Name prohibited), I noticed that the role
none
is in the list but notpresentation
. I assumed that since they are synonyms, that listing one or the other is OK however, the 5.3.3 Document Structure Roles section lists bothnone
/presentation
.My concern is that a quick glance of section 5.2.8.6 may yield a false impression that the
presentation
role can be named, and that it's not a true alias fornone
.I tried to add the
presentation
role in section 5.2.8.6 as a simple<li>
however, it looks like the list is dynamically generated byaria/common/script/aria.js
using the characteristics table for each role's definition inaria/index.html
(and the "Name From: " row and whether it is "prohibited"); this appears to be whypresentation
is missing from 5.2.8.6 because thepresentation
role definition has no characteristics table unlike thenone
role definition.Should
presentation
/none
always be listed together (like in 5.3.3)? And should thepresentation
role definition have the same characteristics table asnone
?Link to the version of the specification or documentation you were looking at at.
Link to documentation: https://w3c.github.io/aria/
Does the issue exists in the editors draft (the editors draft is the most recent draft of the specification)?
Yes
The text was updated successfully, but these errors were encountered: