+
+
+
+
+
+
+
+Date: Updated 1 August 2023.
-Editor: Shawn Lawton Henry.
-Developed with input from the Education and Outreach Working Group (EOWG).
+Date: Updated 13 March 2024.
github: repository: w3c/wai-about-wai path: '_about/index.md' --- +{::nomarkdown} +{% include box.html type="start" class="" %} +{:/} + +**Accessibility: Essential for some, useful for all.** + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + {::nomarkdown} {% include box.html type="start" h="2" title="Brief" class="full" %} {:/} -**[WAI develops…](https://www.w3.org/WAI/Resources/Overview)** +**[WAI develops…](/resources/)** -- guidelines which are widely regarded as the international standard for web accessibility +- guidelines that are widely regarded as the international standard for web accessibility - support materials to help understand and implement web accessibility -- resources, through international collaboration +- free online resources, through international collaboration **[WAI welcomes…](/about/participating/)** @@ -30,13 +38,10 @@ github: - volunteers to review, implement, and promote guidelines - dedicated participants in Working Groups - {::nomarkdown} {% include box.html type="end" %} {:/} -{::options toc_levels="2" /} - {::nomarkdown} {% include_cached toc.html type="start" title="Page Contents" %} {:/} @@ -48,55 +53,95 @@ github: {% include_cached toc.html type="end" %} {:/} -## World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI) +## W3C WAI -The World Wide Web Consortium's (W3C) commitment to lead the web to its full potential includes promoting a high degree of usability for people with disabilities. The Web Accessibility Initiative (WAI) is an initiative of the W3C. +The World Wide Web Consortium ([W3C](https://www.w3.org/about/)) is an international [public-interest non-profit organization](https://www.w3.org/news/2022/w3c-to-become-a-public-interest-non-profit-organization/) where Member organizations, a full-time staff, and the public work together to develop Web standards. Web Accessibility Initiative (WAI) is a key aspect of W3C's work for the benefit of humanity. -WAI develops its work through W3C's consensus-based process, involving different stakeholders in web accessibility. These include industry, disability organizations, government, accessibility research organizations, and more. +This information extends the [W3C Mission](https://www.w3.org/mission/) (vision, identity, design principles, strategic goals) to address accessibility specifics. -WAI, in partnership with organizations around the world, pursues accessibility of the web through these primary activities: +
+
+
+
+To reach all WAI staff, you can e-mail Date: Updated 24 March 2022.
+Date: Updated 29 April 2024.
Editor: Shawn Lawton Henry.
Developed with the Education and Outreach Working Group (EOWG).
@@ -50,7 +50,7 @@ accessibility. We encourage individuals and organizations around the world to participate in activities that help improve accessibility of the web. -**_After you read this page_, if you have any questions about getting involved with WAI or would like more information, please send specific questions to Shawn atDate: Updated 9 November 2023.
+Date: Updated 9 April 2024.
Editors: Shawn Lawton Henry and Rémi Bétin.
Developed with input from the Education and Outreach Working Group (EOWG). Developed with support from the WAI Expanding Access project, funded by the Ford Foundation. Updated as part of the WAI-CooP project, co-funded by the European Commission.
--- @@ -66,7 +66,10 @@ To avoid overlapping work: ### If you want to translate a WAI resource: - Follow instructions in [[Step-by-Step Guide to Translating WAI Resources]](/about/translating/step-by-step/). -- You will find more detailed guidance in [[Translations Guides]](/about/translating/guides/). + +### If you want to volunteer to review a translation: + +- Follow instructions in [[Reviewing a Translation]](/about/translating/guides/review-translation/). We encourage you to keep up on related translations work by [subscribing to the WAI Translations mailing list](mailto:public-wai-translations-request@w3.org?subject=subscribe). diff --git a/_about/translating/guides.md b/_about/translating/guides.md index 665c7e2e..f5ea5a39 100644 --- a/_about/translating/guides.md +++ b/_about/translating/guides.md @@ -7,13 +7,13 @@ github: permalink: /about/translating/guides/ ref: /about/translating/guides/ lang: en -last_updated: 2023-11-09 +last_updated: 2024-03-19 description: Help make the Web accessible to people with disabilities around the world. We appreciate your contributions to translating W3C WAI accessibility resources. image: /content-images/wai-about-wai/social-translations.png feedbackmail: wai@w3.org footer: | -Date: Updated 9 November 2023.
+Date: Updated 19 March 2024.
Editors: Shawn Lawton Henry and Rémi Bétin.
Developed as part of the WAI-CooP project, co-funded by the European Commission.
--- @@ -21,7 +21,9 @@ footer: | ## Guides - [Creating a Translation](/about/translating/guides/new-translation/) -- [Translating Subtitiles/Descriptions](/about/translating/guides/video-subtitles/) +- [Translating Subtitles/Descriptions](/about/translating/guides/video-subtitles/) +- [Translating Images](/about/translating/guides/images/) - [Reviewing a Translation](/about/translating/guides/review-translation/) - [Translation Guidance](/about/translating/guides/translation-guidance/) - [Using GitHub](/about/translating/guides/using-github/) +- [Translating WCAG](/about/translating/guides/wcag/) diff --git a/_about/translating/guides/images.md b/_about/translating/guides/images.md new file mode 100644 index 00000000..0a79a970 --- /dev/null +++ b/_about/translating/guides/images.md @@ -0,0 +1,174 @@ +--- +title: "How to Translate Images" +nav_title: Images +github: + repository: w3c/wai-about-wai + path: '_about/translating/guides/images.md' +permalink: /about/translating/guides/images/ +ref: /about/translating/guides/images/ +lang: en +last_updated: 2024-04-09 + +description: Help make the Web accessible to people with disabilities around the world. We appreciate your contributions to translating W3C WAI accessibility resources. +image: /content-images/wai-about-wai/social-translations.png + +feedbackmail: wai@w3.org +footer: | +Date: Updated 9 April 2024.
+Editor: Rémi Bétin.
+--- + +{::nomarkdown} +{% include box.html type="start" h="2" title="Summary" class="full" %} +{:/} + +This page guides you through the technical steps to translate images from the Web Accessibility Initiative (WAI) website. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +{::options toc_levels="2" /} +{::nomarkdown} +{% include_cached toc.html type="start" title="Page Contents" class="simple" %} +{:/} + +- TOC is created automatically. +{:toc} + +{::nomarkdown} +{% include toc.html type="end" %} +{:/} + +## Overview + +There are 3 steps to create translated versions of our resources' images: + +1. **[Translate the SVG source file](#translate-svg)** + +2. **[Export the translated image as a PNG](#export-png)** + +3. **[Commit your changes and open a Pull Request](#commit-changes)** + +## Initial step: Declare your intent + +In accordance with the WAI Translations process, please always [declare your intent](/about/translating/step-by-step/#intent) and wait for reply from WAI team _before_ starting a translation. + +## Step 1: Translate the SVG source file {#translate-svg} + +When an image from our website can be translated, it is usually provided with an SVG source file. + +In general: +- PNG images are located in the `content-images/` folder of the repository +- SVG source files are located in the `content-images/source/` folder of the repository. + +**What you will need:** +- An SVG editor. The following instructions apply to the [Inkscape](https://inkscape.org/) editor that have been used by some volunteers. +- The ["Noto Sans" font family](https://fonts.google.com/noto/specimen/Noto+Sans), including the _Regular_ and _Bold_ weights, installed on your computer. + +**Translating the SVG source file:** + +{::nomarkdown} +Date: Updated 9 November 2023.
+Date: Updated 9 April 2024.
Editors: Shawn Lawton Henry and Rémi Bétin.
Developed as part of the WAI-CooP project, co-funded by the European Commission.
--- -{::options toc_levels="2,3" /} {::nomarkdown} -{% include toc.html type="start" title="Page Contents" %} +{% include box.html type="start" h="2" title="Summary" class="full" %} +{:/} + +This page guides you through the technical steps to translate Web Accessibility Initiative (WAI) resources, and provides other important guidance. + +For instructions on translating the Web Content Accessibility Guidelines (WCAG), see [[How to Translate WCAG 2]](/about/translating/guides/wcag/). + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +{::options toc_levels="2" /} +{::nomarkdown} +{% include_cached toc.html type="start" title="Page Contents" class="simple" %} {:/} - TOC is created automatically. @@ -31,10 +44,30 @@ footer: | {% include toc.html type="end" %} {:/} -## Initial steps +## Overview + +There are 4 main technical steps to create a new WAI resource translation: + +1. **[Create a new file](#create-file)** + +2. **[Update the "front matter" metadata](#frontmatter)** + +3. **[Translate the main content](#main-content)** + +4. **[Commit your changes and open a Pull Request](#commit-changes)** + +## General 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. +- **Before starting, find the language short code "subtag"** from [Language Subtag Registry {% include_cached external.html %}](https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry). You will use it at multiple times during the translation. +- The markdown files are very sensitive to indentation, commas, quotes, and special characters. **We recommend that you use a markdown editor or a simple text editor** (including GitHub interface) — and not a document editor like Microsoft Word that often changes quotes and indentation. +- **Some resources have specific Translations notes.** If you see a comment such as "Read Translations Notes at" in the ["front matter" metadata](/about/translating/guides/new-translation/#frontmatter), follow the link and read the specific guidance.\ +If you wish to translate the [WCAG-EM Report Tool](https://www.w3.org/WAI/eval/report-tool/), please read [this specific guidance {% include_cached external.html %}](https://github.com/w3c/wai-wcag-em-report-tool/wiki/How-to-add-a-language), as different steps have to be followed. + +## Initial step: Declare your intent -Before starting: -- Find the language short code "subtag" from [Language Subtag Registry {% include_cached external.html %}](https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry). You will use it at multiple times during the translation. +In accordance with the WAI Translations process, please always [declare your intent](/about/translating/step-by-step/#intent) and wait for reply from WAI team _before_ starting a translation. ## Step 1: Create a new file {#create-file} @@ -51,7 +84,7 @@ Duplicate the file used by the original version, with the language shortcode add {% include box.html type="end" %} {:/} -## Step 2: Update "front matter" metadata {#frontmatter} +## Step 2: Update the "front matter" metadata {#frontmatter} {::nomarkdown} {% include box.html type="start" class="highlighted" %} @@ -184,6 +217,98 @@ Many resources have inline instructions in the front matter (after the "`#`" cha Please follow these instructions. It will help you know what to translate/update and what to not change. -## Step 3: Translate main content +## Step 3: Translate main content {#main-content} + +### Markdown/Code + +Please leave the code, HTML, and markdown as is without changing it. + +Make sure to: + +{::nomarkdown} +
`
+
+{::nomarkdown}
+{% include box.html type="end" %}
+{:/}
+
+{::nomarkdown}
+Date: Updated 9 November 2023.
+Date: Updated 7 March 2024.
Editors: Shawn Lawton Henry and Rémi Bétin.
Developed as part of the WAI-CooP project, co-funded by the European Commission.
--- +{::nomarkdown} +{% include box.html type="start" h="2" title="Summary" class="full" %} +{:/} + +This page explains how you can participate in reviewing translations of Web Accessibility Initiative (WAI) resources. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} -{::options toc_levels="2,3" /} +{::options toc_levels="2" /} {::nomarkdown} -{% include toc.html type="start" title="Page Contents" %} +{% include_cached toc.html type="start" title="Page Contents" class="simple" %} {:/} - TOC is created automatically. @@ -41,14 +50,95 @@ footer: | {% include toc.html type="end" %} {:/} -## Initial things to check +## Overview + +The W3C Web Accessibility Initiative (WAI) welcomes contributions to review volunteer translations, before they are published on the WAI website. + +There are 3 steps to contribute as a reviewer: + +1. **[Find a translation](#find)** ready for review + +2. **[Declare your intent](#volunteer)** to review the translation by a date. + +3. **[Review the translation](#review)** and work together with the translator(s) and other reviewer(s). + +## Step 1: How to find a translation ready for review? {#find} + +You can find translations to review in the [GitHub project {% include_cached external.html %}](https://github.com/orgs/w3c/projects/46/views/2) we use to track translations: +- Filter the view by clicking on your language in the "Language" sidebar. +- Look into the "Review" column of the board: this lists the translations that are ready for review. + +If you have trouble using this _board_ view, you can look at the [equivalent table view {% include_cached external.html %}](https://github.com/orgs/w3c/projects/46/views/3), or you can contact us at [group-wai-translations@w3.org](mailto:group-wai-translations@w3.org)[^1]. + +## Step 2: How to volunteer? {#volunteer} + +### New volunteers: + +Please send an email to [group-wai-translations@w3.org](mailto:group-wai-translations@w3.org)[^1], expressing your interest in joining the WAI translator volunteers community. We will guide you through the next steps. + +### Regular volunteers: + +Indicate that you are volunteering to review the translation in the related GitHub issue. + +**Please always indicate the date by which you plan to review the translation.** This way, we can ask other volunteers if you are unable to complete the review by this date. + +## Step 3: How to review a translation? {#review} + +Review discussions take place directly in the Pull Request(s) opened by the translator. These are listed in the GitHub issue related to the translation. + +We encourage you to respectfully share your comments, suggested changes, spotted issues; and to work together with the translator(s) and other reviewer(s) to improve the translation. + +The most important things for review are: +- **helping accurately convey the meaning from the English version** in the translated language. Translations must not change or adapt or add to the meaning of the English version in their translation. +- **using respectful disability terminology** in the target language and region. + +For that, you will need to read the English version and compare it to the translation. Often, it is best to have them open in side-by-side windows. A preview is included in most Pull Requests, to see the rendered page. + +{::nomarkdown} +{% include box.html type="start" title="Helpful tip" %} +{:/} + +A technique for proof-reading is to listen to the translation being read aloud, for example with a screen reader or text-to-speech in the operating system. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +### Specific wording {#specific-wording} +- Check [other translations in your language](/translations) to see how similar words and concepts have been translated. In particular, [Authorized Translations](https://www.w3.org/Translations/authorized.html) have had significant review and input. +- Consider different dialects. Where possible, the translation should use words and phrases that will be best understood across different areas. +- The translator and reviewer(s) might want to work together to consider different options for some wording. +- When you decide on translation of unclear words and phrases that will likely be in other resources, feel free to add them to the [Glossary for your language {% include_cached external.html %}](https://github.com/w3c/translation-glossaries). + +{::nomarkdown} +{% include box.html type="start" title="We are here to help" %} +{:/} + +If you have any questions for us about the wording, you can report them in the GitHub issue or send email to [group-wai-translations@w3.org](mailto:group-wai-translations@w3.org)[^1]. + +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. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +### Things to check {#initial-things-to-check} + +#### For all translations + +1. There is no code showing in the rendered page. +2. All of the text that should be translated, is actually translated. +3. The links work. +4. In the raw file, all alternative texts and other not-visible content are translated. + +#### For most resources on WAI website {::nomarkdown}Date: Updated 9 November 2023.
-Editors: Shawn Lawton Henry and Rémi Bétin.
-Developed as part of the WAI-CooP project, co-funded by the European Commission.
---- - -{::options toc_levels="2" /} -{::nomarkdown} -{% include toc.html type="start" title="Page Contents" %} -{:/} - -- TOC is created automatically. -{:toc} - -{::nomarkdown} -{% include toc.html type="end" %} -{:/} - -## General 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. - -## Markdown/Code - -Please leave the code, HTML, and markdown as is without changing it. - -Make sure to: - -{::nomarkdown} -`
-
-{::nomarkdown}
-{% include box.html type="end" %}
-{:/}
-
-{::nomarkdown}
-Date: Updated 9 November 2023.
+Date: Updated 9 April 2024.
Editors: Rémi Bétin and Shawn Lawton Henry.
Developed as part of the WAI-CooP project, co-funded by the European Commission.
@@ -28,6 +28,15 @@ inline_css: | } --- +{::nomarkdown} +{% include box.html type="start" h="2" title="Summary" class="full" %} +{:/} + +This page guide you through the steps to translate WAI resources using GitHub. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} {::options toc_levels="2,3" /} {::nomarkdown} @@ -41,11 +50,13 @@ inline_css: | {% include toc.html type="end" %} {:/} -## Creating a translation in GitHub - A step by step guide - {% include showhidebutton.html showtext="Show all screenshots" hidetext="Hide all screenshots" target=".screenshot" %} -### Create the translation file +## Initial step: Declare your intent + +In accordance with the WAI Translations process, please always [declare your intent](/about/translating/step-by-step/#intent) and wait for reply from WAI team _before_ starting a translation. + +## Create the translation fileWhen you have done all your checks and edits, click on the "Edit" button at the top of the Pull request view, to change the title prefix "[IN-PROGRESS]" to "[Ready for Review]"
diff --git a/_about/translating/guides/video-subtitles.md b/_about/translating/guides/video-subtitles.md index 140cecab..018bdab5 100644 --- a/_about/translating/guides/video-subtitles.md +++ b/_about/translating/guides/video-subtitles.md @@ -1,27 +1,37 @@ --- -title: "Translating Video Subtitles and Descriptions" -nav_title: Video Subtitles/Descriptions +title: "How to Create Translated Video Subtitles and Descriptions" +nav_title: Subtitles/Descriptions github: repository: w3c/wai-about-wai path: '_about/translating/guides/video-subtitles.md' permalink: /about/translating/guides/video-subtitles/ ref: /about/translating/guides/video-subtitles/ lang: en -last_updated: 2023-12-06 +last_updated: 2024-04-12 description: Help make the Web accessible to people with disabilities around the world. We appreciate your contributions to translating W3C WAI accessibility resources. image: /content-images/wai-about-wai/social-translations.png feedbackmail: wai@w3.org footer: | -Date: Updated 6 December 2023.
+Date: Updated 12 April 2024.
Editors: Shawn Lawton Henry and Rémi Bétin.
Developed as part of the WAI-CooP project, co-funded by the European Commission.
--- +{::nomarkdown} +{% include box.html type="start" h="2" title="Summary" class="full" %} +{:/} + +This page guides you through the technical steps to create new subtitles and translated descriptions for Web Accessibility Initiative (WAI) videos. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + {::options toc_levels="2" /} {::nomarkdown} -{% include toc.html type="start" title="Page Contents" %} +{% include_cached toc.html type="start" title="Page Contents" class="simple" %} {:/} - TOC is created automatically. @@ -31,6 +41,24 @@ footer: | {% include toc.html type="end" %} {:/} +## Overview + +There are 4 steps to create new subtitles or video descriptions in a new language: + +1. **[Find the related video identifier](#find-video-id)** + +2. **[Edit the video-metadata.yml file](#video-metadata)** + +3. **[Create the subtitles/descriptions file(s)](#create-vtt)** + +4. **[Translate the VTT file(s)](#translate-vtt)** + +5. **[Commit your changes and open a Pull Request](#commit-changes)** + +## Initial step: Declare your intent + +In accordance with the WAI Translations process, please always [declare your intent](/about/translating/step-by-step/#intent) and wait for reply from WAI team _before_ starting a translation. + ## Step 1: Find the related video identifier {#find-video-id} If you want to create new subtitles/translated descriptions for a video, you have probably seen the video in a W3C WAI resource. @@ -160,7 +188,7 @@ To find the path to the VTT files to translate, look at `path` and `lang-folder` {::nomarkdown} {% include box.html type="start" title="Example" %} {:/} -In this example, English VTT files are located into "/wai-folders/perspective-videos/en/" +In this example, English VTT files are located into "/wai-videos/perspective-videos/en/" ```yaml - id: keyboard @@ -202,7 +230,7 @@ If files are stored into lang subfolders, create a subfolder for your language.Date: Updated 9 April 2024.
+Editor: Rémi Bétin.
+--- + +{::nomarkdown} +{% include box.html type="start" h="2" title="Summary" class="full" %} +{:/} + +This page guides you through the technical steps to translate the Web Content Accessibility Guidelines (WCAG) 2.2 and 2.1. + + +For general information on WCAG 2 Translations, see [Contributing to W3C Translations {% include_cached external.html %} +](https://www.w3.org/Consortium/Translation/) and [Policy for Authorized W3C Translations {% include_cached external.html %}](https://www.w3.org/2005/02/TranslationPolicy.html). + + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +{::nomarkdown} +{% include_cached toc.html type="start" title="Page Contents" class="simple" %} +{:/} + +{::options toc_levels="2" /} + +- This text will be replaced by the TOC. +{:toc} + +{::nomarkdown} +{% include_cached toc.html type="end" %} +{:/} + +## Overview + +Web Content Accessibility Guidelines (WCAG) 2.1/2.2 are currently [available in more than 14 languages](/standards-guidelines/wcag/translations/)! + +There are 5 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 +2. **[Translate WCAG source files](#translate-source-files)** +3. **[Export in HTML](#preview-export)** +4. **[Edit the HTML files](#edit-html)** to complete the translation +5. **[Deliver the final files to W3C](#deliver-files)** + +## Step 1: Get the source files {#get-source-files} + +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. Base your translation on the following branch: +- [`main` branch {% include_cached external.html %}](https://github.com/w3c/wcag/tree/main) to translate WCAG 2.2 +- [`WCAG-2.1` branch {% include_cached external.html %}](https://github.com/w3c/wcag/tree/WCAG-2.1) to translate WCAG 2.1 + +## Step 2: Translate WCAG source files {#translate-source-files} + +The repository contains numerous folders and files. Only some of them are relevant to your WCAG translation. + +Translate user-oriented content in: +- `guidelines/index.html` +- All files in `guidelines/sc/` folder and subfolders +- All files in `guidelines/terms/` folder and subfolders +- `guidelines/input-purposes.html` +- `guidelines/relative-luminance.html` +- `guidelines/respect-config.js`: translate Editors list. +- `guidelines/wcag.json` +- All files in `acknowledgements/` folder + +Make sure to follow these translation guidelines: +- Update `lang` and `xml:lang` attributes in `index.html` and `relative-luminance.html`.\ + Use the appropriate language "subtag" from [Language Subtag Registry {% include_cached external.html %}](https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry) +- Do not translate IDs +- Add `hreflang="en"` to links when needed, and `lang="en"` where needed. +- Follow the guidelines of the [W3C Internationalization Activity {% include_cached external.html %}](https://www.w3.org/International/): for example, the proper usage of language tags, encoding declarations, handling bidirectional text, etc. + +## Step 3: Preview your changes and export in HTML {#preview-export} + +To preview your changes, open the `index.html` file in a modern browser, on a local server. Without a server, the success criteria and glossary terms will not be included. + +Allow the script to compile and format the content. + +1. If your document has "ReSpec" errors or warnings, they will shop up at the top of the page, next to the "ReSpec Menu" link. +- Check and resolve (potential) "ReSpec Errors". +- Check "ReSpec Warnings". The original document may contain some warnings. Make sure you do not introduce new ones. + +2. Export in HTML using ReSpec: +- Activate the "Respec Menu" link in the top right corner +- Choose "Export...", then the "HTML" option. + +## Step 4: Edit the resulting HTML file and complete the translation {#edit-html} + +Rename the exported HTML file to `index.html` and make the following changes. + +### Add the translation header + +At the very start of your `body` element, add a [translation header, based on the provided boilerplate](https://www.w3.org/2005/02/TranslationPolicy#Disclamier). + +The text in this disclaimer must be in the target language, except for the original title and the reference to the Lead Translation Organization (LTO) at the top. + +### Make some edits + +- Translate the `.head` section +- In each `dfn-panel`, translate “Permalink” and “Referenced in:” +- Next to each Success Criterion, translate “Understanding” and “How to Meet” +- Change the ID of the ["5. Conformance"](https://www.w3.org/TR/WCAG22/#conformance) `Developed as part of the WAI-CooP project, co-funded by the European Commission.
+ +#Custom frontmatter for this page +tlang: ja +--- +{% assign tlangname=site.data.lang[page.tlang].name %} +{% assign alldocs=site.documents | concat: site.pages %} + +{::nomarkdown} +{% include box.html type="start" h="2" title="Summary" class="full" %} +{:/} + +This page lists the status of {{ tlangname }} translations for most pages on the WAI website. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +{% include excol.html type="all" %} + +{% include excol.html type="start" %} + +## Priorities Status + +{% include excol.html type="middle" %} + +{::nomarkdown} +{% if site.data.translations-priorities %} + {%- for prio in site.data.translations-priorities -%} + {%- include t-status.html page=prio h="3" -%} + {%- for priosub in prio.pages -%} + {%- include t-status.html page=priosub h="3" -%} + {% include box.html type="end" %} + {%- endfor -%} + {% include box.html type="end" %} + {%- endfor -%} +{% endif %} +{:/} + +{% include excol.html type="end" %} + +## Sitemap + +{::nomarkdown} +{% assign sections=site.data.navigation | where_exp:"item", "item.mainnav != false and item.hide != true" -%} +{%- for section in sections -%} + {% include excol.html type="start" %} +Developed as part of the WAI-CooP project, co-funded by the European Commission.
+ +#Custom frontmatter for this page +tlang: ko +--- +{% assign tlangname=site.data.lang[page.tlang].name %} +{% assign alldocs=site.documents | concat: site.pages %} + +{::nomarkdown} +{% include box.html type="start" h="2" title="Summary" class="full" %} +{:/} + +This page lists the status of {{ tlangname }} translations for most pages on the WAI website. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +{% include excol.html type="all" %} + +{% include excol.html type="start" %} + +## Priorities Status + +{% include excol.html type="middle" %} + +{::nomarkdown} +{% if site.data.translations-priorities %} + {%- for prio in site.data.translations-priorities -%} + {%- include t-status.html page=prio h="3" -%} + {%- for priosub in prio.pages -%} + {%- include t-status.html page=priosub h="3" -%} + {% include box.html type="end" %} + {%- endfor -%} + {% include box.html type="end" %} + {%- endfor -%} +{% endif %} +{:/} + +{% include excol.html type="end" %} + +## Sitemap + +{::nomarkdown} +{% assign sections=site.data.navigation | where_exp:"item", "item.mainnav != false and item.hide != true" -%} +{%- for section in sections -%} + {% include excol.html type="start" %} +Developed as part of the WAI-CooP project, co-funded by the European Commission.
+ +#Custom frontmatter for this page +tlang: pl +--- +{% assign tlangname=site.data.lang[page.tlang].name %} +{% assign alldocs=site.documents | concat: site.pages %} + +{::nomarkdown} +{% include box.html type="start" h="2" title="Summary" class="full" %} +{:/} + +This page lists the status of {{ tlangname }} translations for most pages on the WAI website. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +{% include excol.html type="all" %} + +{% include excol.html type="start" %} + +## Priorities Status + +{% include excol.html type="middle" %} + +{::nomarkdown} +{% if site.data.translations-priorities %} + {%- for prio in site.data.translations-priorities -%} + {%- include t-status.html page=prio h="3" -%} + {%- for priosub in prio.pages -%} + {%- include t-status.html page=priosub h="3" -%} + {% include box.html type="end" %} + {%- endfor -%} + {% include box.html type="end" %} + {%- endfor -%} +{% endif %} +{:/} + +{% include excol.html type="end" %} + +## Sitemap + +{::nomarkdown} +{% assign sections=site.data.navigation | where_exp:"item", "item.mainnav != false and item.hide != true" -%} +{%- for section in sections -%} + {% include excol.html type="start" %} +Date: Updated 9 November 2023.
+Date: Updated 9 April 2024.
Editors: Shawn Lawton Henry and Rémi Bétin.
Developed as part of the WAI-CooP project, co-funded by the European Commission.
--- @@ -33,7 +33,7 @@ To get announcements related to WAI translations, subscribe to the WAI Translati {% include box.html type="end" %} {:/} -{::options toc_levels="2,3" /} +{::options toc_levels="2" /} {::nomarkdown} {% include_cached toc.html type="start" title="Page Contents" %} {:/} @@ -45,9 +45,21 @@ To get announcements related to WAI translations, subscribe to the WAI Translati {% include_cached toc.html type="end" %} {:/} -Thank you for taking the time to contribute to WAI accessibility resources translations! +## Overview -This resource will guide you through the important steps to creating and reviewing translations. +There are 6 steps to contribute as a volunteer translator: + +1. **[Find a resource to translate](#find-resource)** + +2. **[Inform us of your intent to translate a resource](#intent)** + +3. **[Translate the resource](#start-translation)** + +4. **[Preview and check your translation](#preview)** + +5. **[Ask for reviews](#review)** + +6. **[Wait for publication](#publication)** Before starting your work, please take the time to read the information in [[Translating WAI Resources]](/about/translating/), and verify that you are willing to contribute under these policies. @@ -60,7 +72,7 @@ Discussions, collaboration with reviewers and progress tracking are more easily - If you do not already have a GitHub Account, [sign up {% include_cached external.html %}](https://github.com/signup) for an account; - If you are new to GitHub, we recommend that you follow this interactive free course:\ [Introduction to GitHub {% include_cached external.html %}](https://github.com/skills/introduction-to-github); -- Then, for more specific guidance during the translation process, you can deep dive with our [[Using Github]](/about/translating/guides/using-github/) guide. +- For more specific guidance during the translation process, you can deep dive with our [[Using Github]](/about/translating/guides/using-github/) guide. {::nomarkdown} {% include box.html type="start" title="Important Note" class="simple" %} @@ -74,20 +86,18 @@ If you are unsure how to proceed and need guidance; or if you are not comfortabl {% include box.html type="end" %} {:/} -## Translating Resources {#translating} - {% include excol.html type="all" %} {% include excol.html type="start" %} -### Step 1: Find a resource to translate {#find-resource} +## Step 1: Find a resource to translate {#find-resource} {% include excol.html type="middle" %} -#### Have a look at our priorities +### Have a look at our priorities For suggestions on which to translate first, see [Priorities for Translations](#priorities). -#### Or pick a resource according to your preference +### 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. @@ -101,7 +111,7 @@ Translations sitemaps display the structure of WAI website, and indicate for eac {% include excol.html type="start" %} -### Step 2: Inform us of your intent to translate a resource {#intent} +## Step 2: Inform us of your intent to translate a resource {#intent} {% include excol.html type="middle" %} @@ -120,13 +130,13 @@ When you have found a resource to translate, you must indicate your interest, an Please wait for reply from WAI team before starting a translation. -#### Recommended / quickest way {#translation-issue} +### Recommended / quickest way {#translation-issue} 1. From the [translations sitemap](/about/translating/sitemaps/) for your language, click on the "Volunteer to translate this page" link, displayed next to the resource you intend to translate. 2. It will automatically pre-fill a GitHub issue with some useful information. 3. Read and submit the issue. -#### Alternatives: +### Alternatives: - [Create an Issue in the dedicated "WAI Translations" repository](https://github.com/w3c/wai-translations/issues/new). - If you are not comfortable with GitHub, send e-mail to the publicly-archived WAI translations list using [this e-mail template](mailto:public-wai-translations@w3.org?subject=%5Blang%5D%20Intent%20to%20Translate%3A%20%5Btitle%5D&body=I%20would%20like%20to%20translate%20into%20%5Blanguage%5D%20the%20following%20resource%3A%0A%5BEnglish%20title%5D%0A%5BURI%5D%0A%0AI%20have%20read%20the%20information%20on%20Translating%20WAI%20Documents%20at%20https%3A%2F%2Fwww.w3.org%2FWAI%2Fabout%2Ftranslating%2F%0A%0AI%20will%20wait%20for%20confirmation%20that%20the%20resource%20is%20ready%20for%20translation.). @@ -134,11 +144,11 @@ Please wait for reply from WAI team before starting a translation. {% include excol.html type="start" %} -### Step 3: Start translating {#start-translation} +## Step 3: Start translating {#start-translation} {% include excol.html type="middle" %} -#### Initial setup +### Initial setup 1. Log in to your existing GitHub account, or [create one {% include_cached external.html %}](https://github.com/signup). 2. Get to the repository of the resource you will translate. @@ -148,26 +158,24 @@ Please wait for reply from WAI team before starting a translation. For further guidance on using GitHub to translate a WAI resource, follow the [dedicated guide](/about/translating/guides/using-github/). -#### Translate the resource +### Translate the resource - Refer to [[Creating a Translation]](/about/translating/guides/new-translation/) guide -- If the page you are translating has videos, also refer to [[Creating Video Subtitles/Descriptions]](/about/translating/guides/video-subtitles/) -- Read the [[Translating Guidance]](/about/translating/guides/translation-guidance/). +- If the page you are translating has videos, also refer to [[How to Create Translated Video Subtitles and Descriptions]](/about/translating/guides/video-subtitles/) +- If the page you are translating has images with text, also refer to [[How to Translate Images]](/about/translating/guides/video-subtitles/) - Commit your changes. {% include excol.html type="end" %} {% include excol.html type="start" %} -### Step 4: Preview and check your translation {#preview} +## Step 4: Preview and check your translation {#preview} {% include excol.html type="middle" %} -We have enabled a preview with Netlify so you can check your file and make edits. - 1. Open a [draft Pull Request {% include_cached external.html %}](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) in the GitHub repository of the resource, with `[IN-PROGRESS]` at the beginning of the title. -2. After you submit the pull request, a preview will be generated. +2. 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. @@ -182,7 +190,7 @@ We have enabled a preview with Netlify so you can check your file and make edits {% include excol.html type="start" %} -### Step 5: Ask for reviews {#review} +## Step 5: Ask for reviews {#review} {% include excol.html type="middle" %} @@ -201,7 +209,7 @@ If you have any questions about the wording, please report them in the GitHub is {% include excol.html type="start" %} -### Step 6: Wait for publication {#publication} +## Step 6: Wait for publication {#publication} {% include excol.html type="middle" %} @@ -264,46 +272,4 @@ Please note these steps may take some time depending on other ongoing priorities {%- endif -%} -## Reviewing Translations {#reviewing} - -Translations are reviewed by volunteers and WAI team before they are published. - -{% include excol.html type="all" %} - -{% include excol.html type="start" %} - -### Step 1: Find translations ready for review - -{% include excol.html type="middle" %} - -{::nomarkdown} -{% include box.html type="start" title="New volunteer?" class="highlighted" %} -{:/} -Thank you so much for your interest in reviewing W3C WAI Resources! - -First and foremost, send an email to [group-wai-translations@w3.org](group-wai-translations@w3.org) (not publicly archived [^1]) to express your interest in joining the WAI translator volunteers community. - -{::nomarkdown} -{% include box.html type="end" %} -{:/} - -1. Explore the [WAI Translations GitHub project {% include_cached external.html %}](https://github.com/orgs/w3c/projects/46/views/2) - - Look into the "Ready for review" column to find translations ready for review. - - You can filter the view by clicking on your language in the "Language" column. - - If you have trouble using this _board_ view, you can look at the [equivalent table view {% include_cached external.html %}](https://github.com/orgs/w3c/projects/46/views/3) - -2. Communicate you are volunteering to review, by leaving a comment in the corresponding issue. - -{% include excol.html type="end" %} - -{% include excol.html type="start" %} - -### Step 2: Review the translation - -{% include excol.html type="middle" %} - -Follow [Reviewing translations](/about/translating/guides/review-translation/) step-by-step guide. - -{% include excol.html type="end" %} - [^1]: Emails sent to `group-wai-translations@w3.org` are not publicly visible. \ No newline at end of file diff --git a/_about/translating/translations-sitemaps.md b/_about/translating/translations-sitemaps.md index 87002600..24008480 100644 --- a/_about/translating/translations-sitemaps.md +++ b/_about/translating/translations-sitemaps.md @@ -30,5 +30,8 @@ Translation sitemaps display the structure of WAI website, and indicate for each - [German (de)](/about/translating/sitemaps/sitemap-de/) - [Greek (el)](/about/translating/sitemaps/sitemap-el/) - [Indonesian (id)](/about/translating/sitemaps/sitemap-id/) + - [Japanese (ja)](/about/translating/sitemaps/sitemap-ja/) + - [Korean (ko)](/about/translating/sitemaps/sitemap-ko/) + - [Polish (pl)](/about/translating/sitemaps/sitemap-pl/) - [Russian (ru)](/about/translating/sitemaps/sitemap-ru/) - [Spanish (es)](/about/translating/sitemaps/sitemap-es/) \ No newline at end of file diff --git a/_about/update.md b/_about/update.md index c95dc223..667b35d9 100644 --- a/_about/update.md +++ b/_about/update.md @@ -1,6 +1,6 @@ --- title: "What We're Working On" -title_html: "What We're Working OnDate: Updated 22 December 2023. First published March 2022.
-Editor: Shawn Lawton Henry. Contributors: Participants of the EOWG and others working on accessibility at W3C.
-Developed with the Accessibility Education and Outreach Working Group (EOWG).
+Date: Updated 26 March 2024. First published March 2022.
+Editor: Shawn Lawton Henry. Contributors: WAI staff, Working Group Co-Chairs, and others working on accessibility at W3C.
inline_css: | h1 { @@ -78,17 +77,16 @@ We hope you'll find accessibility work on this page that you are interested in c * **Cognitive Accessibility** — We're updating several documents to better address the needs of people with cognitive and learning disabilities. A current topic is mental health. [[Cognitive Accessibility at W3C]](/cognitive/). _[AG WG, COGA TF]_ +* **Low Vision Accessibility** — We're writing guidance that goes beyond the minimums required by WCAG. It is called "supplemental guidance". Current topics cover proximity, printing, and alternative themes such as high contrast and dark mode. _[AG WG, Low Vision TF]_ --> * **Mobile Accessibility** work includes supporting on-going standards development, including supporting WCAG 3 exploration. [[Mobile Accessibility at W3C]](/standards-guidelines/mobile/) _[AG WG, Mobile TF]_ -### Updating Guidance on EPUB Accessibility and on Applying WCAG to ICT - -* **EPUB Fixed Layout Accessibility** aims to help publishers address challenges for people with cognitive disabilities and low vision. [EPUB Fixed Layout Accessibility Editor's Draft](https://w3c.github.io/epub-specs/epub33/fxl-a11y/) _[EPUB3 WG, FXL A11y TF]_ +### Updating Guidance on Applying WCAG to ICT and on EPUB Accessibility * **WCAG2ICT** describes how Web Content Accessibility Guidelines (WCAG) 2 can be applied to non-web information and communications technologies (ICT). We are updating it to include WCAG 2.1 and WCAG 2.2. [[WCAG2ICT Overview]](/standards-guidelines/wcag/non-web-ict/) _[AG WG, WCAG2ICT TF]_ +* **EPUB Fixed Layout Accessibility** aims to help publishers address challenges for people with cognitive disabilities and low vision. [EPUB Fixed Layout Accessibility Editor's Draft](https://w3c.github.io/epub-specs/epub33/fxl-a11y/) _[EPUB3 WG, FXL A11y TF]_ + ### Defining User Requirements (AUR) and Exploring Emerging Technologies Documenting the user needs of people with disabilities helps develop standards to meet those needs. It also helps designers, developers, and others better understand and meet user needs in order to support accessibility. XR Accessibility User Requirements and more listed at [Digital Accessibility User Requirements](https://www.w3.org/WAI/research/user-requirements/). @@ -97,21 +95,24 @@ Documenting the user needs of people with disabilities helps develop standards t * **Collaboration Tools Accessibility User Requirements ("CTAUR")** is a Working Draft. It describes user needs in tools that provide support for one or more specific collaborative features. These features include real-time editing of content by multiple authors, the use of comments or annotations, and revision control. [CTAUR Editor's Draft](https://w3c.github.io/ctaur/) _[APA WG, Research TF]_ -* **How People with Disabilities Use the Web** helps you understand user needs broadly. We're updating this resource and publishing new videos to go along with it. Previous version: [[How People with Disabilities Use the Web]](/people-use-web/) _[EOWG]_ +* **How People with Disabilities Use the Web** helps you understand user needs broadly. We're updating this resource and publishing new videos to go along with it. [[How People with Disabilities Use the Web - previous version]](/people-use-web/), [in-progress update of How People with Disabilities Use the Web](https://deploy-preview-113--wai-people-use-web.netlify.app/people-use-web/) ### Testing Accessibility, Evaluation Tools +* **Easy Checks – A First Review of Web Accessibility** helps you start to assess the accessibility of a web page. We are polishing up a new iteration of this popular resource. [Easy Checks - previous version](/test-evaluate/preliminary/), [draft new version of Easy Checks](/easy-checks/) * **ACT Rules** (Accessibility Conformance Testing (ACT), also known as "WCAG 2 Test Rules") describe ways to test conformance to WCAG success criteria. They are primarily for developers of evaluation tools and test methodologies. We're documenting more. [[About WCAG 2 Test Rules]](/standards-guidelines/act/rules/about/) _[AG WG, ACT TF]_ * ACT Rules implementation reports list how test tools or methodologies address test examples in ACT Rules. We invite evaluation tool developers to [submit implementation reports](https://act-rules.github.io/pages/implementations/reporting/). _[AG WG, ACT TF]_ +### Translating Resources + +Existing translations of W3C accessibility resources are listed in [All WAI Transations](/translations/). We are currently working with volunteer translators to translate more resources and update existing translations, including translations of WCAG and of educational resources. See [Translating WAI resources](/about/translating/). + ## Upcoming Publications -We plan to publish the following documents in Q1 2024, which is January, February, March. To learn about "Candidate Recommendation" (**CR**) and other stages, see [How WAI Develops Accessibility Standards through the W3C Process: **Milestones** and Opportunities to Contribute](https://www.w3.org/WAI/standards-guidelines/w3c-process/). +We plan to publish the following documents in Q2 (March, April, May) 2024. -* More [WAI Translations](/translations/) -* [Guidance on Applying WCAG 2.2 to Non-Web Information and Communications Technologies (WCAG2ICT) Draft](https://www.w3.org/TR/2023/DNOTE-wcag2ict-20230815/) updates -* [ARIA](/standards-guidelines/aria/) 1.3 as a First Public Working Draft -* [Core Accessibility API Mappings 1.2](https://www.w3.org/TR/core-aam-1.2/) as an updated CR +* More [WAI Translations](/translations/) - usually some each week +* [Guidance on Applying WCAG 2.2 to Non-Web Information and Communications Technologies (WCAG2ICT) Draft](https://www.w3.org/TR/2023/DNOTE-wcag2ict-20230815/) updates in Q2 * and some updated educational resources Recent publications and other announcements are listed on the **[News page](/news/)**. @@ -126,14 +127,14 @@ This page _only lists about half_ of the active work on accessibility at W3C. Mu To learn more about what the Working Groups are working on right now, see: -* [EOWG Current Work](https://www.w3.org/WAI/EO/wiki/EOWG_Current_Projects) - lists over 20 current and upcoming projects of the Accessibility Education and Outreach (EO) Working Group + * [APA Current Work](https://www.w3.org/WAI/APA/#work) - Accessible Platform Architectures (APA) Working Group * ARIA - Accessible Rich Internet Applications (ARIA) Working Group * [ARIA Working Drafts](https://www.w3.org/groups/wg/aria/publications#WD) * [ARIA Authoring Practices Guide (APG)](https://www.w3.org/WAI/ARIA/apg/) * [AG WG Current Work](https://www.w3.org/WAI/GL/#work) - Accessibility Guidelines (AG) Working Group * [COGA Current Work](https://www.w3.org/WAI/GL/task-forces/coga/wiki/Main_Page) - Cognitive and Learning Disabilities Accessibility Task Force (COGA) - * [LVTF Current Work](https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page) - Low Vision Accessibility Task Force (LVTF) + * [Mobile Current Work](https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Main_Page) - Mobile Accessibility Task Force * [EPUB 3 Working Group document publication status and milestones](https://www.w3.org/publishing/groups/epub-wg/PublStatus) @@ -151,17 +152,10 @@ Links to each Working Group's "How to Participate" page are in the [Participatin We also offer ideas for [Promoting and Implementing Web Accessibility](https://www.w3.org/WAI/about/participating/#promoting-and-implementing-web-accessibility). -We welcome translations! If you might want to volunteer to contribute to translations, please see [Translating WAI resources](/about/translating/). +**Translations:** If you might want to volunteer to contribute to translations, please see [Translating WAI resources](/about/translating/). You can send questions via e-mail to [group-wai-translations@w3.org](group-wai-translations@w3.org) We are currently seeking translators in all languages and reviewers for draft translations in Czech, Greek, Indonesian and Korean. **We look forward to your contributions to making the web more accessible to people with disabilities!** - -_If you heard about W3C WAI strategic plannning, you can get more info from:_ -* **[Draft W3C Accessibility Mission, Vision, Objectives](https://wai-mission.netlify.app/draft/)** -* **[Discussion topics in GitHub](https://github.com/w3c/wai-mission/discussions)** -* Background: [Draft W3C Accessibility 2023 Context](https://wai-mission.netlify.app/2023/) -* [Presentation to W3C Members September 2023](https://www.w3.org/2023/09/TPAC/ac-activities-wai.html) - video, slides with links, transcript - ### Who is We "We" is: @@ -172,12 +166,8 @@ _If you heard about W3C WAI strategic plannning, you can get more info from:_ * [Kevin White](https://www.w3.org/staff/#kevin) is Accessibility Technical Lead and supports the Accessibility Guidelines Working Group that develops Web Content Accessibility Guidelines (WCAG). * [Roy Ruoxi Ran (冉若曦)](https://www.w3.org/staff/#ran) supports accessibility Working Groups and accessibility in China. * [Daniel Montalvo](https://www.w3.org/staff/#dmontalvo) supports accessibility Working Groups and standards harmonization in Europe. - * [Akosua “Kosi” Asabere](https://www.w3.org/staff/#kosi) joined the W3C Team in November 2023 and brings first-hand experience with mobile accessibility in Africa. * Participants of: [AG](https://www.w3.org/groups/wg/ag/participants), [APA](https://www.w3.org/groups/wg/apa/participants), [ARIA](https://www.w3.org/groups/wg/aria/participants), [EPUB](https://www.w3.org/groups/wg/epub/participants), [EO](https://www.w3.org/groups/wg/eowg/participants), and other [W3C groups](https://www.w3.org/groups/) -_W3C WAI Team photos:_ -
-