Fix: Correct broken link #515
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add /wcag21 to 2.1 requirements link to fix 404 error
awkawk
added
Editorial
ErratumRaised
nschonni
reviewed
Oct 10, 2018
guidelines/index.html
Outdated
| @@ -78,7 +78,7 @@ <h3>WCAG 2.1 Supporting Documents</h3> | |||
| </section> | |||
| <section> | |||
| <h3>Requirements for WCAG 2.1</h3> | |||
| <p>WCAG 2.1 meets a set of <a href="https://w3c.github.io/wcag/requirements/">requirements for WCAG 2.1</a> which, in turn, inherit requirements from WCAG 2.0. Requirements structure the overall framework of guidelines and ensure backwards compatibility. The Working Group also used a less formal set of acceptance criteria for success criteria, to help ensure success criteria are similar in style and quality to those in WCAG 2.0. These requirements constrained what could be included in WCAG 2.1. This constraint was important to preserve its nature as a dot-release of WCAG 2.</p> | |||
| <p>WCAG 2.1 meets a set of <a href="https://w3c.github.io/wcag/wcag21/requirements/">requirements for WCAG 2.1</a> which, in turn, inherit requirements from WCAG 2.0. Requirements structure the overall framework of guidelines and ensure backwards compatibility. The Working Group also used a less formal set of acceptance criteria for success criteria, to help ensure success criteria are similar in style and quality to those in WCAG 2.0. These requirements constrained what could be included in WCAG 2.1. This constraint was important to preserve its nature as a dot-release of WCAG 2.</p> | |||
There was a problem hiding this comment.
This seems more up-to-date https://w3c.github.io/wcag21/requirements/
|
It's odd that we've got two similar links that go to different dates of the editors draft: @michael-n-cooper which should be canonical? The WCAG 2.0 link is https://www.w3.org/TR/wcag2-req/, should it be at https://www.w3.org/TR/wcag21-req/ ? |
|
The version in the w3c/wcag repo is canonical, since the w3c/wcag21 repo is retired. However, that's not to say it's more current. I have on a middle burner to sort out a few folders in the wcag repo, and it might be that I still need to migrate the requirements doc over. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add /wcag21 to 2.1 requirements link to fix 404 error
Preview | Diff