rename files as WCAG criteria and rejig contents #499
Conversation
This file contains hidden or 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
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.
I'm going to be sharing this with some new friends and I wanted to tidy it up a bit and make the relationships between each problem and its WCAG criterion more obvious.
To this end, I've renamed all the files to match their respective WCAG entry, linked to the Understanding documents where that wasn't already available, updated some links to use the latest WCAG docs, and moved some issues into other files. I've also added some sub-lists to the ToCs for some of the criteria to at least try to retain some grouping of common problems.
I haven't made any changes to the actual recommendations themselves, though I did add to the README intro and added intros to any pages that didn't otherwise have them.