-
Notifications
You must be signed in to change notification settings - Fork 252
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
[Comment] Meaning of "Alternate version" is not clear (G136) #73
Comments
I submitted the above suggestion via the web interface. Another possibility is "Accessible alternate version". The important thing is that the text is clear and concise. Would people understand "accessible" to refer to accessibility for people with disabilities? "Accessible" sometimes means just that one is able to access it, that is, it's not behind a password. |
David MacDonald will look into |
_READY FOR REVIEW_ We have concerns about having the link be too verbose. On many sites, real estate is expensive. "Alternate Version" is well understood by the audience to which it is addressed. "WCAG Version" would not be sufficient because the authors may have to meet other standards such as the M376 with the same link. "Accessible Alternate Version" is wordy and it may not be accessible to all. We've historically been very shy about using the word "accessible" and prefer "Conforming". "WCAG Conforming Version" is verbose and may cause trouble for those writing for other standards also. Therefore, we have chosen to leave the current wording. |
Updated G136 as approved by WG (714f9a4) |
Thanks, everyone. |
https://www.w3.org/2006/02/lc-comments-tracker/35422/NOTE-WCAG20-TECHS-20140911/2994
The example suggests that the link text to the conforming alternate version be "Alternate version". This does not clearly identify that the link goes to an accessible version of the same content.
Proposed Change:
Replace: "Alternate version"
With: "WCAG-conforming alternate version"
Or: "WCAG-conforming alternate version of this page"
The text was updated successfully, but these errors were encountered: