Translating WAI Resources
Thank you for your interest in translating resources from the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI).
You are welcome to translate any WAI resource. For suggestions on which to translate first, see Priorities for Translations below.
- 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.
If you want to translate a WAI resource:
- Check that there is not already a completed translation listed in All WAI Translations.
- Get a W3C account if you do not already have one. (This will allow us to associate your translations with your W3C profile.)
- Indicate your interest in translating the resource by sending an e-mail to the WAI and W3C translations lists using this e-mail template.
- WAI staff will send you an e-mail when the resource is ready to be translated. It will include instructions for translating the file.
More Translation Instructions
Before starting your translation, please read:
- Important Translations Guidance below
- Translation Notes for the specific resource in the README file in GitHub
- Translation Glossaries - the General glossary and if there’s a glossary for your language
When you are done with the translation, we encourage you to use GitHub to fork, edit, and submit a pull request. If you are not comfortable with GitHub, you can e-mail the translated file to firstname.lastname@example.org with the subject: Completed Translation – [language] – [resource title]
Translations will be reviewed before they are published. Please include in GitHub or e-mail:
- Names of people who already reviewed the translation.
- Contact information for other people who might be interested in reviewing the translation.
This policy is based on Internationalization Links, which provides some background.
Translations can include:
- Translator’s formal name, common name used online, &/or Twitter handle.
- Link to translator’s individual page, such as personal blog, personal home page, bio page, or acceptable social media page.
- Organization name - translator’s employer &/or other sponsor/funder of the translation.
- Links to organizations. (Exception: Qualifying accessibility/disability organizations or translation organizations. To request an exception, e-mail email@example.com with subject [Translations link request].)
W3C Translations Information
More information is available in W3C Translations and in W3C Intellectual Rights FAQ, particularly under the questions starting with can I translate one of your specifications into another language?
Important Translations Guidance
- Do not change or adapt or add to the meaning of the English version in your translation. If you have suggestions for changes to the English version, submit them via GitHub or e-mail using the links in the “Help improve this page” box near the bottom of the page.
- Make sure to translate image alts.
- Please leave the code, HTML, and markdown as is without changing it (other than at the top as noted after #).
- If you have any questions about the translation, please e-mail them to firstname.lastname@example.org. We are happy to help you decide on the best translated wording by sharing the considerations and nuances that went into choosing the wording for the English page.
By submitting a translation, you agree:
- To the redistribution terms of the W3C Document License. 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.)
When the English version of a resource is updated, we will inform translators what has changed, and request that translators update their translation.
If the changes are only small changes, such as a new paragraph or a new short section, we might add the English to the translation while awaiting an update. If the changes are substantive, the translation will be removed until an updated version is provided.
WAI Translations Mailing List
- To subscribe, send e-mail to email@example.com with subject: subscribe.
- To unsubscribe, send e-mail to firstname.lastname@example.org with subject: unsubscribe.
You can also see the [WAI Translations List Archives %5D(http://lists.w3.org/Archives/Public/public-wai-translations/).
Priorities for Translating WAI Resources
You are welcome to translate any current WAI resource that you think would be useful in your language. The lists below are suggested priorities.
- High priority introductory resources
- High priority WCAG resources
- Main navigation overview pages
- Other priority resources
- To be updated
High priority introductory resources
- Video Introduction to Web Accessibility and W3C Standards (including VTT file)
- Introduction to Web Accessibility (minor edits planned for 2019 Q2)
- W3C Accessibility Standards Overview
- Mobile Accessibility at W3C
- Accessibility Principles (minor addition planned for 2019 Q2)
High priority WCAG resources
- Web Content Accessibility Guidelines (WCAG) 2.1 — the Web Standard / W3C Recommendation (TR)
- WCAG Overview
- WCAG 2.1 at a Glance
Main navigation overview pages
If you translate these pages, then users will get the main navigation in your language. In most cases, we will wait to publish these until all of them are translated.
- Accessibility Fundamentals Overview (new page coming in 2019)
- W3C Accessibility Standards Overview (repeat from above)
- Evaluating Web Accessibility Overview
- Design and Develop Overview
- Planning and Policies Overview
- Teach and Advocate Overview
- WAI home page (see notes on which parts to translate)
Other priority resources
- How People with Disabilities Use the Web — 4 pages
- Other standards overviews:
- Essential Components of Web Accessibility
- WAI-ARIA Overview (this page will be updated in the future; however, it could be many months before it is updated)
- User Agent Accessibility Guidelines (UAAG) Overview
- Authoring Tool Accessibility Guidelines (ATAG) Overview
- Advocating and teaching resources:
- Planning and managing resources:
- Design and development resources:
There are many more WAI resources available for translation. The complete list of WAI resources is available in the WAI Site Map.
To be updated
The following pages will be updated. You might want to wait to translate them until after they are updated, or be prepared to update your translation. To get announcements when they are updated, see Get WAI News and subscribe to the WAI Translations mailing list, per above.
- About W3C WAI — minor update planned for 2019
- Participating in WAI (see notes on which parts to translate) — minor update planned for 2019
- Easy Checks - A First Review of Web Accessibility — significant update planned for 2019
- Why Standards Harmonization is Essential to Web Accessibility (no date set for the update to be completed)
TR & Authorized W3C Translations
Web pages at URIs that begin with www.w3.org/TR/ (for “Technical Report”) follow a different process described in W3C Translations.
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. 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.Back to Top