Summary of the translation of WCAG2.1 to Dutch
Eric Velleman <[email protected]> Wed, 15 Apr 2020 10:17:30 +0200
| Newsgroups | gmane.org.w3c.translators.general |
|---|---|
| Message-ID | <CACaX0g_h7SETFwaUuwqpgghLTLDn3KgBLpbbCJx=1T8kRYs4RQ@mail.gmail.com> |
--0000000000002bddd605a34ff360 Content-Type: text/plain; charset="UTF-8" Dear reader, The LTO and stakeholders are proud to present to you the final CAT for the authorized translation of WCAG2.1 to Dutch. A lot of hard and creative work was done to produce an accurate translation into Dutch. The LTO would like to thank all stakeholders for their support and active commenting en input during the translation process. After the first version of the translation was provided to the stakeholders internally, we received many comments and organized a telco to help discussion and decide on the best terminology for the translation. We launched the formal CAT in November 2019 and the formal review period extended till January 10, 2020 [1]. We received 158 good comments, most of them general and editorial changes, none of them were substantive [2]. For the comments we asked reviewers to follow a format we used earlier for the translation of WCAG2.0 (with columns: Status; ID; Reviewer name; Reviewer organization; Section; Subsection/SC; Type of comment (GE/TE/ED); Current text; Comment; Proposed change; Assigned to; Group observation; Resolution). Using this format everybody can see and check what has been done with their own and others' comments. Most comments led to direct improvements of the text. Many comments were the same, Some comments were discarded as they would change the meaning of the text as compared to the English version. We talked to stakeholders about their comments and based on all the input and comments launched a new CAT on February 26 [3][4]. We then asked the stakeholders to review the CAT and let us know if they agree that it is an accurate translation of WCAG2.1. A large majority of stakeholders have agreed [5][6]. 19 of the 23 stakeholders (including the Benelux Chapter of W3C) have in fact reviewed the translation and consider it to be an accurate translation. 4 stakeholders have not responded to the request. In one case the person working at the stakeholder had just changed jobs and could not be reached. We received no objections. We are happy and proud to present the end result. The LTO wishes to thank all the stakeholders for their work and input for the translation. The final list of stakeholders can be found on the W3C mailing list [7]. Eric Velleman Scientific Director Accessibility Foundation Innovation Expert Bartimeus [1] https://lists.w3.org/Archives/Public/public-auth-trans-nl/2019Dec/0000.html [2] https://lists.w3.org/Archives/Public/public-auth-trans-nl/2020Feb/0000.html [3] https://lists.w3.org/Archives/Public/public-auth-trans-nl/2020Feb/0001.html [4] https://accessibilitynl.github.io/WCAG21-NL/translations/WCAG21-nl/ [5] https://lists.w3.org/Archives/Public/public-auth-trans-nl/2020Mar/ [6] https://lists.w3.org/Archives/Public/public-auth-trans-nl/2020Apr/ [7] https://lists.w3.org/Archives/Public/w3c-translators/2020AprJun/0006.html --0000000000002bddd605a34ff360 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Dear reader,=C2=A0<br><br>The LTO and stakeholders are pro= ud to present to you the final CAT for the authorized translation of WCAG2.= 1 to Dutch. A lot of hard and creative work was done to produce an accurate= translation into Dutch. The LTO would like to thank all stakeholders for t= heir support and active commenting en input during the translation process.= =C2=A0<br><br>After the first version of the translation was provided to th= e stakeholders internally, we received many comments and organized a telco = to help discussion and decide on the best terminology for the translation. = We launched the formal CAT in November 2019 and the formal review period ex= tended till January 10, 2020 [1]. We received 158 good comments, most of th= em general and editorial changes, none of them were substantive [2]. For th= e comments we asked reviewers to follow a format we used earlier for the tr= anslation of WCAG2.0 (with columns: Status; ID; Reviewer name; Reviewer org= anization; Section; Subsection/SC; Type of comment (GE/TE/ED); Current text= ; Comment; Proposed change; Assigned to; Group observation; Resolution). Us= ing this format everybody can see and check what has been done with their o= wn and others' comments. Most comments led to direct improvements of th= e text. Many comments were the same, Some comments were discarded as they w= ould change the meaning of the text as compared to the English version.<br>= <br>We talked to stakeholders about their comments and based on all the inp= ut and comments launched a new CAT on February 26 [3][4]. We then asked =C2= =A0the stakeholders to review the CAT and let us know if they agree that it= is an accurate translation of WCAG2.1. A large majority of stakeholders ha= ve agreed [5][6]. 19 of the 23 stakeholders (including the Benelux Chapter = of W3C) have in fact reviewed the translation and consider it to be an accu= rate translation. 4 stakeholders have not responded to the request. In one = case the person working at the stakeholder had just changed jobs and could = not be reached. We received no objections.<br><br>We are happy and proud to= present the end result. The LTO wishes to thank all the stakeholders for t= heir work and input for the translation. The final list of stakeholders can= be found on the W3C mailing list [7].<br><br>Eric Velleman<br>Scientific D= irector Accessibility Foundation<div>Innovation Expert Bartimeus</div><div>= <br><br>[1] <a href=3D"https://lists.w3.org/Archives/Public/public-auth-tra= ns-nl/2019Dec/0000.html">https://lists.w3.org/Archives/Public/public-auth-t= rans-nl/2019Dec/0000.html</a><br>[2] <a href=3D"https://lists.w3.org/Archiv= es/Public/public-auth-trans-nl/2020Feb/0000.html">https://lists.w3.org/Arch= ives/Public/public-auth-trans-nl/2020Feb/0000.html</a><br>[3] <a href=3D"ht= tps://lists.w3.org/Archives/Public/public-auth-trans-nl/2020Feb/0001.html">= https://lists.w3.org/Archives/Public/public-auth-trans-nl/2020Feb/0001.html= </a><br>[4] <a href=3D"https://accessibilitynl.github.io/WCAG21-NL/translat= ions/WCAG21-nl/">https://accessibilitynl.github.io/WCAG21-NL/translations/W= CAG21-nl/</a><br>[5] <a href=3D"https://lists.w3.org/Archives/Public/public= -auth-trans-nl/2020Mar/">https://lists.w3.org/Archives/Public/public-auth-t= rans-nl/2020Mar/</a><br>[6] <a href=3D"https://lists.w3.org/Archives/Public= /public-auth-trans-nl/2020Apr/">https://lists.w3.org/Archives/Public/public= -auth-trans-nl/2020Apr/</a><br>[7] <a href=3D"https://lists.w3.org/Archives= /Public/w3c-translators/2020AprJun/0006.html">https://lists.w3.org/Archives= /Public/w3c-translators/2020AprJun/0006.html</a></div></div> --0000000000002bddd605a34ff360--