W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2015

Re: SC 3.3.4

From: Priti Rohra <priti.rohra@gmail.com>
Date: Tue, 28 Apr 2015 16:52:40 +0530
Message-ID: <CAEAadGwcWatSXonQ1_foObZAUYLfssdcN_h84RgdAasESVjjgQ@mail.gmail.com>
To: "Mattes, Kurt X1" <Kurt.X1.Mattes@chase.com>
Cc: David Woolley <forums@david-woolley.me.uk>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Hi All,

I believe if we go strictly by the success criteria's definition, if
the form checks for errors and presents users with errors it satisfies
the SC. However, a point to remember is that form error will check the
inputs as per the set validations but the errors that can happen due
to unintentionally pressing a key or incorrectly entering the
telephone no. etc and such errors won't be presented as an error. This
can cause serious consequences if it is a financial transaction.

As an user, I will prefer to have the details reviewed before hitting
the Submit/Confirm button.

Having said that if it is not technically possible to edit the entered
data, how about including an Alert as soon as users fill up the first
step and hits the submit button and including a check box that
confirms: I have reviewed the details  entered... The alert should
also clearly mention that details once submitted can not be changed.

This will help meet the SC and take care of the user's requirements.

Regards,
Priti Rohra


On 4/27/15, Mattes, Kurt X1 <Kurt.X1.Mattes@chase.com> wrote:
> Personally I prefer a final verification screen prior to submitting a form
> with any financial implications. However, in a longer multi-step process
> verification at each step may be easier for people with cognitive
> disabilities as long as it affords an easy way to locate and correct any
> errant user provided information.
>
> Regards,
> Kurt Mattes
> VP - eCAT ADA Controls | JPMorgan Chase
>
> ________________________________________
> From: David Woolley [forums@david-woolley.me.uk]
> Sent: 27 April 2015 AM 07:07:17
> To: w3c-wai-ig@w3.org
> Subject: Re: SC 3.3.4
>
> On 27/04/15 10:49, Emanuela Gorla wrote:
>> I still believe that a review screen that allows users to check and
>> correct information is the best solution. However, would a website that
>> does not have a review screen but checks for input errors on each form
>> of a purchasing process satisfy SC 3.3.4?
>>
>
>
> What are the consequences of entering invalid data?  How easy is it to
> correct later?  Can correction be done at no cost to the user.
>
> Anything that involves a payment, and especially if shipping, or
> customisation, or non-refundable commission costs may be incurred,
> really needs a review screen.  Statistical information that will be
> anonymised, probably doesn't, as long as a few errors will not
> significantly distort the results.
> This transmission may contain information that is proprietary, privileged,
> confidential, and/or exempt from disclosure under applicable law.  If you
> are not the intended recipient, you are hereby notified that any disclosure,
> copying, distribution, or use of the information contained herein (including
> any reliance thereon) is STRICTLY PROHIBITED.  If you received this
> transmission in error, please immediately contact the sender and destroy the
> material in its entirety, whether in electronic or hard copy format.
> Although this transmission and any attachments are believed to be free of
> any virus or other defect that might affect any computer system into which
> it is received and opened, it is the responsibility of the recipient to
> ensure that it is virus free and no responsibility is accepted by JPMorgan
> Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"), as
> applicable, for any loss or damage arising in any way from its use.  Please
> note that any electronic communication that is conducted within or through
> JPMC's system is subject to interception, monitoring, review, retention and
> external production; may be stored or otherwise processed in countries other
> than the country in which you are located; and will be treated in accordance
> with JPMC's policies and applicable laws and regulations.
>
>
Received on Tuesday, 28 April 2015 11:23:08 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 25 May 2017 01:54:15 UTC