-
Notifications
You must be signed in to change notification settings - Fork 355
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
Draft guidance on aria-details #70
Comments
Aside from the obvious examples of descriptions being hidden by default, it would be valuable to see examples of descriptions displayed by default. (This is a request from George Kerscher on behalf of DAISY et al) |
… 1050 (pull #1062) * Fallback naming guidance section: reference cardinal rule 4 to avoid it. * Naming Rule 3: Remove mention of alt attribute: Per feedback from @LJWatson in issue #1050, revises rule 3 to remove mention of alt. * Adds sentence refering readers to the naming techniques for specific advantages of using HTML features instead of ARIA. * Fix formatting and bugs in code snippets reported in #1060. * Intro: most fundamental and important -> most important * Minor editorial change to section: How Are Name and Description Strings Derived? * Intro paragraph: additional editorial simplification based on feedback from @LJWatson in issue #1050. * Clarify language describing when captions become descriptions: to resolve feedback from @jessebeach in issue #1050. Modified language in sections 5.3.2.6 Naming Tables and Figures with Captions and section 5.4.1.3 Describing Tables and Figures with Captions. * Provide richer description of screen reader behavior in section 5.1 per feedback from @jongund in issue #1050. * Remove aria-details guidance, which will be addressed in the future by issue #70.
This is now critical for the spec with the changes for annotations to support multiple idrefs Content to support this can be taken from https://github.com/aleventhal/aria-annotations |
#994 covers aria-details and has been merged. Can this issue be closed? |
@zcorpan I see this was done but do not see it in the latest editors draft https://w3c.github.io/aria-practices/#describing_techniques |
Looks like #1062 removed it |
Ah right, OK. Thanks. |
Biggest problem for general usage of |
aria-details is new to ARIA 1.1. It would be very useful to include best practices for
details
, especially as opposed todescribed-by
. Members of DPUB can be called upon to assist or provide samples.The text was updated successfully, but these errors were encountered: