E-mail List Archives

Search E-mail List Archives for

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

From: Sumit Patel
Date: Sun, Apr 27 2025 2:33AM
Subject: Clarification on Error suggestion and Error identification
No previous message | Next message →

Hi all,
I just have a couple of queries regarding WCAG 3.3.1 (Error Identification)
and 3.3.3 (Error Suggestion) criteria, and I’d appreciate your insights.
1.
Invalid Date Input
When we input a date in an invalid format in the date edit field and press
the Tab key, the input gets removed without any error message or feedback.
Would this be considered a failure under 3.3.3 (Error Suggestion), or does
it fall under a different criterion?
2.
Type Dropdown Field
There’s a dropdown where initially no values are shown. When a user types a
keyword, results appear if there’s a match; otherwise, it shows a “No
results” message. Since the accepted inputs are always alphabetic, even
typing numbers shows the same "No results" message.
Should we consider adding a more specific message like “Please enter
alphabets only” when digits are entered, to meet the 3.3.3 requirement? Or
is the current behavior acceptable under WCAG?
Looking forward to your thoughts.

Regards,
Sumit.

From: Birkir R. Gunnarsson
Date: Sun, Apr 27 2025 6:33AM
Subject: Re: Clarification on Error suggestion and Error identification
← Previous message | No next message

In the first situation, I'm not sure.
It feels like it's not so much about the error message itself but more
about what is sufficiently accessible inline form validation.
I typically do not go too specific on inline form validation as long as
there's clear error messaging when the user tries to submit a form with
errors.
For inline form validation I recommend validating on blur and coding the
error message as a live region or using built-in browser validation (not
perfectly accessible but getting better).
The only exception to inline validation is either when the user types in an
invalid character or exceeds the maximum number of characters.

For your second scenario, it fails labels or instructions (3.3.2). If you
only get results if you type in alphabetical characters that should be part
of the form instructions for that search input.
So it's more about the instructions than the error message.


On Sun, Apr 27, 2025 at 4:33 AM Sumit Patel via WebAIM-Forum <
= EMAIL ADDRESS REMOVED = > wrote:

> Hi all,
> I just have a couple of queries regarding WCAG 3.3.1 (Error Identification)
> and 3.3.3 (Error Suggestion) criteria, and I’d appreciate your insights.
> 1.
> Invalid Date Input
> When we input a date in an invalid format in the date edit field and press
> the Tab key, the input gets removed without any error message or feedback.
> Would this be considered a failure under 3.3.3 (Error Suggestion), or does
> it fall under a different criterion?
> 2.
> Type Dropdown Field
> There’s a dropdown where initially no values are shown. When a user types a
> keyword, results appear if there’s a match; otherwise, it shows a “No
> results” message. Since the accepted inputs are always alphabetic, even
> typing numbers shows the same "No results" message.
> Should we consider adding a more specific message like “Please enter
> alphabets only” when digits are entered, to meet the 3.3.3 requirement? Or
> is the current behavior acceptable under WCAG?
> Looking forward to your thoughts.
>
> Regards,
> Sumit.
>
>

--
Work hard. Have fun. Make history.