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.

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

Update "Translating" page #874

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
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
114 changes: 70 additions & 44 deletions pages/about/translating.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: "Translating WAI Resources"
nav_title: Translating
lang: en
last_updated: 2024-04-09
last_updated: 2024-09-30
description: Help make the Web accessible to people with disabilities around the world. We appreciate your contributions to translating W3C WAI accessibility resources.

permalink: /about/translating/
Expand All @@ -17,7 +17,7 @@ image: /content-images/about/social-translations.png
feedbackmail: [email protected]

footer: |
<p><strong>Date:</strong> Updated 9 April 2024.</p>
<p><strong>Date:</strong> Updated 30 September 2024.</p>
<p><strong>Editors:</strong> <a href="https://www.w3.org/People/Shawn/">Shawn Lawton Henry</a> and Rémi Bétin.</p>
<p>Developed with input from the Education and Outreach Working Group (<a href="https://www.w3.org/WAI/EO/">EOWG</a>). Developed with support from the <a href="https://www.w3.org/WAI/expand-access/">WAI Expanding Access project</a>, funded by the Ford Foundation. Updated as part of the <a href="https://www.w3.org/WAI/about/projects/wai-coop/">WAI-CooP project</a>, co-funded by the European Commission.</p>
---
Expand All @@ -26,11 +26,13 @@ footer: |
{% include box.html type="start" title="Summary" class="" %}
{:/}

This page provides general instructions on translating WAI resources.
Help make Web Accessibility Initiative (WAI) resources available in your language.

For a list of existing translations, see {% include link.html to="/translations/" text="All WAI Translations" %}.
Join the volunteer translation community to raise awareness of digital accessibility among a global audience. This page provides general instructions on translating WAI standards and resources.

To get announcements related to WAI translations, subscribe to the WAI Translations mailing list by sending e-mail to <a href="mailto:[email protected]?subject=subscribe">[email protected] with subject: &ldquo;subscribe&rdquo;</a>
For a list of existing translations, see [All WAI Translations](/translations/).

To get announcements related to WAI translations, subscribe to the WAI Translations mailing list by sending e-mail to [[email protected] with subject: &ldquo;subscribe&rdquo;](mailto:[email protected]?subject=subscribe)

{::nomarkdown}
{% include box.html type="end" %}
Expand All @@ -49,68 +51,92 @@ To get announcements related to WAI translations, subscribe to the WAI Translati
{% include_cached toc.html type="end" %}
{:/}

Thank you for your interest in translating resources from the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI).
## Ways to contribute

## Translation Instructions
You can contribute to WAI translations in many ways:

**Scope:**
* These instructions cover web pages with a URI that begins with www.w3.org/WAI
* For web pages that begin with www.w3.org/TR/ or something else, there is a different process that is introduced in [TR & Authorized W3C Translations below](#tr).
[Providing video captions/subtitles](/about/translating/resources/subtitles/)
: This is the easiest way to start contributing, especially if you are not technical.

**Translator background** &mdash; we prefer translators to be:
* native speakers
* familiar with accessibility terminology in their language
* comfortable editing a file with code
[Translating a WAI resource](/about/translating/resources/)
: You are welcome to provide a translation for educational resources on WAI website (web pages with a URL that begins with www.w3.org/WAI). It is best if you are comfortable editing a file with code.

To avoid overlapping work:
* please do **not** translate files from the web
* follow the [step-by-step guide](/about/translating/resources/) to _get the right file to translate_ and to ensure that the resource is ready for you to translate.
[Reviewing WAI resources translations](/about/translating/reviewing/)
: You can help spot issues in translations before publication, even if you are not technical or do not know the translated language.

### If you want to translate a WAI resource:
[Creating a WCAG Unofficial translation {% include_cached external.html label="Different page format" %}](https://www.w3.org/Consortium/Translation/)
: You can host an unofficial translation of the Web Content Accessibility Guidelines (WCAG) after following a light process. Unofficial translations are not hosted on W3C website nor endorsed by W3C.

- Follow instructions in [[Step-by-Step Guide to Translating WAI Resources]](/about/translating/resources/).
[Creating a WCAG Authorized translation](/about/translating/wcag/)
: You can develop an Authorized translation of WCAG that will be published on W3C website. It involves a formal process, coordination with stakeholder organizations, and a thorough review.

### If you want to volunteer to review a translation:
We encourage you to keep up on translations work by [subscribing to the WAI Translations mailing list](mailto:[email protected]?subject=subscribe).

- Follow instructions in [[Reviewing a Translation]](/about/translating/reviewing/).
## Process

We encourage you to keep up on related translations work by [subscribing to the WAI Translations mailing list](mailto:[email protected]?subject=subscribe).

### Important notes
All contributions must go through the following main steps before publication. These steps are described in more detail in each policy, and additional steps may be necessary for some documents.

#### Translation Agreement
### 1. Intent to translate

By submitting a translation, you agree:
* To the redistribution terms of the [W3C Document License](https://www.w3.org/copyright/document-license-2023/). Your translation may be republished by the W3C or other entities if it is done in compliance with the License terms.
* That the W3C may rescind your right to publish or distribute the derivative work if the W3C finds that it leads to confusion regarding the original document's status or integrity. ([Source](https://www.w3.org/copyright/intellectual-rights/#translate).)
Before starting a translation, verify that you are willing to contribute under the [Translation agreement](#translation-agreement).

#### Reviews
Then, **you must ask and receive permission from W3C**. It generally involves sending an email to a mailing list, or opening a GitHub issue in the relevant repository.

Translations will be reviewed before they are published.
### 2. Translation

#### Names and Links {#links}
It involves the following steps:
- get the files to translate, from a GitHub repository or from WAI staff.
- edit the file(s) in a code editor.
- send the code for review: directly by opening a pull request in GitHub, or by sending the file(s) back to WAI staff.

This policy is based on [Internationalization Links](https://www.w3.org/International/i18n-drafts/pages/translation.html#linkingrules), which provides some background.
To avoid overlapping work:
* please do **not** translate files from the Web
* follow the guidance to get the right file to translate and to ensure that the resource is ready for you to translate.

Translations can include:
### 3. Review

* Translator's formal name, common name used online, &/or Twitter handle.
* Link to information about the translator as an individual, such as "about" page on personal website or biography page on a scholarly website.
* Organization name - translator's employer &/or other sponsor/funder of the translation.
All translations are reviewed before they are published.
- WAI resources translations are reviewed by other volunteers and WAI staff. Once reviewed, they are published on W3C WAI website.
- WCAG Candidate Authorized Translations (CAT) follow a formal review process described in the [Policy for Authorized W3C Translations](https://www.w3.org/2005/02/TranslationPolicy.html). Once reviewed, they are published on W3C website.
- WCAG Unofficial translations follow a simpler review process.

## Additional information

### Translator background

We prefer translators to be:
* native speakers
* familiar with accessibility terminology in their language
* comfortable editing a file with code

### Translation Agreement {#translation-agreement}

By submitting a translation, you agree:
* To the redistribution terms of the [W3C Document License](https://www.w3.org/copyright/document-license-2023/). Your translation may be republished by the W3C or other entities if it is done in compliance with the License terms.
* That the W3C may rescind your right to publish or distribute the derivative work if the W3C finds that it leads to confusion regarding the original document's status or integrity. ([Source](https://www.w3.org/copyright/intellectual-rights/#translate))

### Crediting {#links}

Translations can include:
* Translator's formal name, common name used online, and/or X/Mastodon handle.
* Link to information about the translator as an individual, such as "about" page on personal website or biography page on a scholarly website.
* Organization name - translator's employer and/or other sponsor/funder of the translation.

Cannot include:
* Links to organizations. (Exception: Qualifying accessibility/disability organizations or translation organizations. To request an exception, e-mail [[email protected] with subject [Translations link request]](mailto:[email protected]?subject=%5BTranslations%20link%20request%5D).)
* Links to organizations. (Exception: qualifying accessibility/disability organizations or translation organizations. To request an exception, e-mail [[email protected] with subject [Translations link request]](mailto:[email protected]?subject=%5BTranslations%20link%20request%5D).)
* Links to personal home pages rather than "about" pages.

#### Updating Resources
This policy is based on [Internationalization Links](https://www.w3.org/International/i18n-drafts/pages/translation.html#linkingrules), which provides some background.

### Updating Resources

When the English version of a resource is updated, we will inform translators what has changed<!-- @@by GitHub &/or e-mail -->, and request that translators update their translation. If original translators do not respond before we need the update, we will invite others to update the translation.
When the English version of a resource is substantively updated, we inform translators what has changed, and request that translators update their translation. If original translators do not respond before we need the update, we will invite others to update the translation.

In some cases, we will add the updated English to the translation while awaiting an update. If the changes are substantive, the translation may be removed until an updated version is provided.
In some cases, we will add the updated English to the translation while awaiting an update. If the changes are subtantial, the translation may be removed until an updated version is provided.

#### W3C Translations Information
### W3C Translations Information

More information is available in [W3C Translations](https://www.w3.org/Consortium/Translation/) and in <a href="https://www.w3.org/copyright/intellectual-rights/">W3C Intellectual Rights FAQ</a>, particularly under the questions starting with <a href="https://www.w3.org/copyright/intellectual-rights/#translate">can I translate one of your specifications into another language?</a>
More information is available in [W3C Translations](https://www.w3.org/Consortium/Translation/) and in [W3C Intellectual Rights FAQ](https://www.w3.org/copyright/intellectual-rights/), particularly under the questions starting with [May I translate a W3C specification into another language?](https://www.w3.org/copyright/intellectual-rights/#translate).

## WAI Translations Mailing List {#mailinglist}

Expand All @@ -123,9 +149,9 @@ There is also a broader W3C Translators list. To subscribe: [e-mail to w3c-trans

## TR & Authorized W3C Translations {#tr}

Web pages at URIs that begin with www.w3.org/TR/ (for "Technical Report") follow a different process described in [W3C Translations](https://www.w3.org/Consortium/Translation/).
Web pages at URIs that begin with www.w3.org/TR/ (for "Technical Report") follow the process described in [W3C Translations](https://www.w3.org/Consortium/Translation/).

Most translations are informative and unofficial. In cases where standards translations are meant for official purposes, they may be developed as Authorized W3C Translations according to the **[Policy for Authorized W3C Translations](https://www.w3.org/2005/02/TranslationPolicy.html)**. Generally only completed W3C Recommendations and Working Group Notes are candidates for Authorized W3C Translations, including the WAI guidelines. The authorized translations policy is designed to ensure transparency and community accountability in the development of authorized translations under the oversight of W3C.

* [WCAG 2 Translations](/standards-guidelines/wcag/translations/) lists in-progress and completed translations of Web Content Accessibility Guidelines (WCAG) 2.2, 2.1 and 2.0, including unofficial translations and Authorized W3C Translations. To translate WCAG 2, follow the instructions at [[How to translate WCAG 2]](/about/translating/wcag/).
* [Authorized Translations of W3C Recommendations](https://www.w3.org/Translations/authorized.html) lists completed Authorized W3C Translations of WCAG 2.1, WCAG 2.0, Authoring Tool Accessibility Guidelines (ATAG) 2.0, and others.
* [Authorized Translations of W3C Recommendations](https://www.w3.org/Translations/authorized.html) lists completed Authorized W3C Translations of WCAG 2.1, WCAG 2.0, Authoring Tool Accessibility Guidelines (ATAG) 2.0, and others.