Website Accessibility Basics Every Small Business Should Know

Picture someone trying to book an appointment on your site using only a keyboard, or with a screen reader reading the page aloud, or on a phone in bright sunlight with poor eyesight. Can they do it? Website accessibility is about making sure the answer is yes. It’s often treated as a compliance chore for large organisations, but most of the work is basic good practice that any small business site can follow, and much of it costs nothing if it’s done while the site is being built.

What website accessibility means in practice

An accessible website can be used by people with a wide range of abilities: people who are blind or have low vision, people who are deaf or hard of hearing, people with motor impairments who can’t use a mouse, and people with cognitive differences who benefit from clear structure and plain language. It also helps a much larger group who don’t think of themselves as disabled at all: older visitors, people with a broken wrist, someone on a slow connection, or anyone reading on a small screen outdoors.

The common reference point is the Web Content Accessibility Guidelines (WCAG), published by the W3C. The current version is WCAG 2.2, and most legal and contractual requirements point to level AA. You don’t need to read the full standard to make real progress; the items below cover the issues I see most often on small business sites.

The legal side, briefly

I’m not a lawyer, so please treat this as orientation rather than advice. In the USA, businesses have faced lawsuits over inaccessible websites under the Americans with Disabilities Act, and small businesses are not immune. In the UK, the Equality Act 2010 requires service providers to make reasonable adjustments, which can extend to websites. In Canada, Ontario’s AODA sets web accessibility requirements for many organisations, and in Australia the Disability Discrimination Act applies to goods and services, including online ones. Requirements differ by size, sector and location, so check what applies to you. The practical takeaway is the same everywhere: aiming for WCAG 2.2 AA is a sensible, defensible target.

Ten accessibility basics to check on your site

1. Text alternatives for images

Every meaningful image needs alt text describing what it shows or does. A photo of your team might be “Our five technicians standing beside the service van”. A logo that links to the homepage should say the company name. Purely decorative images should have empty alt text so screen readers skip them.

2. Enough colour contrast

Light grey text on a white background looks elegant in a design mock-up and is hard to read for many people. WCAG AA asks for a contrast ratio of at least 4.5:1 for normal text. Free contrast checkers will tell you in seconds whether your colours pass.

3. Don’t rely on colour alone

If a form error is shown only by turning a field red, someone with colour blindness may miss it. Add a text message too, such as “Please enter a valid email address”.

4. Full keyboard access

Try navigating your site using only the Tab, Shift+Tab and Enter keys. Can you reach every link, open the menu, fill in the form and submit it? Can you see where you are on the page? If the focus outline has been removed for style reasons, keyboard users are lost.

5. Proper heading structure

Headings should follow a logical order and describe the content beneath them. Screen reader users often jump between headings to scan a page, the way sighted visitors skim. Choosing a heading level because of how big it looks, rather than where it sits in the outline, breaks that.

6. Descriptive link text

“Click here” and “read more” mean nothing out of context. Link text like “view our pricing for commercial cleaning” tells everyone, including screen reader users listing all the links on a page, where it leads.

7. Labelled form fields

Every field needs a visible label that stays in place. Placeholder text inside the box disappears as soon as someone starts typing, which is confusing for many users and isn’t announced reliably by all assistive technology.

8. Captions and transcripts

Videos with speech need captions. Auto-generated captions are a start, but check them; they often get names and technical terms wrong. Audio-only content such as podcasts benefits from a transcript.

9. Readable, resizable text

Visitors should be able to zoom to 200% without content being cut off or overlapping. Responsive layouts help a great deal here, which is one more reason to get mobile-friendly website design right.

10. No surprises

Avoid auto-playing audio, carousels that rotate too fast to read, and pop-ups that trap keyboard focus. If something moves for more than a few seconds, give people a way to pause it.

A word about accessibility overlays

You may see plugins or services promising to make your site compliant with one line of code, usually by adding a toolbar icon. Be cautious. These tools can’t fix underlying problems like missing labels, poor heading structure or inaccessible custom components, and many disabled users and accessibility specialists report that they get in the way. They are not a substitute for fixing the site itself.

How to improve website accessibility on a budget

If you’re building a new site, include accessibility in the website design brief from the start. Choosing accessible colours, sensible headings and proper form markup at the design stage costs very little extra. Retrofitting the same things later takes longer.

For an existing site, start with a free automated checker to catch obvious issues such as missing alt text and low contrast, then do the manual keyboard test described above. Automated tools only catch a portion of problems, so the manual check matters. Fix the pages that matter most first: home, main service pages, contact form and checkout.

Content matters as much as code. Short sentences, clear headings and specific calls to action help everyone, which overlaps heavily with the advice in my post on website content that converts.

Some fixes do need a developer: rebuilding a menu so it works with a keyboard, repairing a theme that strips focus outlines, or fixing a form plugin that outputs unlabelled fields. These are typical tasks in website development work and are usually manageable on a small site.

Frequently Asked Questions

Is my WordPress theme accessible by default?

Not necessarily. Some themes are tagged “accessibility ready” in the WordPress directory, which is a good sign, but page builders, plugins and custom content added later can introduce problems. Test the finished site, not just the theme.

How much does an accessibility review cost?

It depends on site size and how deep the review goes. A basic check of a handful of key pages is a modest job; a full audit of a large site with an online shop is considerably more. Ask for a list of issues with priorities, not just a score.

Does accessibility help SEO?

Indirectly. Alt text, clear headings, descriptive links and captions all help search engines understand your content too. The main reason to do it, though, is so more people can use your site.

Need help?

If you’d like a second pair of eyes on your site’s accessibility, or you’re planning a new site and want it built properly from the start, I’m happy to help. You can browse the services I offer and then contact me. I’ll reply within 24–48 hours.

Services That Can Help

Estimate Project