Website & Development
Website accessibility: a step-by-step plan for your existing site
Copy for AI
Website accessibility on an existing site rarely needs a rebuild.
It needs a series of targeted fixes on the pages you already have.
The verdict: map where visitors get stuck, remove the biggest barriers first, test with real people, and record the result in an honest accessibility statement.
Below: a practical step-by-step plan for a live site, plus how to write a statement that actually holds up.
What does website accessibility really mean?
It means your site is usable by as many people as possible, including people with a disability.
Think of visitors who see poorly, don’t use a mouse or browse with a screen reader.
WCAG is the reference framework
The international reference is WCAG (Web Content Accessibility Guidelines) from the W3C. Our wiki entry on WCAG gives the short version.
It’s built around four principles:
- Perceivable: people can see or hear the content
- Operable: people can use every control
- Understandable: content and controls make sense
- Robust: assistive software can read the code
In practice, level AA is often the target. It’s the middle one of three conformance levels.
The W3C offers a clear introduction to web accessibility with examples per type of disability.
Accessibility is good UX for everyone
Accessibility is almost always simply good UX for everyone.
Better contrast also helps the visitor standing in bright sunlight. Clear button text also helps someone in a hurry.
So you improve the experience broadly, not only for a niche group. More in our UX best practices.
It directly affects your conversion
Excluded visitors never become customers.
Someone who can’t fill in your form doesn’t fill it in.
Does your company have to comply?
For many B2B organisations: probably in part, but have it checked legally.
The European Accessibility Act applies since June 2025
Since 28 June 2025 the European Accessibility Act applies (EAA, directive (EU) 2019/882).
This European law requires a broad group of consumer-facing products and services to meet accessibility standards. Examples:
- webshops
- banking services
- e-books
- certain telecom services
The technical bar is set by the EN 301 549 standard, which closely follows WCAG 2.1 level AA.
Micro-enterprises: exempt in the directive, delayed in Belgium
Not every organisation falls under the same obligations.
Micro-enterprises that provide services are exempt under the directive. That means fewer than 10 employees and at most 2 million euros turnover or balance sheet total.
Watch out: Belgium gives them no exemption. They get a delay until 28 June 2030.
Have the scope checked
The exact scope depends on what you offer and to whom.
Who is and isn’t covered is explained in our article on the European Accessibility Act. How it affects your forms and lead flow is in the EAA and lead generation.
We don’t give legal advice here. What is clear: accessibility is shifting from “nice to have” to “expected”, and the steps below move you in the right direction either way.
Rule of thumb: have a specialist check whether and how the EAA applies to your situation.
How common are accessibility errors?
Very common: almost every homepage has them.
WebAIM tests the homepages of the top 1,000,000 websites every year. In its February 2026 run, 95.9% of homepages had detected WCAG 2 failures, with an average of 56.1 errors per page (WebAIM Million).
The same six error types keep coming back:
Most of those six are exactly the quick wins in step 2 below.
So the odds are high your site has them too. The good news: they’re also the easiest to fix.
Which steps do you follow to make an existing site accessible?
Four steps, from quick wins to deeper fixes; you rarely need to rebuild.
Most errors are targeted adjustments to existing pages. Work in this order and you’ll book visible gains quickly without getting lost in details.
Here’s the route:
Step 1: map the problems
Start with a quick check of your own. It makes the pain points obvious immediately.
Our WCAG checker gives you a first list of automatically detectable errors within a minute. Run it on your homepage, a product page and a form.
Here’s what a first scan looks like:
Then do two manual checks:
- Keyboard only: navigate your whole site with tab, enter and the space bar. Can you reach every button and form, with a visible focus outline?
- Low brightness: turn your screen brightness down to spot contrast problems.
Add an automated scan to this. A free tool such as the WebAIM Contrast Checker checks colour contrast. A browser-based audit like the one in Google Lighthouse gives a first list of issues.
Watch out: automated tools catch only part of the problems, so the manual check stays necessary.
Step 2: tackle the low-hanging fruit
A large part of the gain sits in a handful of basic errors that recur on almost every site.
These are the classics, and they’re usually quick to solve:
- Alt text: give informative images a descriptive alt text and decorative images an empty one (
alt=""), so a screen reader skips them neatly. - Colour contrast: normal text needs a contrast ratio of at least 4.5 to 1, large text at least 3 to 1. Be especially critical of buttons and forms.
- Keyboard operation: make everything clickable reachable with tab, with a visible focus, and add a “skip to content” link at the top of every page.
- Form labels: link every field to a visible
<label>. Placeholder text doesn’t count, because screen readers often skip it.
Those contrast ratios come straight from WCAG success criterion 1.4.3. “Large” means at least 18 point, or 14 point bold (W3C, Understanding Contrast Minimum).
For example, say your buttons use light grey text on white. That pair almost certainly fails 4.5 to 1, and every visitor squints at it.
Alt text has a second job today: AI systems read it too. See our guide to alt text for multimodal AI and the wiki entry on alt text.
A deeper overview of these pitfalls is in our guide to the most common web accessibility mistakes.
Get your forms right first
Your forms are your conversion engine, so it pays to get those flawless first.
Feel free to combine this step with your work on accessible, conversion-focused forms.
Step 3: solve the structural issues
After the quick wins come the slightly deeper points:
- Headings: one
h1, then tidyh2andh3levels, so a screen reader can scan the page like a table of contents. - Link texts: describe where you end up instead of “click here”.
- Tables: keep them simple, with correct headers.
- Dynamic components: menus, pop-ups and notifications must work with keyboard and screen reader.
Clean, meaningful code makes all of this easier. Our guide to semantic HTML explains why.
This is where custom work and technical knowledge make the difference. It pays to involve a developer.
Step 4: test with real tools and real people
Check your fixes again with your audit tools, but don’t lean on them entirely.
The most valuable test is letting someone use your site with a screen reader or only a keyboard. Within minutes you see what a scan will never find.
Keep an eye on your technical foundation
Slow or unstable pages are a barrier in themselves.
Layout that jumps while someone tries to click is a good example. Search Console flags it in the Core Web Vitals report:
Our own Search Console, Core Web Vitals on mobile, October 2026. Layout shift keeps 349 mobile URLs out of the green.
A shifting button is annoying for everyone. For someone with a tremor or a screen magnifier, it can block the task.
Work on Core Web Vitals and accessibility reinforce each other.
How do you write a valid accessibility statement?
Honestly: describe what meets the standard, what doesn’t yet, and what you’re doing about it.
A valid accessibility statement is a public document. It isn’t a marketing text and not a tick box.
Its strength lies precisely in the honesty. You may name open items, as long as you attach a plan and a deadline.
What goes in the statement
A usable statement generally contains these parts:
- The scope: which website or application the statement applies to.
- The compliance status: to what extent the site meets WCAG 2.1 level AA, often expressed as fully, partially or non-compliant.
- The non-accessible parts: which parts don’t comply yet, why, and which alternative you offer in the meantime.
- The test method: whether you did a simplified or thorough review, with a reference to the audit report.
- Date: when the statement was drawn up and last updated.
- Contact details: where visitors can report an accessibility problem, and who follows it up.
Public sector versus private companies
For the Belgian public sector there’s a fixed template that refers to EN 301 549.
For private companies under the EAA the exact form is less strictly described. The Belgian FPS Economy asks you to describe how your service works and how you apply the requirements. You do that in your terms and conditions or an equivalent document, such as an accessibility statement.
The same logic and transparency apply. A full template with example passages is in our guide with website accessibility statement examples.
Where to put it and how often to update
Put the statement in a fixed, findable place, such as your footer.
Link it to your contact page, so reporting stays low-threshold.
Update it at least annually, and immediately whenever something changes.
Watch out: a statement that’s no longer accurate is worse than no statement at all.
How do you build accessibility into your website?
At three levels: in your design, in your CMS and in your publishing process.
A clean-up fixes today’s errors. If you want new pages to be accessible by default, you lock it in:
| Layer | What you lock in | What it prevents |
|---|---|---|
| Design system | Colour pairs that meet contrast, a fixed focus style, a minimum click size, font sizes in relative units | Campaign colours and new buttons quietly dropping below the standard |
| Components | Menu, accordion, slider, pop-up and form built correctly once and reused everywhere | The same keyboard and screen reader error on hundreds of pages |
| CMS | A required alt field for meaningful images, heading levels as a dropdown, no text in images | Editors publishing errors without knowing it |
| Content | Clear link texts, short sentences, captions on video, accessible PDFs or HTML instead of PDF | Content that is technically correct but still unusable |
| Process | An accessibility check in the definition of “done” for every release and campaign | Regression after every update or plugin |
The biggest gain sits in the components
A website usually consists of a few dozen building blocks.
Build them right once and every page inherits that quality.
Repair page by page and you start over with every new landing page.
How do you keep your site accessible after the first clean-up?
Make it a fixed part of your process instead of a one-off clean-up.
Every new page, campaign or plugin can introduce new barriers. So include the checklist by default with every change.
Three habits keep it in place:
- a check in every release
- a light re-check every quarter or major release
- accessibility built in from the start of any redesign
If you’re considering a larger intervention anyway, build accessibility in from the start rather than afterwards. Read more in our approach to a website redesign.
Ongoing care is part of website maintenance too.
Accessibility is standard in our builds
With us, accessibility is standard in every serious project where we build a website, not an afterthought.
We’re a small, senior team, and we always steer on the same question: does your website deliver more usable pages and more leads?
Accessibility that doesn’t lead to more conversion is half the job. The bigger picture is in our guide to B2B website development.
Frequently asked questions
How long does it take to make an existing website accessible?
That depends on the size and build of your site. The low-hanging fruit (alt text, contrast, labels) is often fixed in a few days. Structural errors in menus, forms or an outdated theme take more time, because they sit in the templates.
Do I have to rebuild my website to make it accessible?
Rarely. Most errors are targeted adjustments to existing templates and content. A rebuild only makes sense if the theme or page builder itself generates inaccessible code you cannot change.
Is an accessibility plugin enough?
No. Plugins and overlays do not change your underlying code and rarely fix structural problems. They can even get in the way of assistive software. Use tools to find errors, and fix them in the code and content.
Which pages should I tackle first?
The pages where visitors take action: your contact or quote form, the most important service or product pages and the navigation. There every barrier directly costs requests or sales.
The short summary
Making your existing website accessible isn’t a rebuild, but a targeted route.
Map the problems, fix the basics first (alt text, contrast, keyboard, form labels), then tackle the structural points, and test with real people.
Record the result in an honest accessibility statement with a date, contact details and a plan for what’s still open. Keep it up to date with every change.
That way you meet the expectations around the EAA. You also turn visitors you’re quietly losing today into customers.
Would you rather not walk that route alone? Our page on WCAG compliance explains how we handle the audit, the fixes and the statement.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.