WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Error prevention on required fields

for

From: Maxability
Date: Jul 17, 2019 11:34PM

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 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
>>