E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 6 (In chronological order)

From: dinesh tripathi
Date: Tue, Jul 09 2019 9:17PM
Subject: Error prevention on required fields
No previous message | Next message →

Hello,
There is a long form with more than 100 required fields in multiple sections of single page. Each section has ‘Save' button. The form might not finish in single sitting. When I save each section without entering required fields, error message doesn't occurr but error message published on the page when hit ‘Save and Submit' button which is OK. Can I expect error or warning message to meet the error prevention WCAG requirement when I save each section with empty required fields?
Thank you,Dinesh

From: Patrick H. Lauke
Date: Wed, Jul 10 2019 1:31AM
Subject: Re: Error prevention on required fields
← Previous message | Next message →

On 10/07/2019 04:17, dinesh tripathi via WebAIM-Forum wrote:
> Hello,
> There is a long form with more than 100 required fields in multiple sections of single page. Each section has ‘Save' button. The form might not finish in single sitting. When I save each section without entering required fields, error message doesn't occurr but error message published on the page when hit ‘Save and Submit' button which is OK. Can I expect error or warning message to meet the error prevention WCAG requirement when I save each section with empty required fields?

When saving only, it makes sense for errors not to show / prevent the
saving. So yes I'd say there's no requirement at that point for error
prevention, since the user isn't trying to actually submit the data so
an error in a field or an incomplete required field won't have any
adverse effect anyway at that point.

Long story short: the error prevention requirement arguably only applies
when you're actually trying to submit, not just saving/stashing the data.

P
--
Patrick H. Lauke

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

From: Tim Harshbarger
Date: Wed, Jul 10 2019 9:58AM
Subject: Re: Error prevention on required fields
← Previous message | Next message →

If the sole purpose of the Save button is to save the current state of the form so a user can complete it later, I don't think any of the WCAG success criteria related to error prevention or providing error information would apply. So that aspect of the UI should be fine as it relates to errors.
Thanks,
Tim
Tim Harshbarger
Senior Accessibility Consultant
Deque Systems

From: Lucy Greco
Date: Wed, Jul 10 2019 11:07AM
Subject: Re: Error prevention on required fields
← Previous message | Next message →

i would find this form a bad user experience. if there are that many form
elaments and i save part of the form and want to go back later how do i
know what i have filled in already and not filled in i think that
messages letting me jump back to the empty fields would be a big help are
you stuck on makeing this one page this form sounds like a nightmare to
fill out
lucy
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces



On Wed, Jul 10, 2019 at 8:59 AM Tim Harshbarger < = EMAIL ADDRESS REMOVED = >
wrote:

> If the sole purpose of the Save button is to save the current state of the
> form so a user can complete it later, I don't think any of the WCAG success
> criteria related to error prevention or providing error information would
> apply. So that aspect of the UI should be fine as it relates to errors.
> Thanks,
> Tim
> Tim Harshbarger
> Senior Accessibility Consultant
> Deque Systems
>

From: John Foliot
Date: Thu, Jul 11 2019 9:52AM
Subject: Re: Error prevention on required fields
← Previous message | Next message →

Hi All,

I'll split this even more finely than my colleague Tim: If the sole purpose
of the Save button is to save the current state of the form so a user can
complete it later, then it MAY take advantage of notifying the end user
there are errors, but currently WCAG does not mandate that it MUST do so,
as long as errors are properly noted on Submit.

(MUST, SHOULD, or MAY in the RFC 2119 context
https://tools.ietf.org/html/rfc2119)

JF

On Thu, Jul 11, 2019 at 10:20 AM Tim Harshbarger < = EMAIL ADDRESS REMOVED = >
wrote:

> If the sole purpose of the Save button is to save the current state of the
> form so a user can complete it later, I don't think any of the WCAG success
> criteria related to error prevention or providing error information would
> apply. So that aspect of the UI should be fine as it relates to errors.
> Thanks,
> Tim
> Tim Harshbarger
> Senior Accessibility Consultant
> Deque Systems
>

From: Maxability
Date: Wed, Jul 17 2019 11:34PM
Subject: Re: Error prevention on required fields
← Previous message | No next message

I agree with Lucy. This is a great example for me to talk about the
difference between user experience and compliance.


Thanks & regards

Rakesh

On 7/11/2019 9:22 PM, John Foliot wrote:
> Hi All,
>
> I'll split this even more finely than my colleague Tim: If the sole purpose
> of the Save button is to save the current state of the form so a user can
> complete it later, then it MAY take advantage of notifying the end user
> there are errors, but currently WCAG does not mandate that it MUST do so,
> as long as errors are properly noted on Submit.
>
> (MUST, SHOULD, or MAY in the RFC 2119 context
> https://tools.ietf.org/html/rfc2119)
>
> JF
>
> On Thu, Jul 11, 2019 at 10:20 AM Tim Harshbarger < = EMAIL ADDRESS REMOVED = >
> wrote:
>
>> If the sole purpose of the Save button is to save the current state of the
>> form so a user can complete it later, I don't think any of the WCAG success
>> criteria related to error prevention or providing error information would
>> apply. So that aspect of the UI should be fine as it relates to errors.
>> Thanks,
>> Tim
>> Tim Harshbarger
>> Senior Accessibility Consultant
>> Deque Systems
>>