Accessibility statement for small business websites: what to include and why it matters

# Accessibility statement for small business websites: what to include and why it matters

A lot of small businesses are working on accessibility right now, but many still skip one simple page that helps users and reduces friction at the same time: the accessibility statement.

That is a mistake.

An accessibility statement is not a legal shield that magically solves compliance problems. It is also not empty corporate copy you publish because a checklist told you to. Done properly, it is a practical page that explains what you are doing, where the site still falls short, and how someone can get help if they run into a barrier.

If your website matters to sales, enquiries, bookings, recruitment, or customer support, that page deserves more attention than it usually gets.

This guide covers what an accessibility statement should include, how to write one without sounding robotic, and why it matters for small business websites in 2026.

At its simplest, an accessibility statement tells visitors three things:

That sounds basic, but it solves a real problem.

Most visitors do not arrive on a website thinking in terms like WCAG 2.2, conformance levels, or remediation roadmaps. They just want to complete a task. Book a table. Buy a product. Download a guide. Fill in a form. If something gets in the way, they need a fast answer.

A clear accessibility statement gives them one.

It also signals that accessibility is being treated as an ongoing part of website quality, not an afterthought.

There are four good reasons to add an accessibility statement to your site.

If someone struggles with a menu, form, checkout, PDF, or booking widget, the statement gives them a route to support. That matters more than most businesses realise.

Accessibility failures rarely show up in analytics as neatly as a broken button. They often show up as abandonment, confusion, repeat attempts, or a customer quietly giving up.

A statement cannot fix the underlying issue, but it can stop the experience from turning into a dead end.

People are used to polished claims on websites. They are less used to straightforward honesty.

A good accessibility statement says, in plain language, "Here is what we have done, here is what still needs work, and here is how to reach us if something blocks you."

That kind of clarity builds credibility. Especially for service businesses, charities, healthcare providers, education brands, local businesses, and any organisation that depends on trust.

If you are reviewing your site against WCAG 2.2, preparing for European Accessibility Act expectations, or improving internal processes, the statement becomes a useful public record.

It forces discipline.

You have to define scope, name known issues, assign a contact route, and keep the page current. That is healthy. It prevents accessibility from becoming a vague internal promise that never turns into operational work.

This is the underrated part.

Once you publish an accessibility statement, you have created a page that needs ownership. Someone has to update it when the website changes, when an audit happens, when a third-party tool is replaced, or when new issues are resolved.

That makes accessibility more likely to stay alive after launch.

There is no need to overcomplicate this. Most small business accessibility statements should include the following sections.

Start with a plain-English summary of your intent.

For example:

"We want our website to be usable for as many people as possible. We are working to improve accessibility across our site and aim to meet WCAG 2.2 Level AA where reasonably possible."

That is enough. You do not need grand claims or legal theatre.

Avoid lines that imply everything is perfect unless you are absolutely sure it is. Most sites are not perfect, and overclaiming creates risk you do not need.

Be specific about the benchmark.

In many cases, that will be WCAG 2.2 Level AA. If you are following another internal standard or working through staged improvements, say so clearly.

This helps users, partners, and procurement teams understand how you are measuring progress.

Explain which parts of the digital experience the statement covers.

That might include:

If some systems are third-party tools, mention that too. Many accessibility problems live inside booking systems, chat widgets, maps, embedded forms, or ecommerce apps. Pretending they are outside your responsibility does not help users.

A better approach is to say what is included, what is external, and what alternatives exist if the third-party experience causes difficulty.

This is the section businesses often avoid, but it is the one that makes the statement useful.

If you know some PDFs are not fully accessible, say so. If a legacy booking tool has keyboard navigation issues, say so. If some older videos do not yet have captions, say so.

Keep it factual.

For each limitation, include:

That is much better than hiding the problem and hoping nobody notices.

Make it easy for someone to reach you.

Include a specific email address or contact route and explain what kind of help a visitor can request. If relevant, include phone support and your expected response time.

For example:

This section should feel practical, not ceremonial.

Add a "last reviewed" date and keep it current.

An accessibility statement with no date looks abandoned. One that has not been updated in two years suggests the underlying work probably has not been maintained either.

If you want a clean format, use this:

That is enough for most small business websites.

The best accessibility statements sound clear and human. The worst read like someone stitched them together from policy fragments.

If a customer cannot understand the page, it is failing its own purpose.

This one is risky.

Unless you have audited the site properly, tested key journeys, and reviewed third-party components, do not claim full compliance. It is safer and more honest to describe progress and limitations accurately.

Businesses often say the website is accessible while the booking flow, payment step, or embedded form is where the real friction lives.

Users do not care which vendor caused the issue. They experience it as part of your website.

A statement is not a one-and-done page. Every redesign, platform migration, plugin change, content upload, or new PDF library can affect accessibility.

If the site evolves, the statement should too.

Usually the footer is the right home.

That keeps it consistently available across the site and makes it easy to find. If accessibility is especially relevant to your sector, such as education, government-adjacent services, healthcare, charities, or ecommerce, it may also deserve links from help pages or customer support sections.

The important thing is not fancy placement. It is discoverability.

Accessibility conversations often get pushed into a compliance corner. That misses the bigger point.

A more accessible website is usually a clearer website. Better structure, better contrast, better focus states, simpler forms, clearer error handling, better captions, more usable navigation. Those changes help people with disabilities, but they also help everyone else.

The accessibility statement supports that work because it turns accessibility into a visible operational standard.

For small businesses, that can mean:

That is not a side benefit. It is website quality doing real business work.

If your business already has accessibility improvements underway, publish the statement now and update it as the work progresses.

If you have not started, do not wait for a perfect audit before creating the page. Start with an honest version, fix the biggest friction points, and improve both together.

A small business website does not need to sound like a regulator to handle accessibility well. It needs clarity, ownership, and a way for people to get help when something breaks.

That is what a good accessibility statement does.

And in 2026, it should be standard.