Skip to main content
All WCAG Criteria
4.1.3
AA

Status Messages

Robust › 4.1 Compatible › WCAG 2.1

Overview

In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

Understanding

The W3C Web Accessibility Initiative (WAI) provides detailed guidance on understanding and implementing this criterion. The Understanding document covers the intent, benefits, and supporting techniques in depth.

Read Understanding 4.1.3 on W3C WAI

Techniques

W3C provides documented techniques for meeting this criterion. Each technique links to the full specification with code examples and test procedures.

How to Test

  1. Run an HTML validator to check for parsing errors.

  2. Test with multiple browsers and assistive technologies (NVDA, JAWS, VoiceOver).

  3. Inspect ARIA roles and properties for correct usage.

  4. Verify that status messages are programmatically exposed without receiving focus.

How VPATify tests this

VPATify runs automated WCAG checks against every page you scan and flags violations against individual success criteria. Our deep scan combines axe-core, contrast analysis, and structural checks to catch criterion-level failures that single-tool scans miss. See the full testing methodology and features for what's covered at each level.

Run a deep scan

Want deeper accessibility insights?

Scan your entire website and generate an official VPAT document — free, in minutes.

Scan Your Site — It's Free