Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update all WCAG URLs to the equivalent 2.2 location #1016

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update all WCAG URLs to the equivalent 2.2 location #1016

wants to merge 1 commit into from

Conversation

lb-
Copy link
Contributor

@lb- lb- commented Oct 18, 2024

@lb- lb- force-pushed the docs/1015-update-wcag-urls-2.2 branch 2 times, most recently from d786f06 to 252f4f6 Compare October 18, 2024 06:23
@lb-
Copy link
Contributor Author

lb- commented Oct 18, 2024

As per https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/#changes-from-wcag-21-to-wcag-22

WCAG 2.2 provides 9 additional success criteria since WCAG 2.1. They are introduced on this page.

The 2.0 and 2.1 success criteria are essentially the same in 2.2, with one exception: 4.1.1 Parsing is obsolete and removed from WCAG 2.2. More information is in WCAG 2 FAQ, 4.1.1 Parsing. WCAG 2.2 includes Notes about different languages; more information is in WCAG 2 FAQ, internationalization.

I have left the link in that this project has for 4.1.1. but it may be better to review this link in the future. As for any other differences, there are only additions with new requirements and no significant changes to existing requirements.

I have noticed that some links have better linked examples and explanations but the actual success criteria itself remains the same.

@lb- lb- mentioned this pull request Oct 18, 2024
Open
@ljharb
Copy link
Member

ljharb commented Oct 18, 2024

I'm fine converting the 2.1 links to 2.2 as long as it doesn't imply that we're not validating parsing, since I suspect some of our rules do indeed do that.

@lb- lb- force-pushed the docs/1015-update-wcag-urls-2.2 branch from 252f4f6 to 2ab9e56 Compare October 21, 2024 09:21
@lb-
Copy link
Contributor Author

lb- commented Oct 21, 2024

OK @ljharb would you like me to further refine this PR with additional context where the links exist? Or are you happy with it in its current state?

@lb-
[Docs] Update all WCAG URLs to the equivalent 2.2 location
aa08ee9 
Fixes jsx-eslint#1015
Ensure all URLs are consistent (without trailing HTML) as this is the canonical URL
@lb- lb- force-pushed the docs/1015-update-wcag-urls-2.2 branch from 2ab9e56 to aa08ee9 Compare October 25, 2024 23:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@MichaelDeBoey MichaelDeBoey MichaelDeBoey approved these changes

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Update all documentation links to WCAG 2.2 equivalent
3 participants
@lb- @ljharb @MichaelDeBoey