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 documentation links to WCAG 2.2 equivalent #1015

Open
lb- opened this issue Oct 18, 2024 · 2 comments · May be fixed by #1016
Open

Update all documentation links to WCAG 2.2 equivalent #1015

lb- opened this issue Oct 18, 2024 · 2 comments · May be fixed by #1016

Comments

@lb-
Copy link
Contributor

lb- commented Oct 18, 2024 •
edited
Loading

It would be good for all the links to the WCAG website be updated to the equivalent WCAG 2.2 standard.

This came out just over a year ago now and should be the canonical links we provide when giving guidance to developers.

There was this issue #1008 - however it was more about rules that need to change.

I am only suggesting we change our links in the documentation.
lb- pushed a commit to lb-/eslint-plugin-jsx-a11y that referenced this issue Oct 18, 2024
Update all WCAG URLs to the equivalent 2.2 location
198ea61 
Fixes jsx-eslint#1015
Ensure all URLs are consistent (without trailing HTML) as this is the canonical URL
@lb- lb- linked a pull request Oct 18, 2024 that will close this issue
Open
lb- added a commit to lb-/eslint-plugin-jsx-a11y that referenced this issue Oct 18, 2024
@lb-
Update all WCAG URLs to the equivalent 2.2 location
d786f06 
Fixes jsx-eslint#1015
Ensure all URLs are consistent (without trailing HTML) as this is the canonical URL
lb- added a commit to lb-/eslint-plugin-jsx-a11y that referenced this issue Oct 18, 2024
@lb-
[Docs] Update all WCAG URLs to the equivalent 2.2 location
252f4f6 
Fixes jsx-eslint#1015
Ensure all URLs are consistent (without trailing HTML) as this is the canonical URL
@ljharb
Copy link
Member

ljharb commented Oct 18, 2024

The links in docs should match what we implement; we shouldn’t link to 2.2 unless we comply with it.

@lb-
Copy link
Contributor Author

lb- commented Oct 18, 2024 •
edited
Loading

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 noticed that some links have better linked examples and explanations but the actual success criteria itself remains the same.

See a similar comment on the PR. #1016 (comment)

lb- added a commit to lb-/eslint-plugin-jsx-a11y that referenced this issue Oct 21, 2024
@lb-
[Docs] Update all WCAG URLs to the equivalent 2.2 location
2ab9e56 
Fixes jsx-eslint#1015
Ensure all URLs are consistent (without trailing HTML) as this is the canonical URL
lb- added a commit to lb-/eslint-plugin-jsx-a11y that referenced this issue Oct 25, 2024
@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update all WCAG URLs to the equivalent 2.2 location lb-/eslint-plugin-jsx-a11y
2 participants
@ljharb @lb-