-
Notifications
You must be signed in to change notification settings - Fork 38
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
Review ARIA 1.3 #341
Comments
tl;dr: All good IMHO. More detailed notes below. A couple of actions:
Major feature in this release
All good IMHO. There is a note to deter people from using this unless it's really required, and the extra responsibilities they take on by using it.
All good IMHO. This will be great! Being able to link the suggestion with further contextual info will be great too. There are strict requirements on child elements' roles - this seems OK as it matches similar rules for e.g.
All good IMHO. There is a naming inconsistency vs
All good IMHO. This too will be great. It's good that it's a subclass of
All good IMHO. Slight concern about over-use (or rather under-use of descriptive text in the DOM for everyone), but I don't think that will be as prominent as with Wondering whether there should be slightly stronger encouragement to use the ID-referencing versions of both name and description attributes, and slightly stronger discouragement of the flat-string ones, but that is a minor issue. The point about whether flat strings could make translations harder was raised. There is a section on Translatable Attributes - and this actually shows up what appears to be a bug, as
All good IMHO.
All good IMHO. There is a note to deter people from using this unless it's really required, and the extra responsibilities they take on by using it. Wondering if a stronger note against the use of Substantive changes since ARIA 1.2I've reviewed all of the changes, and have no concerns. There are some particularly helpful changes for both AT vendors, AT users, and implementers here. |
@mbeganyi-a11y, @fredrika11y: Further to my comment directly above, item 1 of our potential TODOs (that That leaves the second question from the tl;dr bit at the top of my comment (i.e. whether slightly stronger discouragement from using If we do decide to submit something, we should check the issues in the ARIA repo first. |
https://github.com/search?q=repo%3Avalidator%2Fvalidator+aria-label&type=issues issues would probably another source of were the current guidance gets misunderstood |
Opened by matatk via IRC channel #apa on irc.w3.org
Due: 2024-02-15 (Thursday 15 February)
Spec review request: w3c/a11y-request#72
Significant changes since ARIA 1.2.
The text was updated successfully, but these errors were encountered: