Stone & saffron pages.
Semantic HTML, sufficient contrast across the stone + saffron palette, visible focus states, keyboard navigation through primary flows, and screen-reader-friendly alt text.
Accessibility
Built for everyone
to use.
ClearConsent targets WCAG 2.1 Level AA conformance for the marketing site, the in-Shopify embed app, and the consent banners we generate for merchant storefronts. This page describes the current state honestly — what's working, what's known to need work, and how to report an issue.
An accessibility statement should be a snapshot of reality, not aspiration. If we say we're AA-conformant, we mean it — and if we know about gaps, we name them here.
/ The principle
Reviewed for conformance
What's working today.
The marketing site, in-Shopify app, and generated consent banner have been reviewed against WCAG 2.1 Level AA criteria and are believed to meet that target.
Storefront banner.
Keyboard-navigable end-to-end, announces its dialog role to screen readers, maintains focus trap while open, and respects prefers-reduced-motion.
In-Shopify app.
Form controls have associated labels, every toggle is reachable by keyboard with a visible focus ring, and the Theme Editor "embed enabled" prompt uses Shopify's own a11y-approved patterns.
Known limitations
Where we're still working.
Three gaps we're aware of and actively addressing.
Generated PDF reports
Audit-export PDFs are visually styled but not fully tagged for screen readers. Request a tagged-PDF or accessible alternative version via the contact form if you need one.
Animated landing reveals
Some scroll-triggered animations on the marketing home page may produce unexpected motion for users not setting prefers-reduced-motion. The query is respected; report any breakage.
Color-only legacy reports
A handful of older report layouts use color (red/green/yellow) without secondary indicators. Newer report views use both color and icons; we're migrating the older layouts.
Banner specifics
The cookie banner itself.
The cookie banner ClearConsent injects on merchant storefronts is the part visitors actually interact with. Four accessibility commitments.
Fully navigable.
Tab cycles through Accept / Reject / Preferences in logical order. Enter/Space activates. Esc closes the preferences modal where present.
Announces as dialog.
role="dialog" + aria-labelledby on the banner heading. Preferences modal traps focus while open and restores focus on close.
Validated at install.
Default banner color presets are contrast-validated at AA. Merchants who customize colors can fail this; the banner designer warns if a chosen pair drops below 4.5:1.
Respects preference.
Banner slide-in animation is suppressed under prefers-reduced-motion: reduce. The banner appears instantly instead of animating in.
Reporting an issue
How to flag a problem.
If you encounter an accessibility barrier on any ClearConsent surface, contact us via the contact form with three things.
URL or surface.
The exact URL, page, or in-app surface where the issue occurred — marketing site, embed app, storefront banner, or generated report.
Assistive tech.
The assistive technology you're using (screen reader name, keyboard-only navigation, voice control, magnification, etc.).
Expected vs actual.
What you expected to happen and what happened instead. A short description is fine; screenshots optional.
Accessibility-related reports are triaged at the same priority as production-affecting issues. We acknowledge receipt within one business day and provide a remediation timeline within five business days, even if the fix itself takes longer.
Standards
What we conform to.
The conformance target is Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, published by the W3C. WCAG 2.1 Level AA is widely used as a benchmark for digital accessibility and is commonly referenced in accessibility laws, regulations, and procurement requirements.
This statement was last reviewed in May 2026. Substantive changes to the accessibility of ClearConsent's surfaces will be reflected here.
Found something?
Tell support.
A barrier on any surface — marketing site, embed app, storefront banner, or generated report — gets the same priority as a production-affecting issue.