Website accessibility fixes: real code, never overlay widgets.

In one sentence: we find the parts of your website that are hard to see, hear, tap or understand, fix them in the site itself so they stay fixed, and keep re-checking them, without ever claiming your site is "ADA compliant".

What does "accessible" mean for a small business website?

It means anyone who wants to book, call or buy from you can do it, whatever their body or device. That's a lot of your customers. The US Centers for Disease Control and Prevention reported that more than 1 in 4 adults in the United States, over 70 million people, had a disability in 2022 (CDC, 2024). Add the people with tired eyes, a cracked phone screen, a broken wrist or bright sunlight on their screen, and "accessibility" stops sounding like a niche.

In practice, it comes down to everyday things. Can someone read your prices if the text is pale grey? Can a person who uses a keyboard, not a mouse, reach your "Book now" button? Does a screen reader say "image, image, image" or "Our treatment room, with a view of the garden"?

What is WCAG, in simple words?

WCAG stands for the Web Content Accessibility Guidelines. It's the standard almost everyone uses to judge whether a website is accessible, written by the W3C, the group that sets many of the web's rules. The current version is WCAG 2.2, published in October 2023 (W3C, 2023). It rests on four simple ideas. Your site should be:

• Perceivable. People can see or hear the content: readable text, described images, captions on videos.
• Operable. People can use it: everything works with a keyboard, buttons are big enough to tap, nothing flashes or moves too fast.
• Understandable. Clear words, menus that behave the same on every page, form errors that explain what to fix.
• Robust. The code is built properly, so screen readers and other tools can make sense of it.

Each rule has a level: A (the basics), AA (the level most laws and guides point to) and AAA (the strictest, rarely needed for a whole site). We work towards AA, starting with the problems that stop people booking.

What do you actually fix?

Real changes to your site's code and content. These are the problems we find most often on small business sites:

• Low-contrast text. Pale text on pale backgrounds, especially on buttons and in footers. We adjust colours while keeping your look.
• Images with no description. We write short "alt text" for photos that matter, and mark decorative ones so screen readers skip them.
• Form fields with no labels. A box that only says "Name" in faint grey until you click is hard for many people. Every field gets a proper label and helpful error messages.
• Buttons and links with no name. An icon-only phone or menu button reads as just "button". We give it a name, like "Call the clinic".
• Keyboard traps and hidden focus. Menus and pop-ups that can't be used or closed without a mouse, and no visible outline showing where you are.
• Tiny tap targets. WCAG 2.2 added a minimum size for things you tap. We make your call and booking buttons easy to hit.
• Messy headings and page language. Headings in order, so people can jump around the page, and the page language set so it's read out in the right accent.

How is it set up, and what do you need from me?

Very little, apart from a few decisions. We confirm timing in your quote, because it depends on the size of your site and what we find.

1. We agree the pages that matter most. Usually your home page, main services, prices, contact and booking.
2. We test and send you the list. Each problem with a screenshot, who it affects, and how we'll fix it.
3. We fix, on a copy first. Then we check your design and bookings still work, and put the changes live.
4. We re-test and write your statement. A short, honest page saying what we checked, when, and how people can tell you about a problem.

What we need from you

• Access to your website, or the OK to use the access your plan already gives us.
• Your brand colours, and whether you're happy for us to darken a shade slightly so text is readable.
• Descriptions only you know, like who is in a team photo or what a treatment room is for. We draft, you check.
• Who makes your booking or payment tool, so we can check its own accessibility settings and what it supports.
• An email address for accessibility feedback, to put in your statement.

How does this compare with doing it yourself?

You can make a real start yourself. Free browser checkers will flag contrast and missing labels, and many fixes are simple once you know where to look. The hard parts are the problems tools miss, and keeping it right over time.