Yes, website accessibility matters for your business, both legally and commercially, and you can start checking today. Aim for WCAG 2.2 at level AA as your practical target. Right now, try tabbing through your homepage and contact page using only your keyboard, and run a quick colour contrast check, or ask a specialist for a short review.
TL;DR:
- Sample your homepage, contact page, and highest risk booking, enquiry, or payment page; keyboard tests reveal failures automated scanners often miss.
- Fix broken forms and invisible keyboard focus first, then address contrast and heading order; reserve larger structural changes for a later stage.
- Keep an accessibility statement with your target standard, unresolved issues, feedback contact, and next review date, plus a dated log of completed and pending fixes.
- Invite disabled people to test a real task, such as booking or sending an enquiry, because automated checks can miss confusing keyboard navigation.
Table of Contents
- What the Equality Act and WCAG mean for your website
- Why fixing accessibility pays off commercially
- Common accessibility barriers and how to fix each one
- A low-cost accessibility audit you can run this week
- Your priority checklist for fixing issues in order
- Keeping accessibility current after the first fix
- How a pay-monthly website keeps accessibility maintained
- How accessible design fits your branding and user experience
- Tools and resources that suit a small business budget
- Budgeting for accessibility without a big project
- Testing with real disabled users for honest feedback
- A practical perspective on getting started
- Get ongoing accessibility support built into your website plan
- FAQ
- Sources
What the Equality Act and WCAG mean for your website
Under the Equality Act 2010, you have an anticipatory duty to make reasonable adjustments so disabled customers are not substantially disadvantaged when using your services. This duty covers the information and services you provide, which includes your website, and it applies before someone asks you for help, not just after.
WCAG 2.2 is the international technical standard most businesses use to judge whether their site meets a reasonable level of access. It sets out testable success criteria across three levels, with level AA typically considered the sensible target for most organisations.
Keeping a record matters almost as much as the fixes themselves:
- Publish a short accessibility statement on your site.
- Note known issues and the date you reviewed them.
- Keep a simple log of fixes completed and still outstanding.
That paper trail shows you are acting proactively, which counts for a great deal if a complaint ever arrives.
Why fixing accessibility pays off commercially
Accessible design widens your potential customer base and reduces your exposure to complaints. The Business Disability Forum frames this plainly: accessible design improves usability for everyone, not only disabled visitors, and supports wider business inclusion goals. Clear navigation, readable text and predictable layouts help a tired parent scrolling on a phone just as much as they help someone using a screen reader.
Most accessibility fixes double as usability fixes. Tidying your heading structure makes a page easier to scan for every visitor. Improving colour contrast helps anyone reading in bright sunlight. Adding proper form labels reduces abandoned checkouts, not just accessibility complaints.
Three business reasons to act now:
- You reach customers who currently bounce off a confusing or unusable page.
- You reduce the chance of a discrimination complaint reaching a tribunal.
- You build a site that generally performs better in search and converts more visitors.
Pro Tip: Treat your next planned website update as the moment to fix one accessibility issue, rather than waiting for a dedicated project with its own budget line.
Common accessibility barriers and how to fix each one
Most small business sites share the same handful of problems, and each has a straightforward fix.
- Missing or poor alt text. Describe what the image shows and why it matters, not just “photo1.jpg”; decorative images can have empty alt text so screen readers skip them.
- Inconsistent heading structure. Use one H1 per page, then H2 and H3 in order, so the page reads as a logical outline rather than a jumble of bold text.
- Forms without clear labels. Attach a visible label to every field, and write error messages that say what went wrong and how to fix it, not just “invalid entry”.
- Poor colour contrast and missing focus indicators. Check text against its background with a free contrast checker, and never remove the outline that shows which button or link is currently selected by keyboard.
- Multimedia without captions or transcripts. Add captions to video and a short transcript to audio content; both also help visitors watching with the sound off.
None of these require rebuilding your site. They are edits to existing content and a handful of style changes.
A low-cost accessibility audit you can run this week
You do not need a paid specialist to find your biggest problems. Gov recommends a basic check when a full audit is not affordable, built around sampling a handful of key pages rather than testing everything.
- Pick your sample. Test your homepage, contact page, and whichever page takes bookings, enquiries or payments, since these carry the most risk if something breaks.
- Run a keyboard walk-through. Use Tab and Shift+Tab to move forward and back, Enter to activate links and buttons, and Escape to close menus, watching whether focus moves in a sensible order and never disappears.
- Use free tools for the rest. A contrast checker browser extension flags failing text within seconds, and automated scanners catch missing alt text and obvious structural errors.
- Triage what you find. Sort issues into fix this week (broken forms, invisible focus), fix this month (contrast, headings) and plan for later (bigger structural changes).
A keyboard walk-through using Tab, Shift+Tab, Enter and Escape is the fastest manual test available, and it reveals operability problems that automated scanning tools often miss entirely.
Your priority checklist for fixing issues in order
Work through fixes in the order they affect the most visitors, starting with content and structure before moving to controls and finally to multimedia.
Content and structure first:
- Fix heading order so each page reads as a logical outline.
- Write alt text for every meaningful image.
- Check that body text meets minimum contrast ratios against its background.
Controls and forms next:
- Label every form field clearly and attach helpful error messages.
- Confirm every link and button works with keyboard alone.
- Check that menus and pop-ups can be closed with the Escape key.
Multimedia and widgets last:
- Add captions to video content and transcripts to audio.
- Review any chat widgets, sliders or carousels for keyboard operability.
Most content management systems make these changes straightforward. Alt text fields sit alongside the image upload tool, heading levels are usually a dropdown in the text editor, and captions can often be uploaded as a separate file alongside your video. Our homepage accessibility checklist walks through the most common fixes for a typical small business site.
When a fix needs a developer, such as rebuilding a broken form or fixing a widget that traps keyboard focus, ask for a clear scope of work, confirmation that the fix will be tested against specific WCAG success criteria, and a written remediation plan you can keep alongside your accessibility statement.
Pro Tip: Fix the content issues yourself this month, then brief a developer only for the structural problems that need code changes.
Keeping accessibility current after the first fix
Accessibility is not a project with an end date, it is a habit you build into how you publish content. Set a monitoring rhythm, a quick spot check every month or quarter, and build an accessibility glance into your normal content workflow whenever you add a new page or blog post.
Your accessibility statement should cover a short, honest set of points:
- The standard you are aiming for, typically WCAG 2.2 AA.
- Any known issues you have not fixed yet.
- A contact method for someone who hits a barrier.
- A rough timeline for your next review.
| Statement element | What to include |
|---|---|
| Standard aimed for | WCAG 2.2 AA |
| Known issues | Honest, current list |
| Contact details | Email or form for feedback |
| Review plan | Next check date |
Keeping this updated gives you something concrete to point to if a complaint ever lands on your desk, showing you have acted proactively rather than ignored the issue.
How a pay-monthly website keeps accessibility maintained
Most small businesses do not have a developer on staff, so the practical question is who checks accessibility every time the site changes. We built our pay-monthly plans around exactly that gap: a single point of contact, ongoing edits included each month, and routine attention rather than a one-off fix that goes stale within a year.
Our pay-monthly website plans include free domain and SSL setup, personal support, and changes made for you each month, so a new heading structure or a missing alt text tag gets corrected as part of your existing plan rather than a separate invoice. Our hosting and maintenance options extend the same ongoing attention to sites we did not originally build.
If you want a second opinion on where your site currently stands, request a quick review and we will talk you through what we find.
How accessible design fits your branding and user experience
Accessible design and strong branding are not in tension, they support each other. A clear visual hierarchy, consistent colour use and readable type are exactly what good branding already asks for, and they are also what accessibility guidance recommends.
Where branding and accessibility can clash is contrast. A pale grey logo colour might look elegant, but body text in that same shade often fails contrast checks against a white background. The fix is usually to keep your brand colour for accents, logos and buttons, and use a darker, more readable shade for body copy.
The same applies to decorative fonts. A stylised heading font can stay for your logo and section titles, while body text uses a plainer, highly legible typeface. This is standard practice for most professional sites already, so accessibility rarely demands a visual overhaul, more often it just tightens choices you have already made.
Good user experience and accessibility overlap almost completely: clear calls to action, obvious navigation, and forms that tell you exactly what went wrong when something is filled in incorrectly. Building with accessibility in mind from the outset tends to produce a site that feels more polished for every visitor, not a compromised version of your original design.
Tools and resources that suit a small business budget
You do not need enterprise software to check or fix most accessibility issues. A free browser extension that overlays contrast ratios directly on your page takes seconds to install and gives an instant pass or fail reading for your text.
Browser developer tools, built into Chrome, Firefox and Edge, include accessibility panels that flag missing labels, poor heading order and contrast failures without installing anything extra. These are free and already on your computer.
For the legal and practical background, gov.uk’s guidance on publishing an accessibility statement explains what a basic review should look like and how to word your own statement. The Business Disability Forum publishes wider guidance on inclusive practice that goes beyond the website itself.
One caution worth flagging: automated “accessibility widget” plugins that promise to fix everything with one line of code are not a substitute for manual testing. They catch some surface issues but cannot repair a broken form or a trapped keyboard focus, and relying on one alone can create a false sense of having dealt with the problem. Combine any automated tool with the manual keyboard walk-through covered earlier, and you will catch far more.
Budgeting for accessibility without a big project
Accessibility work scales down well because most of the highest-impact fixes cost nothing beyond time. Rewriting alt text, correcting heading order and adjusting a colour value in your site’s style sheet are edits, not rebuilds, and many content management systems let you make them yourself in an afternoon.
Where a cost does appear, it is usually for ongoing maintenance rather than a single big spend. Keeping a site accessible as you add new pages, images and offers is a recurring task, which is why a monthly plan tends to suit small businesses better than a one-off audit that goes out of date within months. Our existing website adhoc work plans start at £29.99 a month for an hour of changes, which covers routine fixes like these without a separate invoice each time.
If budgeting support beyond your website is on your mind too, it is worth getting your wider business finances in order at the same time, since accessibility fixes, hosting and other recurring costs are easier to plan for once your bookkeeping is tidy; guidance on when a growing business needs accounting help is a useful starting point for working out what else might need a second pair of hands.
Testing with real disabled users for honest feedback
Automated tools and manual checklists catch most structural problems, but they cannot tell you how a page actually feels to use. Involving a small number of disabled users in testing, even informally, often surfaces issues that no checklist predicts.
A practical way to start is to ask one or two people who use a screen reader, screen magnifier or keyboard-only navigation to try completing a specific task on your site, such as booking an appointment or sending an enquiry, and talk you through where they got stuck. You are not looking for a formal research study, just honest, specific feedback on real friction points.
W3C guidance on WCAG recommends exactly this combination: automated testing plus human evaluation, including people with disabilities wherever practical, because technical compliance and genuine usability are not always the same thing. A page can pass every automated check and still frustrate a real user if, for example, the tab order jumps around unpredictably.
If you do not have contacts to approach directly, local disability charities or community groups are often willing to help in exchange for a small thank-you, and the feedback tends to be more specific and actionable than anything a scanning tool will give you.
A practical perspective on getting started
Accessibility stops feeling daunting once you treat it as a habit rather than a project. Fixing one heading structure this week and one set of alt text next week beats shelving the whole thing until you have a free month that never arrives.
Start small, stay consistent, and ask for help when a fix needs code rather than content. Our blog carries further practical guides if you want to keep going after this one.
— Mark Jones
Get ongoing accessibility support built into your website plan
Accessibility works best as part of how your site is maintained, not as a one-off task you tick off and forget. We built our pay-monthly plans around that idea: no upfront cost, a free domain and SSL included, and changes made for you every month rather than billed separately each time something needs fixing.
That ongoing support matters because your content keeps changing. New pages, new images and new offers all need the same attention the rest of your site got, which is exactly what a managed plan is for:
- Monthly edits included, so a missing alt text tag gets fixed as part of your plan.
- A single point of contact who already knows your site.
- Hosting and maintenance plans that cover sites we did not originally build.
If you want a quick view of where your site stands, get in touch through our pay-monthly website plans page and we will talk you through what we find and what it would take to fix.
FAQ
Is website accessibility a legal requirement in the UK?
Yes, service providers have an anticipatory duty under the Equality Act 2010 to make reasonable adjustments so disabled customers are not substantially disadvantaged. This applies to the information and services you provide, which includes your website, and the duty exists before anyone complains, not only after.
Can a business face legal action over an inaccessible website?
A disabled customer who is substantially disadvantaged by an inaccessible website may have grounds to raise a complaint under the reasonable adjustments duty in the Equality Act 2010. Keeping a documented accessibility statement and a record of fixes made is a practical way to show you have acted proactively rather than ignored the issue.
What accessibility features should a website have?
A reasonably accessible website follows WCAG 2.2 at level AA, covering clear heading structure, useful alt text on images, labelled forms with helpful error messages, sufficient colour contrast, visible keyboard focus indicators, and captions or transcripts for multimedia. These are the fixes most small sites need first.
How much does it cost a small business to improve accessibility?
Many of the highest-impact fixes, such as correcting alt text, heading order and colour contrast, cost nothing beyond time spent editing existing content. Where ongoing cost does appear, it is usually for routine maintenance as new content is added, which is why a monthly support plan often suits small businesses better than a single large audit.
Sources
- Equality Act 2010 (notes and provisions)
- Gov
- Web Content Accessibility Guidelines (WCAG) 2.2 — W3C
- Business case for disability inclusion — Business Disability Forum
