-
Notifications
You must be signed in to change notification settings - Fork 118
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
directory role deprecation should be written as normative text #2161
Comments
it is written as normative text though. the following precedes the note.
|
How did I miss that? Duh. Anyway, why does it say in the note, "Authors are advised to treat directory as deprecated", which is much less strong. But not a big deal. What about the CORE-AAM mapping? |
yeh, i can see that "advised" could be changed out for another word to make this not seem like it's not actually deprecated. the core aam mapping is unchanged. the use of the role is deprecated, but the role would still map to list (i could see adding a call out in core aam to further mention that the role itself is deprecated though) It's been brought up a few times though, that HTML AAM doesn't list the deprecated/obsolete HTML features and what their mappings should be. So there apparently are some who want to know what the mappings are, even for elements/roles that authors should not be using. |
@tranjocelyn would you be interested in updating the spec to make this more clear? |
Describe the change
There is a
NOTE
underdirectory
role stating thatAuthors are advised to treat directory as deprecated
. Instead it should be written as normative text, likeThis role is deprecated
, and also it should not be in aNOTE
so that it is clear that the role is deprecated.Link to the version of the specification or documentation you were looking at
Link to documentation: https://w3c.github.io/aria/#directory
Does the issue exists in the editors draft (the editors draft is the most recent draft of the specification)? Yes.
Related issue in Core AAM: w3c/core-aam#227
The text was updated successfully, but these errors were encountered: