W3C home > Mailing lists > Public > public-agwg-comments@w3.org > March 2021

Comment: WCAG 3.0 - Issue: Accessibility to Web Content Requiring a CAPCHA for Access

From: Rod Macdonald <rjmacdonald@hawaiiantel.net>
Date: Wed, 24 Feb 2021 20:25:19 -1000
Message-ID: <20210225062519.rjmacdonald@hawaiiantel.net>
To: public-agwg-comments@w3.org
Cc: rjmacdonald@hawaiiantel.net
To: Accessibility Guidelines Working Group
From: Rod Macdonald (rjmacdonald@hawaiiantel.net)

Re: W3C Accessibility Guidelines (WCAG) 3.0 - W3C First Public Working Draft 21 January 2021

Issue: Accessibility to Web Content Requiring a CAPCHA for Access

Background: For purposes of this discussion, individuals who are Deaf-Blind can be grouped into four sub-groups:

(1) The Deaf-Blind individual retains sufficient residual hearing, with amplification and/or other enhancements, to access web content in the of a hearing person.

(2) The Deaf-Blind individual retains sufficient residual vision, with screen magnification and/or other enhancements, to access web content in the manner of a sighted person.

(3) The Deaf-Blind individual cannot access web content via speech or hearing, but can do so using braille.

(4) The Deaf-Blind individual cannot access web content using vision, hearing or braille, and thus cannot access web content at all. (There may be extremely rare cases when the use of unusual technology may circumvent this.)

This discussion refers exclusively to Deaf-Blind individuals in the third group - braille users.

Problem: Numerous providers of online services use a technique called a "CAPCHA" (Google calls theirs a "RECAPCHA") to ensure that customers are in fact human. Highly stylized characters are displayed on the screen and the user is asked to type the characters on the keyboard. Vision is required to do this. Typically, an audio work-around is provided so that blind individuals can gain access. However, there is no known workaround if the consumer does not have the vision OR the hearing to gain access. A consumer using a screen reader and braille display is completely excluded. 

Comments: There is no known solution to this accessibility issue.
Received on Monday, 1 March 2021 14:42:29 UTC

This archive was generated by hypermail 2.4.0 : Monday, 1 March 2021 14:42:38 UTC