Status Messages
Status messages (success confirmations, error notices, progress updates) must be programmatically determinable through ARIA live regions so assistive technology announces them without requiring focus.
What it requires
WCAG 2.1 SC 4.1.3 covers the asynchronous interaction layer: "Item added to cart", "Form saved successfully", "Verifying your order…". These messages appear visually but, without ARIA live regions, are silent to screen readers.
The fix: wrap status messages in `<div role="status" aria-live="polite">` for non-urgent updates, or `aria-live="assertive"` for time-critical ones (errors, deadline alerts).
Common Shopify failure
Cart drawer shows "Added to your cart" toast — visible to sighted users, invisible to screen readers. Search auto-suggest dropdown updates result counts silently. "Loading…" spinner with no live-region announcement.
How to fix it
Expose non-urgent updates through an appropriate status or polite live region, and reserve assertive announcements for genuinely urgent messages. Test that dynamic text updates are announced once without unexpectedly moving focus.
Merchant QA checklist
- Scan the storefront page where this pattern appears: product pages, collection pages, cart drawer, customer-account pages, and any landing page built with theme sections.
- Confirm the issue is fixed in the rendered browser output, not only in the Liquid file. Shopify section settings, app blocks, and third-party scripts can reintroduce the same 4.1.3 failure after a theme edit.
- Re-test the affected component with keyboard navigation and a screen-reader accessibility tree before publishing the theme, especially when the fix changes markup or ARIA attributes.
How AccessComply handles it
AccessComply uses automated rules to check supported patterns in the pages reached during a scan. Some WCAG requirements need human judgment, assistive-technology testing, or access to third-party content and cannot be established by an automated scan. This criterion is generally treated as a pattern that may have a supported suggested fix. If the app can safely match the issue to supported source code, the merchant must review and approve the suggested change before anything is written, and the result is checked afterward. Otherwise the merchant should use the guidance above and independent hands-on testing. The label is not a guarantee of detection, a fix, WCAG conformance, or legal compliance.
Primary source: W3C — WCAG 2.1 Understanding 4.1.3