Re: Accessible Authentication

On 15/11/2023 00:29, Kevin Prince wrote:
> To further cast the cat amongst the pigeons - the normative version, 
> https://www.w3.org/TR/WCAG22/#accessible-authentication-minimum, 
> <https://www.w3.org/TR/WCAG22/#accessible-authentication-minimum,> links 
> to a normative definition of process that includes as the 2nd example 
> "An account registration page requires successful completion of a Turing 
> test before the registration form can be accessed."

See https://github.com/w3c/wcag/pull/3538

> That would make it clear that a registration form is covered despite the 
> intentions of the drafters.

Not quite, because the SC isn't scoped to *any* process (and the 
definition for process gives an example of a registration process), but 
more narrowly to *authentication* process.

> To return to the Understanding doc simply replacing the words 'log in" 
> with "authentication/ate" in the following section would help:
> In Brief
> Goal
> Make logins possible with less mental effort.
> What to do
> Don't make people solve, recall, or transcribe something to log in.
> Why it's important
> Some people with cognitive disabilities cannot solve puzzles, memorize a 
> username and password, or retype one-time passcodes.
> 
> The examples section does not limit anything to merely log ins 5/7 
> examples mention only authenticate.

PRs always welcome (though they can take forever to be looked at / 
merged / whatever)

P
-- 
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
https://mastodon.social/@patrick_h_lauke | skype: patrick_h_lauke

Received on Wednesday, 15 November 2023 01:53:30 UTC