RE: How 2.4.5 Multiple Ways ought to apply to software

My understanding is we should be taking WCAG at face value.  I do not believe that this list is the correct venue for discussing If something is meant by that example other than what it plainly states.


From: Gregg Vanderheiden [mailto:gv@trace.wisc.edu]
Sent: Friday, August 10, 2012 9:30 AM
To: Michael Pluke
Cc: Bailey, Bruce; Andi Snow-Weaver; public-wcag2ict-tf@w3.org
Subject: Re: How 2.4.5 Multiple Ways ought to apply to software

that example was added to say

"If the only way to get to some page is to go first through a CAPTCHA page -- then you do not have to have a second way to get to that page (besides the captcha page) because doing a CAPTCHA first is part of the process. "

[snip]

From: Bailey, Bruce [mailto:Bailey@Access-Board.gov<http://Access-Board.gov>]
Sent: 10 August 2012 12:56
To: Andi Snow-Weaver; public-wcag2ict-tf@w3.org<mailto:public-wcag2ict-tf@w3.org>
Subject: How 2.4.5 Multiple Ways ought to apply to software

For Tuesday, might we survey if task force members believe that most (all?) software falls into the "except where the [X] is the result of, or a step in, a process" half of 2.4.5?

I submit that WCAG has a pretty broad definition of "process".  Please see Example 2:  "An account registration page requires successful completion of a Turing test before the registration form can be accessed."
http://www.w3.org/TR/WCAG20/#processdef