Here is a question worth asking about your own website, and almost nobody does. If a customer could not use a mouse, could not see the screen clearly, or was reading one-handed in bright sun outside your shop, could they still get what they came for?
That is the whole of it. Accessibility is not a badge, not a plugin, and not a legal scare story. It is whether a real person can actually use the thing you paid for.
The people this is actually about
The word makes people picture a rare edge case. It is not one. It is the customer who left their reading glasses in the truck. It is somebody on a cracked phone screen. It is your older regulars, who are often your best regulars. It is anyone standing outside at noon here, where the sun turns pale grey text on a white card into a blank rectangle. It is a visitor on a weak signal who never loads the photo your entire message was written on top of.
None of those people send you an email about it. They leave, and you never learn they were there. That is what makes this worth checking rather than assuming.
What the standard actually asks for
There is a published standard for this, WCAG 2.1, and the level almost everyone means is AA. It is far more specific and far less mysterious than it sounds. A handful of its rules come up on nearly every small business site:
- Contrast. Normal size text has to reach a ratio of 4.5 to 1 against its background. Large text can sit at 3 to 1. Light grey on white fails this constantly, and it is the single most common thing I end up fixing.
- Keyboard. Anything you can do with a mouse has to work from the keyboard, and you have to be able to see where you are while you do it.
- Labels. Every field in a form needs a real label, not just placeholder text that disappears the second somebody starts typing.
- Alt text. An image that carries meaning needs a written description. An image that is pure decoration should be marked as decoration, so a screen reader skips past it instead of reading a filename aloud.
- Structure. Headings in order, real landmarks for the header, navigation, main content and footer, and a skip link so a keyboard user does not have to tab through your entire menu on every single page.
- Motion. If somebody has asked their device to reduce motion, the site should respect that and stop animating. It is one line of code and it is almost never there.
Read that list again and notice how much of it is simply building the page properly in the first place.
Five checks you can run in five minutes
You do not need a tool or a consultant for any of these. Open your own site and go.
- Put the mouse down. Press Tab over and over on your homepage. Can you reach every link and button, and can you always see which one you are on? If the highlight vanishes, somebody turned the focus outline off because they thought it looked untidy. That one choice locks out every keyboard user you have.
- Zoom to 200 percent. Control and plus on Windows, Command and plus on a Mac. Does the text reflow and stay readable, or does it start overlapping itself and sliding off the side of the screen?
- Take it outside. Open the site on your phone in full sun. Anything you cannot read out there is something a customer standing in your parking lot cannot read either.
- Turn a screen reader on for thirty seconds. VoiceOver on an iPhone, TalkBack on Android. Listen to your homepage. You will learn more in that half minute than any report will tell you, and the first thing you usually learn is that your logo is being read out as a jumble of letters.
- Click into one form field. Does the label stay visible once you begin typing? If the only label was the grey placeholder text, it is gone now, and so is the person's place in the form.
The failures I find most often
Nearly every site I look at has some of these, and none of them are exotic.
The focus outline removed sitewide. Grey body text that looked elegant on a designer's calibrated screen and fails contrast on everyone else's. Photos with no alt text, or alt text that just repeats the filename. A contact form built entirely out of placeholders. A dropdown menu that only opens on hover, which means it never opens at all on a phone. Text baked into an image, so it cannot be read aloud, cannot be zoomed cleanly and cannot be found by search.
Every one of those is a small fix on its own. Together they are the difference between a site that works for everybody and a site that quietly works for most people.
Why it is cheap now and expensive later
Built in from the start, accessibility costs close to nothing. It is choosing colors that pass before you fall in love with them, writing alt text while you place the photo, and using the right element instead of styling a div to look like a button. That is not extra work, it is the same work done in a sensible order.
Bolted on afterwards it is genuinely expensive, because the color palette, the layout and sometimes the markup all have to be reopened at once. This is the same pattern as everything else on a website: the cheap moment to do it right is before it exists.
I will be honest that I have never once seen accessibility on a web design quote I have been shown. That is exactly why I put it at the top of mine.
How we build
Every site we build targets WCAG 2.1 AA from the first line: contrast checked, visible focus outlines, semantic landmarks, a skip link, labels on every form control, alt text on meaningful images, and reduced motion respected. It is not an upgrade tier and it is not billed separately. It is what a finished site means here, for the same reason we publish our pricing instead of hiding it behind a call.
If you want to know where your current site stands before you talk to anybody, run it through our Site Check. It grades accessibility, SEO and performance and lists the fixes that matter most, in about a minute. There is no email wall and nothing gets sold to you at the end. And if you would rather just do the five checks above yourself this afternoon, that is a genuinely good use of an afternoon.