Resource-Specific Translation Instructions

In Audio Description section:

• Do not translate the text in {% include t.html t='Enable Audio Description' %}: it will be automatically translated.
• After that code, please add ("<span lang='en'>Enable Audio Description</span>").

In Translations section:

1. If the player is available in the translated language :
   • Translate the following words from the video player interface:
     • “Captions”
     • “Show transcript”
     • “Language”
   • Update the image per the instructions below.
     If you are not able to update the image, let us know at group-wai-translations@w3.org.
     • Make a new image to replace show-language.png. The circle is 7px #eed009 / rgb(238,208,9).
     • Name it show-language.[language tag].png
       For example: show-language.fr.png
     • Upload it to the content-images folder
   • In your translation, add the language tag to the image path.
2. If the player is not available in the translated language:
   • Do not translate the following words from the video player interface; leave them in English:
     • “Captions”
     • “Show transcript”
     • “Language”
   • Mark up the English words with the lang attribute:
     <span lang="en">Captions</span>.

The “Web Accessibility Perspective Videos” page points to the resource sub-pages. Once you have translated a sub-page, add your language tag to the end of the corresponding URL in the index page.

The title “How People with Disabilities Use the Web” is not a question: it is a statement. For translation, it might help to think of it as a shorter version of “An Introduction to How People with Disabilities Use the Web” or “Description of How People with Disabilities Use the Web”.

For the Guidelines section:

• Please consider the wording in the WCAG 2.2 success criteria. If there is a translation of WCAG 2 in your language, review it thoughtfully.
• This text is not the same as the success criteria wording — it is a paraphrased summary that is intended to be easier to understand and accurate – yet it does not need to be comprehensive.
• Please collaborate with others who are familiar with WCAG to refine this wording in your language.

Tutorials resources use a dynamic footer, using specific metadata set in the “front matter” of each page.

1. Translate content in editors, update_editors, contributing_participants and support.\
2. Translate the Working Group name and leave the Working Group acronym in English.
3. Add translations for the following terms, used by the footer, in the translations.yml file located in the wai-website-data repository :
   • “Editors:”
   • “Update Editor:”
   • “Status”
   • “Updated”
   • “first published”