Step-by-Step Guide to Translating WAI Resources
Overview
There are 6 steps to contribute as a volunteer translator:
Before starting your work, please take the time to read the information in Translating WAI Resources, and verify that you are willing to contribute under these policies.
GitHub
We encourage you to use GitHub, especially if you intend to become a regular translator.
Discussions, collaboration with reviewers and progress tracking are more easily managed in GitHub.
- If you do not already have a GitHub Account, sign up for an account;
- If you are new to GitHub, we recommend that you follow this interactive free course:
Introduction to GitHub ; - For more specific guidance during the translation process, you can deep dive with our How to Use GitHub to Translate WAI Resources guide.
Step 1: Find a resource to translate
Have a look at our priorities
For suggestions on which to translate first, see Priorities for Translations.
Or pick a resource according to your preference
You are welcome to translate any current WAI resource that you think would be useful in your language.
The easiest way to find a resource to translate is to head over to the dedicated translations sitemap for your language.
Translations sitemaps display the structure of WAI website, and indicate for each page:
- If a translation in this language has been published, and its current status ( Up-to-date or Needs update);
- If a page has no translation available in this language, and therefore welcomes a volunteer translation.
Step 2: Inform us of your intent to translate a resource
When you have found a resource to translate, you must indicate your interest, and wait for a reply from WAI team. We’ll check that the file isn’t currently being translated by someone else, and that it isn’t about to be updated.
Please wait for reply from WAI team before starting a translation.
Recommended / quickest way
- From the translations sitemap for your language, click on the “Volunteer to translate this page” link, displayed next to the resource you intend to translate.
- It will automatically pre-fill a GitHub issue with some useful information.
- Read and submit the issue.
Alternatives:
- Create an Issue in the dedicated “WAI Translations” repository.
- If you are not comfortable with GitHub, send e-mail to the publicly-archived WAI translations list using this e-mail template.
Step 3: Start translating
Initial setup
- Log in to your existing GitHub account, or create one .
- Get to the repository of the resource you will translate.
- Near the bottom of each page on the WAI website, there is a “Help improve this page” box. The middle button is “Fork & Edit in GitHub”. That gets you to the repository.
- If you have followed the recommended way to declare your intent, the link to the repository has been automatically added in the GitHub issue description.
- You can directly work from there.
For further guidance on using GitHub to translate a WAI resource, follow the dedicated guide.
Translate the resource
- Refer to How to Translate a WAI Resource guide
- If the page you are translating has videos, also refer to How to Create Translated Video Subtitles and Descriptions
- If the page you are translating has images with text, also refer to How to Create Translated Video Subtitles and Descriptions
- Commit your changes.
Step 4: Preview and check your translation
-
Open a draft Pull Request in the GitHub repository of the resource, with
[IN-PROGRESS]
at the beginning of the title. - After you submit the pull request, a Netlify preview will be generated so you can check your file and make edits.
- At first it will say “👷 Deploy Preview for wai-repo-name processing.”.
- When done, it will say “✅ Deploy Preview for wai-repo-name ready!” and a “Deploy Preview” link will appear.
- Click on the preview link:
- Check everything listed in Reviewer Guidance;
- Eventually, commit some fixes;
- At this point, if you encounter some technical problems, ask for help from WAI team.
- When your auto-review is done, go to the next step.
Step 5: Ask for reviews
Translations are reviewed before they are published.
- Change the state of your pull request to “Ready for review” and change the beginning of your Pull Request title to
[READY FOR REVIEW]
- Communicate your Pull Request is ready for review in the GitHub issue created at step 2.
- Review discussions take place directly in the GitHub Pull Request. Work together with reviewer(s) to:
- fix issues;
- accurately convey the meaning from the English version;
- consider different dialects.
If you have any questions about the wording, please report them in the GitHub issue so that WAI team and other volunteers can help.
Step 6: Wait for publication
When the review is done, WAI team will:
- do some final checks;
- merge the Pull Request;
- publish the translation on WAI website.
Please note these steps may take some time depending on other ongoing priorities.
Priorities for Translating WAI Resources
- Video Introduction to Web Accessibility and W3C Standards
Completed translations: ar cs de el es fr id ja ko nl pl pt-BR ru zh-hans - Introduction to Web Accessibility
Completed translations: ar cs de es fr id ko ru zh-hans - Web Accessibility Perspectives Videos: Explore the Impact and Benefits for Everyone
Completed translations: fr- Keyboard Compatibility
Completed translations: fr - Colors with Good Contrast
Completed translations: fr - Clear Layout and Design
Completed translations: fr - Text to Speech
Completed translations: fr - Large Links, Buttons, and Controls
Completed translations: fr - Video Captions
Completed translations: fr - Customizable Text
Completed translations: fr - Speech Recognition
Completed translations: fr - Understandable Content
Completed translations: fr - Notifications and Feedback
Completed translations: fr
- Keyboard Compatibility
- Tips for Getting Started
Completed translations: fr id- Writing for Web Accessibility – Tips for Getting Started
Completed translations: fr id ja - Designing for Web Accessibility – Tips for Getting Started
Completed translations: fr id ja - Developing for Web Accessibility – Tips for Getting Started
Completed translations: fr id ja
- Writing for Web Accessibility – Tips for Getting Started
- An alt Decision Tree
Completed translations: de fr id ja ko - Accessibility Principles
Completed translations: ar cs es fr ko ru zh-hans - WCAG 2 Overview
Completed translations: es fr ja - What's New in WCAG 2.2