W3C home > Mailing lists > Public > public-rqtf@w3.org > June 2019

Re: CAPTCHA Comment: character based section I18N considerations [I18N] (#29)

From: Janina Sajka <janina@rednote.net>
Date: Tue, 4 Jun 2019 08:34:04 -0400
To: Scott Hollier <scott@hollier.info>
Cc: "public-rqtf@w3.org" <public-rqtf@w3.org>
Message-ID: <20190604123404.GQ10743@rednote.net>
Thanks, Scott!

I like it, at least on first read. Let me give it a little time to see
whether any concern pops up. If not, I'll just drop this replacement in
to the Editor's Draft before our call Wednesday.

Best,

Janina

Scott Hollier writes:
> To Janina
> 
> I reckon the following addresses all the points raised: see what you think.
> 
> Scott
> 
> *** BEGIN NEW TEXT *** 
>  
> While some sites have begun providing CAPTCHAs utilizing languages other than English, an assumption that all web users can understand and reproduce English predominates. Clearly, this is not the case. Users of Arabic or Thai character sets, for example, may not be familiar with the English alphabet or may not have enough knowledge to identify a distorted version of such characters.  Furthermore, the default keyboard is likely to be localised, potentially making it difficult to enter an alternative character set unless specifically set up to do so.  
> 
> *** END NEW TEXT *** 
> 
> Dr Scott Hollier 
> Digital Access Specialist 
> Mobile: +61 (0)430 351 909
> Web: www.hollier.info
>  
> Technology for everyone
>  
> Looking to upskill your staff with digital access training? Fill the room for one flat fee. 
>  
> Keep up with digital access news by following @scotthollier on Twitter and subscribing to Scott's newsletter. 
> 
> -----Original Message-----
> From: Janina Sajka <janina@rednote.net> 
> Sent: Tuesday, 4 June 2019 7:04 AM
> To: public-rqtf@w3.org
> Subject: CAPTCHA Comment: character based section I18N considerations [I18N] (#29)
> 
> Scott:
> 
> Would you be able to take on incorporating this comment into our draft?
> 
> This comment is from the I18N review we requested early in May and comes via github here:
> 
> https://github.com/w3c/apa/issues/29
> 
> If not, no worries. Just advise. Thanks!
> 
> Janina
> 
> Addison Phillips writes:
> > 2.1.1 Traditional Character-Based CAPTCHA 
> > https://w3c.github.io/apa/captcha/#traditional-character-based-captcha
> > 
> > > While some sites have begun providing CAPTCHAs utilizing languages other than English, an assumption that all web users can understand and reproduce English predominates. Clearly, this is not the case. Arabic or Thai speakers, for example, should not be assumed to possess a proficiency with the ISO 8859-1 character set [iso-8859-1], let alone have a keyboard that can easily produce those characters in the CAPTCHA's form field. Research has demonstrated how CAPTCHAs based on written English impose a significant barrier to many on the web; see Effects of Text Rotation, String Length, and Letter Format on Text-based CAPTCHA Robustness [captcha-robustness].
> > 
> > The above text has several potential issues:
> > 
> > 1. ISO8859-1 ("Latin-1") is possibly not the best reference here, since probably is what is meant are ASCII letters and digits. The difference between Latin-1 and ASCII are the various accented letters, which are not widely used in CAPTCHA.
> > 2. Virtually all computing systems have a means of inputting ASCII, so saying that users might not have a "keyboard that can easily produce those characters" is probably false. 
> > 3. The reverse is not true. Producing CAPTCHA images containing non-ASCII text may prove difficult to use if the user does not have the appropriate keyboard available. It is difficult to determine on the server side what the input capabilities of a given user agent includes.
> > 4. Many characters or writing systems are difficult to discern when distorted. This includes accented Latin-script letters, cursive scripts such as Arabic, and of course Han ideographs.
> > 5. It has been observed that using actually words for CAPTCHA improves accuracy, but or course this depends on being fluent in the language in question.
> > 
> > *This comment is part of the I18N horizontal review. *
> > 
> > --
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly or view it on GitHub:
> > https://github.com/w3c/apa/issues/29
> 
> -- 
> 
> Janina Sajka
> 
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup:	http://a11y.org
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
> 
> 

-- 

Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Tuesday, 4 June 2019 12:35:01 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 17 January 2023 20:26:46 UTC