WCAG & Compliance
An accessibility statement tells users what you support today, how you’re improving, and how they can get help. It reduces legal risk, builds trust with customers and regulators, and creates a clear plan for ongoing work. Use the templates below and tailor them to your site, product, and processes. After you’ve set foundations, add Adjustable for user-side controls that improve real-world access.
Why an accessibility statement matters (for Legal & Compliance)
Transparency: sets expectations and signals good-faith effort.
Risk reduction: documents standards targeted (e.g., WCAG 2.2 AA), scope, and remediation plans.
Process clarity: shows how users can report barriers and how you’ll respond.
Procurement-ready: helps buyers and partners evaluate accessibility posture.
Change control: aligns Marketing, Product, IT, and Legal on a living document.
What to include (key components)
Scope – what properties/products the statement covers.
Standards – the benchmark you aim for (e.g., WCAG 2.2 AA).
Conformance status – current level (full/partial) and known gaps.
Measures & governance – testing, audits, CI/CD checks, training.
Assistive features – on-site tooling and user controls (e.g., Adjustable).
Feedback & contact – how users report issues; response time SLA.
Compatibility – supported browsers/devices/assistive tech.
Limitations – third-party content, legacy docs, embedded widgets.
Enforcement & complaints – optional: regulator/ombudsman routes (by region).
Date & maintenance – last updated; review cadence.
Short template (copy/paste and fill in)
Comprehensive template (with legal-friendly detail)
How to customise (and keep it accurate)
Be precise: list the exact properties, known gaps, and due dates.
Name owners: Legal/Compliance and a Product/Engineering lead.
Point to help: central accessibility@ inbox; add a short SLA.
Reflect reality: don’t claim full conformance if you’re mid-remediation—explain the plan and timeline.
Keep current: update after major releases, audits, or policy changes.
Placement & linking
Link “Accessibility” in the footer site-wide.
Cross-link from Help, Legal, and Procurement pages.
On product pages and docs, reference the statement and your contact path.
Optional: add a short “Roadmap” section
“Q1: remediate PDFs; Q2: replace legacy carousel; Q3: add CI rules for new components.”
This shows active improvement and helps buyers justify investment.
Copy-paste checklist (Markdown)
How Adjustable supports your statement
When you document assistive features, Adjustable adds tangible user benefits that Legal & Compliance care about:
Text to Speech and Translation expand comprehension and reach.
Profiles and Text/Page Options reduce task friction on complex pages.
Reading Ruler, Cursor/Screen Mask, Dictionary improve focus and understanding of dense content.
Light/Dark/Colour modes address visual comfort and contrast preferences.
These controls don’t replace structural compliance, but they demonstrate proactive inclusion while you iterate.
FAQs
Is an accessibility statement legally required?
Requirements vary by jurisdiction. Regardless, a clear statement plus ongoing improvements reduces risk and aids procurement.
Can we claim full WCAG 2.2 AA if only most pages pass?
Avoid overstatement. If some areas are not yet conformant, state partial conformance and provide a remediation plan.
Should we include third-party tools and content?
Yes. Call out third-party dependencies, known limitations, and how users can get alternatives or assistance.
How often should we update the statement?
At least quarterly or after major releases/audits—treat it as a living document.
Next steps
Copy a template above, fill in scope, owners, and SLA, and publish today.
Add a footer link to the statement site-wide.
Schedule a quarterly review and align it with your accessibility roadmap.
Document Adjustable as part of your assistive features and user support.
Share:
