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

WCAG 2 December versions: update “Translating WCAG” guidance #1026

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

WCAG 2 December versions: update “Translating WCAG” guidance #1026

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions pages/about/translating/wcag.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: How to Translate WCAG 2
nav_title: "Translate WCAG 2"
lang: en
last_updated: 2024-10-22
last_updated: 2024-12-19
description: Technical instructions on translating WCAG

permalink: /about/translating/wcag/
Expand Down Expand Up @@ -50,7 +50,7 @@ For general information on WCAG 2 Translations, see [Contributing to W3C Transla

## Overview

Web Content Accessibility Guidelines (WCAG) 2.1/2.2 are currently [available in more than 14 languages](/standards-guidelines/wcag/translations/)!
Web Content Accessibility Guidelines (WCAG) 2.1/2.2 are currently [available in more than 14 languages](/standards-guidelines/wcag/translations/).

There are 6 main steps to create a new translation:
1. **[Get the source files](#get-source-files)** from [`w3c/wcag/` {% include_cached external.html %}](https://github.com/w3c/wcag/) repository
Expand All @@ -64,8 +64,8 @@ There are 6 main steps to create a new translation:

1. Clone [`w3c/wcag` {% include_cached external.html %}](https://github.com/w3c/wcag/) repository (you can [fork {% include_cached external.html %}](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo) it first)
2. Checkout the following tag to get the relevant source files:
- [`WCAG22-20231005` tag {% include_cached external.html %}](https://github.com/w3c/wcag/tree/WCAG22-20231005) to translate WCAG 2.2 (5 October 2023 version)
- [`WCAG21-20230921` tag {% include_cached external.html %}](https://github.com/w3c/wcag/tree/WCAG21-20230921) to translate WCAG 2.1 (21 September 2023 version)
- [`WCAG22-20241212` tag {% include_cached external.html %}](https://github.com/w3c/wcag/tree/WCAG22-20241212) to translate WCAG 2.2 (12 December 2024 version)
- [`WCAG21-20241212` tag {% include_cached external.html %}](https://github.com/w3c/wcag/tree/WCAG21-20241212) to translate WCAG 2.1 (12 December 2024 version)
Copy link
Contributor

@kfranqueiro kfranqueiro Dec 19, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @iadawn RE a quick chat this morning: we may want to hold off encouraging translations on updated WCAG 2.1 until further corrections are discussed/handled (see w3c/wcag#4179)


## Step 2: Translate WCAG source files {#translate-source-files}

Expand Down
46 changes: 28 additions & 18 deletions pages/about/translating/wcag/wcag21-update.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
title: How to update WCAG 2.1 translations
nav_title: "Update WCAG 2.1 translations"
title: How to update WCAG 2 translations
nav_title: "Update WCAG 2 translations"
lang: en
last_updated: 2024-10-22
description: Technical instructions on updating WCAG 2.1 translations
last_updated: 2024-12-19
description: Technical instructions on updating WCAG 2 translations

permalink: /about/translating/wcag/wcag21-update/
ref: /about/translating/wcag/wcag21-update/
Expand All @@ -22,11 +22,7 @@ footer: |
{% include box.html type="start" h="2" title="Summary" class="full" %}
{:/}

Web Content Accessibility Guidelines (WCAG) 2.1 have been updated on 21 September 2023:
- The version published on 21 September 2023: [https://www.w3.org/TR/2023/REC-WCAG21-20230921/](https://www.w3.org/TR/2023/REC-WCAG21-20230921/)
- The outdated version, published on 5 June 2018: [https://www.w3.org/TR/2018/REC-WCAG21-20180605/](https://www.w3.org/TR/2018/REC-WCAG21-20180605/)

This page guides you through the steps to update an existing WCAG 2.1 translation.
This page guides you through the steps to update an existing WCAG 2.2 or 2.1 translation.

{::nomarkdown}
{% include box.html type="end" %}
Expand All @@ -51,35 +47,49 @@ To update a W3C technical report translation, you must follow the same process a
- Unofficial translations: [Instructions for W3C technical reports translations](https://www.w3.org/Consortium/Translation/#how)
- Authorized translations: [Policy for Authorized W3C Translations](https://www.w3.org/2005/02/TranslationPolicy.html)

Considering the limited scope of the WCAG 2.1 update, we will do our best to ensure that the W3C's steps run as smoothly as possible.
We will do our best to ensure that the W3C's steps run as smoothly as possible.

## Browse the content changes

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](https://services.w3.org/htmldiff).

Use the following input values :
### WCAG 2.1 changes

Use the following input values to compare the June 2018 and December 2024 versions of WCAG 2.1:
kfranqueiro marked this conversation as resolved.
Show resolved Hide resolved

Address of reference document
: [https://www.w3.org/TR/2018/REC-WCAG21-20180605/](https://www.w3.org/TR/2018/REC-WCAG21-20180605/)

Address of new document
: [https://www.w3.org/TR/2023/REC-WCAG21-20230921/](https://www.w3.org/TR/2023/REC-WCAG21-20230921/)
: [https://www.w3.org/TR/2024/REC-WCAG21-20241212/](https://www.w3.org/TR/2024/REC-WCAG21-20241212/)

You can use this direct link: [Diff between 2018 and 2023 WCAG 2.1 versions, via W3C HTML diff service](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2F2018%2FREC-WCAG21-20180605%2F&doc2=https%3A%2F%2Fwww.w3.org%2FTR%2F2023%2FREC-WCAG21-20230921%2F)
You can use this direct link: [Diff between 2018 and 2024 WCAG 2.1 versions, via W3C HTML diff service](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2F2018%2FREC-WCAG21-20180605%2F&doc2=https%3A%2F%2Fwww.w3.org%2FTR%2F2024%2FREC-WCAG21-20241212%2F)

We also recommend that you read the [WCAG 2.1 Change log](https://www.w3.org/TR/WCAG21/#changelog).

## Update the translation
### WCAG 2.2 changes

Use the following input values to compare the October 2023 and December 2024 versions of WCAG 2.2:

Address of reference document
: [https://www.w3.org/TR/2023/REC-WCAG22-20231005/](https://www.w3.org/TR/2023/REC-WCAG22-20231005/)

In January 2024, we have published a guide on translating WCAG 2: [How to translate WCAG 2](/about/translating/wcag/). It explains how to use the content in [`w3c/wcag` {% include_cached external.html %}](https://github.com/w3c/wcag/) repository to start translating WCAG.
Address of new document
: [https://www.w3.org/TR/2024/REC-WCAG22-20241212/](https://www.w3.org/TR/2024/REC-WCAG22-20241212/)

You can use this direct link: [Diff between 2023 and 2024 WCAG 2.2 versions, via W3C HTML diff service](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2F2023%2FREC-WCAG22-20231005%2F&doc2=https%3A%2F%2Fwww.w3.org%2FTR%2F2024%2FREC-WCAG22-20241212%2F)

We also recommend that you read the [WCAG 2.2 Change log](https://www.w3.org/TR/WCAG22/#changelog).

## Update the translation

If you want to use this method, refer to the [`WCAG21-20230921` tag](https://github.com/w3c/wcag/tree/WCAG21-20230921) to get the files of the 21 September 2023 version.
[How to translate WCAG 2](/about/translating/wcag/) explains how to use the content in [`w3c/wcag` {% include_cached external.html %}](https://github.com/w3c/wcag/) repository to start translating WCAG.

If starting over with this new method is overly complex for you, you can update your existing files.

## (Authorized translations) Update the translation header

Each "Authorized Translation" must contain a translation header (also called "disclaimer") at the top of the document. When updating a WCAG 2.1 translation, the following information will need update:
Each "Authorized Translation" must contain a translation header (also called "disclaimer") at the top of the document. When updating a WCAG 2 translation, the following information will need update:

Date of publication
: Translation publication date will be updated by W3C.
Expand All @@ -95,7 +105,7 @@ Previous version:
Please add and translate this new text.

Original version:
: Use [https://www.w3.org/TR/2023/REC-WCAG21-20230921/](https://www.w3.org/TR/2023/REC-WCAG21-20230921/)
: Dated URI of the English original. Example: [https://www.w3.org/TR/2024/REC-WCAG21-20241212/](https://www.w3.org/TR/2024/REC-WCAG21-20241212/)

Errata:
: URI of an errata page. Please create and host a new errata page specific to this translation version.
Expand Down