E-mail List Archives
Re: wcag 3.3.4
From: Maxability Accessibility for all
Date: Jul 16, 2016 2:05AM
- Next message: Bhaskarjyoti Hazarika: "Re: wcag 3.3.4"
- Previous message: Bossley, Pete: "Re: Web applicationtesting"
- Next message in Thread: Bhaskarjyoti Hazarika: "Re: wcag 3.3.4"
- Previous message in Thread: Murray Inman (DZZEX54291): "Re: wcag 3.3.4"
- View all messages in this Thread
Hi Jennison,
I still feel it as violation for 3.3.4. I don't find a mechanism to check
the data entered by the user is checked for input errors in cases where a
manual error can happen. Eg: I can enter credit card 1 number in CC number
field and provide CVV of credit card2. Or I want to enter the details of a
card I have but I want to use another card. If I have a review screen I can
check the details of the card before finalizing the purchase.
On Fri, Jul 15, 2016 at 3:21 AM, Murray Inman (DZZEX54291) <
<EMAIL REMOVED> > wrote:
> Jennison,
> When you say "validated" I presume you mean that it is checked for correct
> form (e.g. the CC # doesn't violate any rules). I would think that 3.3.4 is
> trying to give the user a chance to easily review what was typed in for
> correctness rather than for correct form. The user could type in the
> information for credit card A but meant to type in the information for
> credit card B.
>
> I personally would say that it would not pass the rule.
>
> [image: Rio Salado College Logo]
> [image: Rio Facebook] <https://www.facebook.com/RioSaladoCollege> [image:
> Rio Twitter] <https://twitter.com/RioSaladoOnline> [image: Rio YouTube]
> <http://www.youtube.com/user/riosaladocollege> [image: Rio Google+]
> <https://plus.google.com/+riosalado/about>
> *Murray Inman*
> System Applications Analyst / Information Services
> Tel: 480-517-8610 | Fax: 480-377-4817 | <EMAIL REMOVED>
> 2323 W. 14th Street Tempe, AZ 85281 | www.riosalado.edu
> ------------------------------
> A Maricopa Community College
> Strengths: Individualization
> <http://classweb.riosalado.edu/murray.inman/StrengthsQuest/> | Ideation
> <http://classweb.riosalado.edu/murray.inman/StrengthsQuest/> | Relator
> <http://classweb.riosalado.edu/murray.inman/StrengthsQuest/> |
> Connectedness
> <http://classweb.riosalado.edu/murray.inman/StrengthsQuest/> | Input
> <http://classweb.riosalado.edu/murray.inman/StrengthsQuest/>
>
> On Thu, Jul 14, 2016 at 2:41 PM, Jennison Mark Asuncion <
> <EMAIL REMOVED> > wrote:
>
> > Looking for a sanity check - imagine a screen with fields: credit card
> > #, month and year of expiration, and postal code. The Place Order
> > button is disabled until all fields are completed and validated (e.g.,
> > if the CC # is incorrect, a message is dynamically displayed). Once
> > the Place Order button is pressed, the order is in fact being placed,
> > and there is text letting the user know this is the case.
> >
> > Based on WCAG 3.3.4, one of the following must be true:
> > 1) Reversible: Submissions are reversible.
> > 2) Checked: Data entered by the user is checked for input errors and
> > the user is provided an opportunity to correct them.
> > 3) Confirmed: A mechanism is available for reviewing, confirming, and
> > correcting information before finalizing the submission.
> >
> > Based on this, I am saying this meets 3.3.4, specifically #2. Am I on
> > track?
> >
> > Jennison
> > > > > > > > > >
> > > > >
- Next message: Bhaskarjyoti Hazarika: "Re: wcag 3.3.4"
- Previous message: Bossley, Pete: "Re: Web applicationtesting"
- Next message in Thread: Bhaskarjyoti Hazarika: "Re: wcag 3.3.4"
- Previous message in Thread: Murray Inman (DZZEX54291): "Re: wcag 3.3.4"
- View all messages in this Thread