-
Notifications
You must be signed in to change notification settings - Fork 249
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
Need links to Understanding docs for guidelines #595
Comments
Not quite sure from where you mean links are needed. If, for instance, you're on https://www.w3.org/TR/WCAG21/#text-alternatives, there are links in the boxout right there to the understanding and "how to meet" documents, pointing directly to the correct place. |
and there's a link to the main entry point for the understanding doc in the front matter section of the WCAG https://www.w3.org/TR/WCAG21/#wcag-2-1-supporting-documents |
ah, now I get you. sorry, misread and thought you meant individual SCs. so yes, having some link from the guideline itself to https://www.w3.org/WAI/WCAG21/Understanding/text-alternatives ... makes sense |
Those may not be used as much, and it is possible to get to them, but it takes a little work. I noticed in particular when I was looking for GL 1.2. A link right below the permalink, like with the SCs, would be very helpful. |
Unfortunately these are in the Recommendation so we may not be able to fix immediately. I assigned Michael to this as he will handle this in the generator. |
We can fix this when we do the Edited Recommendation, which will probably be soonish. |
Approved in survey and on call: https://www.w3.org/2019/02/12-ag-minutes.html#item03 |
Approved as errata in CfC Feb 21 2019. Leaving open for Michael to implement. |
Links are needed to the Understanding documents for the guidelines from WCAG 2.1.
Currently, it takes several steps to find those Understanding docs. For example, reaching "Understanding Guideline 1.1: Text Alternatives" requires selecting the link "Understanding Non-text Content" under Success Criterion 1.1.1 Non-text Content, then choosing "GL: Text Alternatives" from the navigation at the top of the page.
The text was updated successfully, but these errors were encountered: