- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Fri, 10 Aug 2012 08:30:20 -0500
- To: Michael Pluke <Mike.Pluke@castle-consult.com>
- Cc: "Bailey, Bruce" <Bailey@Access-Board.gov>, Andi Snow-Weaver <andisnow@us.ibm.com>, "public-wcag2ict-tf@w3.org" <public-wcag2ict-tf@w3.org>
- Message-id: <CB27D4B6-F6E1-4349-B762-CD0DDB769E0C@trace.wisc.edu>
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. " Gregg -------------------------------------------------------- Gregg Vanderheiden Ph.D. Director Trace R&D Center Professor Industrial & Systems Engineering and Biomedical Engineering University of Wisconsin-Madison Technical Director - Cloud4all Project - http://Cloud4all.info Co-Director, Raising the Floor - International and the Global Public Inclusive Infrastructure Project http://Raisingthefloor.org --- http://GPII.net On Aug 10, 2012, at 8:21 AM, Michael Pluke <Mike.Pluke@castle-consult.com> wrote: > I am not against surveying this, but I don’t really think that all software is covered by the process exception. > > I would suggest that modal dialog boxes are definitely steps in a process. Once you have initiated the print “process” the next, and sometimes final step in the process, is a modal dialog box with print options and a “Print” or “Cancel” button. This modal dialog box, which is an “interaction context” in M376-speak (and hence analogous to a Web page that is a step in a process). > > In “interaction context”-speak, 2.4.5 becomes: > > “More than one way is available to locate an interaction context within a set of interaction contexts except where the interaction context is the result of, or a step in, a process.” > > The print dialog is an “interaction context. It is the result of (a step in) a process” and should not therefore provide multiple ways of accessing parts of the main application (we are beginning to agree that an application represents one or more interaction contexts “within a set of interaction contexts” – equivalent to a “set of Web pages”). > > However, if an application (which maps to “a set of interaction contexts”) contains several interaction contexts (e.g. the multiple sections of Outlook) then 2.4.5 says that I should be given multiple ways of accessing those different parts e.g. the Navigation bar to the right of the Outlook window, Control + numeric, and maybe more methods. > > Best regards > > Mike > > From: Bailey, Bruce [mailto:Bailey@Access-Board.gov] > Sent: 10 August 2012 12:56 > To: Andi Snow-Weaver; 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 > > > From: Andi Snow-Weaver [mailto:andisnow@us.ibm.com] > Sent: Thursday, August 09, 2012 7:07 PM > To: public-wcag2ict-tf@w3.org > Subject: ACTION: Meeting Preparation Survey for tomorrow - Please answer before the meeting if possible > Sorry for the late notice. At tomorrow's meeting, we're going to step back from the issue of finding a replacement term for "web page" and discuss how task force members fundamentally believe 2.4.1 Bypass Blocks and 2.4.5 Multiple Ways ought to apply to software. > > To help structure the discussion, we have prepared a survey: https://www.w3.org/2002/09/wbs/55145/AUG102012/ > > Please answer it before the meeting if you can. I won't set the usual 6 AM US Eastern time deadline. > > Andi >
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Friday, 10 August 2012 13:30:54 UTC