WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: WCAG 3.3.2 vs 3.3.3

for

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

From: allyssa jessicon
Date: Wed, Jul 13 2022 8:57AM
Subject: WCAG 3.3.2 vs 3.3.3
No previous message | Next message →

Hello everyone,

I have had a hard time understanding the difference between WCAG 3.3.2 and
3.3.3

Can you folks help me understand how is it different? Labels or
instructions and suggestions seem like so much related.


Thanks,
Alyssa.

From: Patrick H. Lauke
Date: Wed, Jul 13 2022 9:35AM
Subject: Re: WCAG 3.3.2 vs 3.3.3
← Previous message | Next message →

On 13/07/2022 15:57, allyssa jessicon wrote:
> Hello everyone,
>
> I have had a hard time understanding the difference between WCAG 3.3.2 and
> 3.3.3

Naive answer: 3.3.2 is about labels or instructions, 3.3.3 about error
messages?

Basic example of missing label:

<input type="text" name="username">

without any visible label that gives the user a hint that you're
expecting them to enter their username there, it fails 3.3.2 Labels or
Instructions. that part has nothing to do with 3.3.3 Error Suggestion
(no error has occurred yet here)

Basic example of missing instruction:

Say you have something like

<label for="foo">Choose a password</label>
<input type="password" id="foo" name="password">

but you also require this password to have specific characteristics
("only A-Z, numbers, underscores, at least one number, etc"), and you
don't tell the user anywhere about this, then that would fail 3.3.2
Labels of Instructions for not having an actual instruction. Now, you
may think "but if I then show it once they try to submit and fail, do I
pass?", then I'd say the answer is no. At that point, it's too late /
the user has already had to do one submission/roundtrip to discover
after the fact that there were specific instructions/requirements...

Basic example of missing error suggestion:

Say the user submits something in a form, it's an error for some reason,
but you don't show/explain explicitly what the error actually is (only
something generic a la "this is wrong, try again" with no further
info)...then that would fail 3.3.3

Of course, there *can* be a bit of an overlap between these two SCs. For
instance, if you have clear labels and instructions, the error message
you show after a failed submission can probably be a bit more terse if
it's just a case of "you didn't follow the required format which we've
already outlined over there in the instructions".

P
--
Patrick H. Lauke

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

From: Barry
Date: Wed, Jul 13 2022 9:44AM
Subject: Re: WCAG 3.3.2 vs 3.3.3
← Previous message | Next message →

W3C have a very useful resource that I call Understanding success criterion...". Here's what it says about 3.3.2:

" The intent of this success criterion is to have content authors place instructions or labels that identify the controls in a form so that users know what input data is expected. Instructions or labels may also specify data formats for fields especially if they are out of the customary formats or if there are specific rules for correct input. Content authors may also choose to make such instructions available to users only when the individual control has focus especially when instructions are long and verbose."


https://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html

And here's what it says about 3.3.3:

" The intent of this Success Criterion is to ensure that users receive appropriate suggestions for correction of an input error if it is possible. The WCAG 2.0 definition of "input error" says that it is "information provided by the user that is not accepted" by the system. Some examples of information that is not accepted include information that is required but omitted by the user and information that is provided by the user but that falls outside the required data format or allowed values."

https://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-suggestions.html

So, the first SC is about giving hints for inputs and the second is feedback on an error.

Cheers

Barry

From: allyssa jessicon
Date: Thu, Jul 14 2022 11:29AM
Subject: Re: WCAG 3.3.2 vs 3.3.3
← Previous message | No next message

Thanks Patrick and Barry. I really appreciate your response. I think I have
what I was looking for now.

Thanks again.

Alyssa.

On Wednesday, July 13, 2022, Barry via WebAIM-Forum <
= EMAIL ADDRESS REMOVED = > wrote:

> W3C have a very useful resource that I call Understanding success
> criterion...". Here's what it says about 3.3.2:
>
> " The intent of this success criterion is to have content authors place
> instructions or labels that identify the controls in a form so that users
> know what input data is expected. Instructions or labels may also specify
> data formats for fields especially if they are out of the customary formats
> or if there are specific rules for correct input. Content authors may also
> choose to make such instructions available to users only when the
> individual control has focus especially when instructions are long and
> verbose."
>
>
> https://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html
>
> And here's what it says about 3.3.3:
>
> " The intent of this Success Criterion is to ensure that users receive
> appropriate suggestions for correction of an input error if it is possible.
> The WCAG 2.0 definition of "input error" says that it is "information
> provided by the user that is not accepted" by the system. Some examples of
> information that is not accepted include information that is required but
> omitted by the user and information that is provided by the user but that
> falls outside the required data format or allowed values."
>
> https://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-suggestions.html
>
> So, the first SC is about giving hints for inputs and the second is
> feedback on an error.
>
> Cheers
>
> Barry
>
>