WebAIM - Web Accessibility In Mind

E-mail List Archives

for

From: Laurence Lewis
Date: Aug 1, 2025 6:34PM

Dear Accessibility Experts,

I'm seeking clarification on how WCAG 2.2 Success Criterion 4.1.3: Status
Messages (Level AA)
<https://www.w3.org/WAI/WCAG22/Understanding/status-messages> applies in
the following scenario:

A date range input is constructed using three separate form fields
displayed horizontally:
*Day* / *Month* / *Year* — e.g., DD/MM/YYYY.

If a user enters an invalid value in *any* of the three fields (e.g., "32"
in the Day input), an error message appears spanning underneath the group
of three inputs when the user leaves the field (onBlur). This error message
is *not* placed in a live region and therefore is not announced by a screen
reader at the time it appears.

My understanding has previously been that this may *not* strictly violate
SC 4.1.3 if the error is later programmatically exposed on form submission
(i.e., focus returns to the invalid field and the error is then announced).
However, on reviewing the Understanding document more closely —
particularly the *Success Techniques* section referencing *ARIA22* and
*G199* — it appears that *immediate* announcement is required when the
error message appears:

“After a user enters incorrect text in an input called Postal Code, a
message appears above the input reading 'Invalid entry'. The screen reader
announces, 'Invalid entry' or 'Postal code, invalid entry.'”

This would suggest that the failure to announce the error when it is
generated — even on blur — *is* a violation, given that screen reader users
are not informed of the error until the Submit button is clicked and
focus is sent to the first, if many, input in error. This is then announced
via aria-describedby on the input.

Given the structure of the date input (where the error spans multiple
related fields and input is sequential), announcing the error on blur could
be helpful, yet I’m also aware of potential confusion in a linear set of
controls, announcing onBlur would be confusing as the user has already left
the input in error and landed on the next focusable element or moved away
by virtual cursor. .

*My questions:*

- Is the absence of a live region announcement onBlur for an invalid
value in one of the date inputs a *strict violation* of 4.1.3? Or any
time this functionality occurs.



I welcome any thoughts or references to existing interpretations. I'm happy
to be corrected as part of continuous learning.

Thanks,
Laurence Lewis
Accessibility Senior Specialist | Telstra