Skip to content

Error Status Messages (accessibility) #1745

@robeastwood-agency

Description

@robeastwood-agency

Is your feature request related to a problem? Please describe.
Created on behalf of accessibility expert:

As per GitHub ticket: #1350, error identification methods have been reverted to standard behavior. Errors are now displayed immediately when detected, without requiring users to tab beyond the input field—this aligns with the intended design.
However, these error messages are not announced dynamically by screen readers when they appear. Currently, users must tab past the input field and shift focus to the error message element to discover the issue. This behaviour violates WCAG 2.1 Success Criterion 4.1.3 (Status Messages), which requires that status messages be programmatically conveyed to assistive technologies without a focus change.(https://www.w3.org/WAI/WCAG21/Understanding/status-messages.html)

Describe the solution you'd like
Implement ARIA live regions to ensure error messages below input fields are automatically announced by screen readers without requiring a focus shift, meeting WCAG 2.1 SC 4.1.3 (Status Messages).

  • Add role="alert" and aria-live="assertive" to error message containers.
  • Link error messages to their respective inputs using aria-describedby.

This fix ensures users relying on assistive technologies receive immediate feedback on form errors, improving usability and compliance with WCAG.

Describe alternatives you've considered
None

Additional context
None

Metadata

Metadata

Assignees

Labels

accessibilityAccessibility-related issue

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions