WCAG & Compliance

Accessibility Statement: Template

Document icon with a tick next to it on a purple background

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: establishes expectations and represents a sincere commitment.
Risk reduction: outlines targeted standards (such as WCAG 2.2 AA), scope, and plans for improvement.
Process clarity: demonstrates how users can report barriers and how responses will be handled.
Procurement-ready: assists buyers and partners in assessing accessibility readiness.
Change control: coordinates Marketing, Product, IT, and Legal on a document that evolves.

What to include (key components)

Scope – the properties/products covered by the statement.
Standards – the benchmark you aspire to achieve (e.g., WCAG 2.2 AA).
Conformance status – current level (complete/partial) and identified gaps.
Measures & governance – testing, audits, CI/CD checks, and training.
Assistive features – on-site tools and user controls (e.g., Adjustable).
Feedback & contact – channels for users to report issues; response time SLA.
Compatibility – supported browsers/devices/assistive technologies.
Limitations – third-party content, legacy documents, embedded widgets.
Enforcement & complaints – optional: routes through regulator/ombudsman (by region).
Date & maintenance – last updated; review schedule.

Short template (copy/paste and fill in)

# Accessibility Statement

[Company] is committed to making [website/app/product] accessible to everyone. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.

## Scope
This statement applies to: [domain(s)/app(s)/properties]. Last updated: [date].

## Measures we take
- Accessibility included in our design and code standards.
- Automated checks in CI/CD and manual keyboard/screen reader tests.
- Periodic expert reviews and remediation sprints.

## Assistive features on our site
We provide the **Adjustable** accessibility toolbar with options such as Text to Speech, Language Translation, Accessibility Profiles, Text Options, Reading Ruler, Cursor Adjustment, Screen Mask, Page Options (page scaling, hide images/animations, highlight links), Dictionary, and Light/Dark/Colour modes.

## Conformance status
We are [fully/partially] conformant with WCAG 2.2 AA. Known areas for improvement:
- [Example: legacy PDFs created before 2024]
- [Example: third-party booking widget focus order]

## Feedback and contact
If you experience difficulty with any content, please contact us:
- Email: [accessibility@company.com]
- Phone: [+44 …]
We aim to respond within [X business days] and provide a fix or alternative within [Y days].

## Compatibility
Our site works with the latest versions of major browsers and assistive technologies. For the best experience, use the most recent browser/OS.

## Limitations
Some third-party content and integrations may be outside our control. We monitor these and work with vendors on improvements.

## Continuous improvement
We review this statement and our accessibility roadmap at least [quarterly]

Comprehensive template (with legal-friendly detail)

# Accessibility Statement for [Company/Product]

**Commitment**  
[Company] is committed to providing a website and digital products that are accessible to the widest possible audience, regardless of technology or ability. Our objective is conformance with **WCAG 2.2 Level AA**.

**Scope**  
This statement covers: [list properties, apps, subdomains]. It does not cover: [explicit exclusions].  
Owner: [Role/Department]. Last updated: [date]. Next review: [date/cadence].

**Standards & Methodology**  
We design and test against WCAG 2.2 AA using:  
- **Automated rules** in CI/CD (titles, landmarks, labels, name/role/value, colour-contrast flags).  
- **Manual validation** (keyboard-only navigation; screen reader smoke tests with NVDA/VoiceOver).  
- **Periodic audits** of components (navigation, dialogs, forms, carousels) and user journeys.  
- **Editor guidance** for headings, link text, alt text, captions/transcripts, and document exports.

**Assistive Features**  
Our site includes the **Adjustable** accessibility toolbar to support diverse needs:  
- **Text to Speech**, **Language Translation**, **Accessibility Profiles**  
- **Text Options** (size/spacing), **Reading Ruler**, **Cursor Adjustment**, **Screen Mask**  
- **Page Options** (page scaling, hide images/animations, highlight links)  
- **Dictionary** lookups; **Light/Dark/Colour modes**; configurable toolbar/widget placement

**Current Conformance Status**  
We are [fully/partially] conformant with WCAG 2.2 AA. Known issues and planned remediation:  
- [Example] Some older PDF downloads are not fully tagged. *Plan:* replace with HTML and provide tagged PDFs by [date].  
- [Example] Focus order within [vendor widget] may be inconsistent. *Plan:* vendor patch planned for [date]; interim keyboard bypass documented.

**Compatibility & Technical Requirements**  
This site is designed to work with modern browsers (Chrome, Safari, Firefox, Edge) and recent mobile OS versions. Assistive tech tested includes [screen readers/browsers]. JavaScript and CSS must be enabled for full functionality.

**Feedback & Formal Complaints**  
We welcome your feedback on accessibility:  
- Email: [accessibility@company.com]  
- Phone: [+44 …]  
- Postal: [address]  
We aim to acknowledge within **[X] business days** and provide a resolution or timeline within **[Y] days**.  
If you are not satisfied with our response, you may escalate to: [local regulator/ombudsman link, if applicable].

**Third-Party Content**  
Our site integrates third-party services (e.g., video players, booking widgets, analytics). We work with vendors to ensure accessibility and provide alternatives where feasible.

**Ongoing Governance**  
Accessibility is part of our product lifecycle and procurement. We train teams, set release gates, and track metrics (issues, time-to-fix). This statement is reviewed **[quarterly]**

How to customize (and keep it accurate)

Be precise: specify the exact properties, known gaps, and deadlines.
Name owners: Legal/Compliance and a Product/Engineering leader.
Point to help: central accessibility@ inbox; include a brief SLA.
Reflect reality: don't claim complete conformance if remediation is ongoing—explain the plan and timeline.
Keep current: update after significant releases, audits, or policy changes.

Placement & linking

Link “Accessibility” in the footer across the entire site.
Cross-link from Help, Legal, and Procurement pages.
On product pages and documents, refer to the statement and your contact path.

Optional: add a short “Roadmap” section

“Q1: remediate PDFs; Q2: replace legacy carousel; Q3: implement CI rules for new components.”
This demonstrates active enhancement and helps buyers justify investment.

Copy-paste checklist (Markdown)

How Adjustable supports your statement

When documenting assistive features, Adjustable provides tangible user benefits that Legal & Compliance value:

Text to Speech and Translation enhance comprehension and outreach.
Profiles and Text/Page Options ease task completion on complex pages.
Reading Ruler, Cursor/Screen Mask, Dictionary improve concentration and understanding of dense content.
Light/Dark/Color modes address visual comfort and contrast preferences.
These controls don’t replace structural compliance, but they demonstrate proactive inclusion as you progress.

Try Adjustable

FAQs

Is an accessibility statement legally required?
Requirements vary by jurisdiction. Regardless, a clear statement plus ongoing improvements reduce risk and support procurement.

Can we claim full WCAG 2.2 AA if only most pages pass?
Avoid exaggeration. If some areas don't yet conform, state partial conformance and outline a remediation plan.

Should we include third-party tools and content?
Yes. Highlight third-party dependencies, known limitations, and how users can find alternatives or support.

How often should we update the statement?
At least quarterly or after major releases/audits—treat it as a dynamic document.

Next steps

Copy the template above, fill in scope, owners, and SLA, and publish today.
Include a footer link to the statement site-wide.
Set up a quarterly review and synchronize it with your accessibility roadmap.
Include Adjustable in your documentation as part of your assistive features and user support.

The Impact of Accessibility for E-Commerce Brands

A stack of pixelated gold coins shimmering against a lavender-colored background

Accessibility ROI: Conversions, Usability & Legal Risk

Email Accessibility: Newsletters Everyone Can Read

The Impact of Accessibility for E-Commerce Brands