Error Suggestion
When a user input error is detected and suggestions for correction are known, the suggestions must be provided unless doing so would jeopardize security.
What it requires
WCAG 2.0 SC 3.3.3 takes 3.3.1 a step further: error messages must include suggestions for fixing the error when known. Not just "Invalid date" but "Invalid date — please use the format MM/DD/YYYY".
Security exemption: password fields generally don't expose what was wrong (would help attackers). Most other fields can and should give specific guidance.
Common Shopify failure
Address form with "Postcode is invalid" and no suggestion — should be "Postcode is invalid — UK postcodes use the format SW1A 1AA". Phone field with "Invalid format" — should suggest "Use international format: +1 555 123 4567".
How to fix it
AccessComply pairs each form-validation error with a per-field suggestion drawn from a known-formats library; falls back to the merchant's manual error message when present.
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 3.3.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 3.3.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 guided partial 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.0 Understanding 3.3.3