Picture someone browsing your site with a screen reader, because they're blind or their eyesight is too poor to read a screen. Or someone who can't use a mouse and is tabbing through every link with a keyboard. Or, far more common than either of those: someone squinting at low-contrast grey text on a white background, on a phone, in direct sunlight, just trying to find your phone number.
None of those people show up in the way you normally test your own site — clicking around on your own laptop, with your own eyesight, in a quiet room. That's exactly why accessibility problems are so easy to miss. The site looks fine to the person who built it and never gets checked against anyone else.
It's also usually framed the wrong way — as a legal risk to manage, or a checkbox for government and enterprise sites. In practice, it's simpler than that: it's just whether real visitors, with real limitations, can actually use what you built.
What Accessibility Actually Looks Like
Text people can read
Light grey text on a white background looks clean in a mockup and is genuinely hard to read for a lot of people — not just those with a diagnosed vision issue, just anyone in bright light or over a certain age. A simple contrast checker will tell you in seconds whether your body text and background actually pass a readable threshold.
Images that make sense without seeing them
Alt text is the short description attached to an image so a screen reader can say what it is. "Product photo" tells a visitor nothing; "navy blue canvas tote bag, front view" does. It also happens to help your images show up in Google Image search, so it's rarely wasted effort either way.
A site that works without a mouse
Try tabbing through your own homepage using only the keyboard. Can you reach every link and button, and can you tell where the focus is at each step? A menu or form that only responds to a mouse click locks out anyone using a keyboard, a switch device, or voice control.
Forms that say what they want
A form field needs a visible label attached to it, not just placeholder text that vanishes the moment you start typing — by then you've already forgotten which field is which, and a screen reader may never announce it at all.
Where This Gets Honest
Full compliance with a standard like WCAG is a real, detailed project — hundreds of individual criteria, and getting all the way there usually means an actual audit, not a weekend pass. If someone tells you your site is "100% accessible" from a quick glance, be skeptical.
The other place to be careful: accessibility overlay widgets, the little floating buttons that promise instant compliance with one script tag. Several of the biggest ones have ended up in lawsuits themselves, because they paper over problems in the code rather than fixing them, and can actively break the experience for the screen reader users they claim to help.
An overlay is a patch bolted onto a page that was never built to be accessible in the first place. It doesn't fix the underlying markup — it just adds another layer for a screen reader to fight through.
And in some places, this isn't purely a courtesy — accessibility lawsuits against small business websites are a real and growing category, particularly in the US under the ADA. But treating it as only a legal question misses the bigger one: a meaningful share of your potential visitors, in any country, are dealing with some kind of visual, motor, or reading limitation, and a site that ignores that is quietly turning them away.
The Honest Model
You don't need a full audit to get meaningfully better. A handful of fixes — real contrast, real alt text, a keyboard-navigable menu, labeled form fields — covers most of the everyday gaps, and none of them require rebuilding your site from scratch. Chasing a perfect compliance score on a simple brochure site is usually not where your time is best spent; getting the basics genuinely right is.
What matters is treating it as part of how the site is built, not a separate feature to bolt on later, and definitely not something a single script tag can shortcut.
What This Means for You
Somebody is going to land on your site who doesn't browse the way you do — older, tired, distracted, using a screen reader, or just stuck on a cracked phone screen in bad light. The basics of accessibility make your site work better for all of them, not just the ones a lawyer would recognize.
If you're wondering whether your own site would hold up to a basic accessibility check, that's the part I can help with — usually it's a short, specific list, not a rebuild.