Website accessibility for a small business, without the panic or the jargon

What accessibility actually means for a five-page site

Somebody forwarded you an email warning about website lawsuits, and you read it twice trying to work out how much of it applies to you. That reaction makes sense. Nobody wants a letter like that.

A lot of what gets called "accessibility" has nothing to do with a courtroom. It means text a screen reader can announce. A menu a keyboard can reach. A form that names which field is wrong instead of just saying "error." None of that needs a lawyer.

Accessibility is a build discipline before it is a legal question. It means writing pages the way markup was designed to be read: headings that follow a real order, images carrying a description, links whose text says where they go. It applies the same way to a five-page site as it does to a five-hundred-page one.

The sharpest example is the contact form. That's where a small mistake costs the most. Get the labels or the error messages wrong there and you're not just failing a checklist. You're losing the enquiry the form was supposed to capture. That single page is worth understanding on its own.

The customers a careless build quietly turns away

A site that fails at accessibility does not announce the failure. Nobody leaves a comment. A visitor using a screen reader hits a form with no labels, gets no useful error message, and closes the tab without a word. You never see the enquiry that didn't happen.

Low vision, color blindness, a broken wrist typing one-handed, a phone screen in bright sun — the list of situations that turn a working site into an unusable one is longer than the word "disability" tends to suggest on its own. Some are permanent. Some last a week. Some last five minutes, at a job site, holding a ladder with one hand.

The pattern that costs a small business the most is the quiet kind. A customer who could have booked, or called, or filled in the form, and instead just left. That loss never shows up in analytics as a reason. It shows up only as a number that's lower than it should be, month after month, with nothing pointing at the cause.

Why the legal question comes after the build question

Once you know accessibility is a build discipline, the legal side gets easier to think about clearly. Litigation tends to follow sites that were never built with any of this in mind. Not sites that made an honest attempt and missed a detail here and there.

The filing numbers are real and current. The litigation figures themselves, sourced properly, are worth reading in full rather than secondhand, because a summary from a stranger's email is not where you want to get your facts.

That's also where a corner-of-the-screen widget gets pitched, promising to make an old site compliant with one line of code. Before paying a monthly fee for anything like that, it's worth understanding what that kind of tool actually changes on the page, and what it leaves untouched.

The pages sitting next to accessibility: privacy, cookies, and image rights

Accessibility rarely travels alone on a small site. It sits next to three other pages that get copied from a template and never looked at again: the privacy policy, the cookie banner, and the source of every photograph on the site.

A privacy policy that lists data practices the site doesn't actually follow is worse than having no policy at all. And whether a plain brochure site needs one in the first place is a narrower question than it first looks.

The cookie banner has the same problem in miniature. Plenty of sites ask consent for tracking they never installed, which is worth untangling before deciding the banner needs to stay as written.

Image rights are the one that arrives as a letter instead of a warning. A photo pulled from a search result years ago can still generate a bill today, and knowing where every image on the site actually came from matters more than any checklist.

What you can check today without spending anything

You don't need a developer or a subscription to find out roughly where your own site stands. A short list of checks, done from your own keyboard and phone, covers a surprising amount of ground:

None of this takes long. Twenty minutes covers all five checks. A longer, step-by-step version of the same routine is worth working through once, properly, with a notebook open.

Raising it with whoever builds or maintains your site

If you're still choosing who builds the site, this is a fair question to bring to the first call. It tells you something a portfolio can't. What to actually ask about accessibility before you sign anything will tell you more about a candidate than a slick pitch deck will, and it sits inside the wider question of how to pick a builder in the first place.

If the site already exists, raise it as a specific, small request rather than a vague worry. Point at the contact form. Point at the pale grey text on the pricing page. Ask what it would take to fix each one.

If the list turns out longer than expected, a paid audit might be the faster path, and it's worth knowing what a good one actually contains before you agree to buy one.

More from the blog

All posts