RatedWithAI

RatedWithAI

Accessibility scanner

Free Scan

WCAG 2.1

4.1.3 Status Messages

Level AA success criterion

Status messages should be programmatically determined without receiving focus.

Why it matters

Screen reader users need to hear confirmations, errors, and updates without hunting for them.

Common violations

  • Form success messages not announced
  • Toast notifications without ARIA live regions
  • Error banners that require manual focus

Code examples

Bad

<div class="toast">Saved</div>

Good

<div role="status" aria-live="polite">Saved</div>

How to fix

Use aria-live regions for dynamic updates and ensure messages are announced automatically.

Related criteria

3.3.2 Labels or Instructions1.4.1 Use of Color4.1.2 Name, Role, Value

Related resources

Google accessibility scoreYouTube accessibility scoreSpotify accessibility scoreWordPress accessibility guideShopify accessibility guideSquarespace accessibility guide

Test & fix this criterion

Use these free tools and guides to check and fix 4.1.3 Status Messages violations:

Free accessibility checker — find WCAG violations automaticallyColor contrast checker — test contrast ratiosHow to fix common WCAG failuresTop 10 most common WCAG failures

Scan your site

Check your WCAG coverage in minutes

Start a free scan