-
Notifications
You must be signed in to change notification settings - Fork 26
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
[ag] Proposal to supersede WCAG10 #123
Comments
Approved. Michael, please include me in the preparation of the draft AC CfR. |
@@todo: check if WCAG 1.0 is currently used in a country... |
AC survey created https://www.w3.org/2002/09/wbs/33280/2019-04_WCAG10_supersede/ |
awaiting on comm draft. |
I didn't do the comm draft because Judy told me to hold the presses, something was terribly wrong with the template I was asked to follow, and not to do anything until it was sorted out, which wouldn't be this week. According to her, @plehegar knows about this and what's wrong with the template. I don't. So I'm awaiting you guys before I do the comm draft. |
what's the status on this front? |
Looks like I dropped the ball after the "hold the presses". PLH created a second AC survey: https://www.w3.org/2002/09/wbs/33280/wcag1-sup/ which has 1 response so we'll use that one. PLH to send draft comm announcement to me and Judy for review. |
draft announcement to start AC review sent to Michael and Judy. |
Removing from my plate, afaik the success or failure of this task is on Judy's plate now. |
title, URL of the document to be superseded
Web Content Accessibility Guidelines 1.0
title, URL of the newer version
Web Content Accessibility Guidelines (WCAG) 2.1
I provide the unversioned URI for supersession, the current version is 2.1 but that will continue to evolve.
Link to group's decision to request superseding
RE: CFC – Marking WCAG 1.0 Superseded and related supporting documents as Retired
Rationale
WCAG 1.0 is 20 years old and was written for the technology of the time. WCAG 2.0 was released nearly 10 years later to much fanfare with less technology-specific features and is now the version most widely referenced in policy. The release of WCAG 2.1, another 10 years on, further suggests that guidelines evolution has superseded WCAG 1.0.
Implementation
WCAG 2.x is generally backwards compatible with WCAG 1.0. Sites that conform to WCAG 1.0 may not yet conform to WCAG 2, but are not inherently unable to do so.
The text was updated successfully, but these errors were encountered: