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
AccessComply rewrites toast / status / spinner Liquid templates to wrap messages in `role="status"` containers and ensures dynamically-injected text passes through an `aria-live` region.
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 treats WCAG 4.1.3 as a rendered-storefront issue first. The scanner checks the live DOM and computed styles, maps the finding back to the Shopify theme file that produced it, then classifies the fix as a safe automatic fix. When automation is safe, the app writes the smallest theme-code change needed and keeps the original theme backup available. When merchant judgment is required, the issue is surfaced for manual review instead of pretending the page is fixed.
Primary source: W3C — WCAG 2.1 Understanding 4.1.3