Updating WCAG 2.2 translations: October 2023 to December 2024 version

Refer to the relevant process

To update a W3C technical report translation, you must follow the same process as for an initial translation:

Considering the limited scope of this update, we will do our best to ensure that the W3C’s steps run as smoothly as possible.

The easiest way to spot the changes between the two versions is to use a “diff checker” tool, such as the W3C HTML Diff service.

Use the following input values :

Address of reference document: https://www.w3.org/TR/2023/REC-WCAG22-20231005/
Address of new document: https://www.w3.org/TR/2024/REC-WCAG22-20241212/

We also recommend that you read the WCAG 2.2 Change log.

Refer to the WCAG22-20241212 tag to get the files of the 12 December 2024 version.

To list the relevant changes:

In your terminal, run the following command:

How to translate WCAG 2 explains how to use the content in w3c/wcag repository to translate WCAG.

If using this recent method is overly complex to you, you can update your existing files.

Please update the following information in the translation header (also called “disclaimer”) at the top of the document.

Date of publication: Translation publication date will be updated by W3C.
This version:: URI will be updated by W3C.
Most recent version:: Keep the existing URI. Example: https://www.w3.org/Translations/WCAG22-fr/
Previous version:: Dated URI of the initial translation. Example: https://www.w3.org/Translations/WCAG22-it-20231205/
Please add and translate this new text.
Original version:: Use https://www.w3.org/TR/2024/REC-WCAG22-20241212/
Errata:: URI of an errata page. Please create and host a new errata page specific to this translation version.
Lead translating organization:: Update information when relevant.
Partners in the translation review:: Update URI as relevant.
Summary of public comments on the Candidate Authorized Translation:: Update URI as relevant.

Please properly check your files before submission to W3C.

In particular, make sure that:

All links are valid. You can use W3C Link Checker
HTML is valid. You can use W3C Markup Validation Service
CSS is valid. You can use W3C CSS Validation Service
Pages are internationalization-friendly. You can use W3C Internationalization Checker
All relevant content has been properly translated
All ids are in English; that is, they have not been translated.
- If you have followed How to Translate WCAG 2 – Get the source files, this should be fine.
- If you have translated WCAG 2 before January 2024, you might want to check this.
lang and xml:lang attributes of the <html> tag are correct
lang attribute has been used when relevant (especially when some text has been kept in English)
The links/anchors of the original and translated versions match.
“Jump to table of contents”, “Collapse sidebar” and “Hide sidebar” have been translated.
There is no code showing in the rendered page.
No custom CSS has been added.
(Authorized translation) An errata has been created and is hosted on the Lead Translation Organization (LTO)’s website.