Edit comment LC-2534 for Accessibility Guidelines Working Group

Previous: LC-2549 Next: LC-2540

Comment LC-2534: Comment Shortname:; Commenter: Roberto Scano <r.scano@webprofession.com>; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
Hi, an issue that comes out here in Italy (where in the next month we will
have approved the government law upgrade for follow WCAG 2.0) about the
audio captcha.

http://www.w3.org/TR/WCAG20-TECHS/G144.html

a lot of audio captcha are in English language so there is need to put
something in techniques / examples regarding that an alternative audio
captcha for visual captcha should (I prefer must) respect the primary
language of the page.; Related issues: (space separated ids); WG Notes: From Vivienne Conway: You would get my hearty approval on that one. From Sailesh Panchang: Indeed. Really this is a no-brainer, as they say, and I imagine it requires no thought to determine that the alt text or equivalent audio CAPTCHA or audio description for a/v presentation must be in the primary or default language of the page. So when one selects Spanish or German or Italian or any available language from available languages for a Web page from the language selector, all content should be rendered in that language. Except for content that needs to be in a different language else it would change its essential character / meaning. Alt text and equivalent audio CAPTCHA or audio description do not make this exception. Organizations spend time and cost in making sure that Web page content is translated accurately into the different languages it needs to be rendered. In some situations they may face a legal risk if they do not. Yet during the extensive translation process they overlook the alt-text and other equivalents like CAPTCHA and audio descriptions maybe because it is out of sight or the attributes and values never existed in the first place to be translated. So I too see this question cropping up time and again and maybe for the removal of doubt, a clarification should be provided in Understanding SC 3.1.1 and Understanding SC 1.1.1. Additional Thoughts/Considerations for WG Discussion: It seems like a captcha in a different modality should use the same "human language" (I believe that's the term defined in WCAG and used in 3.1.1?) as the original (visual?) captcha, but had a preliminary question: Are there any situations you can think of where it makes sense to not use the "human language" of the original (visual?) captcha in an alternate captcha? If the answer is yes, than maybe we could say "The alternate Captcha task should use the same human language as the original Captcha task if appropriate/practical" at end of "description" section of the referenced technique (G144)..; Resolution: The WCAG WG thanks you for your comment. For clarification, we have decided to add "Some CAPTCHA tasks rely on understanding written or spoken language. Such CAPTCHAS should use the same language as the main language of the page." at the end of the "description" section of the referenced technique (G144). We are also filing this issue with the Protocols and Formats Working Group to request that this issue be further explored in the document "Inaccessibility of CAPTCHA" <http://www.w3.org/TR/turingtest/>.; (Please make sure the resolution is adapted for public consumption)