You don’t have an accessibility expert on staff. Neither does almost anyone reading this. But that hasn’t stopped your website from needing to work for the roughly 1 in 4 US adults — about 61 million people — who report living with a disability, according to a CDC analysis of Behavioral Risk Factor Surveillance System data. Some of them will try to read your homepage, fill out your contact form, or check out on your site this week.
The good news: you don’t need an audit or a hire to catch most of what’s broken. Six checks — contrast, alt text, keyboard navigation, heading structure, form labels, and focus indicators — account for the overwhelming majority of what actually goes wrong on small business websites. This is the accessibility pass that the standard pre-launch checklist skips, because it’s built around device passes (desktop, mobile, tablet) rather than accessibility specifically. Here’s how to run it.
Why does accessibility matter if you’re not legally required to comply?
Because the failure rate on live websites is now getting worse, not better, and the legal exposure is rising with it. WebAIM’s 2026 analysis of the top one million homepages found detectable WCAG failures on 95.9% of pages — up from 94.8% the year before, reversing six straight years of small improvement. The average homepage now carries 56.1 distinct accessibility errors, a 10.1% jump from the prior year’s 51.
That’s not a niche compliance problem. It’s the default state of the web, which means it’s very likely the default state of your site too. And the legal side isn’t theoretical: UsableNet’s tracking of ADA digital accessibility lawsuits shows more than 5,000 lawsuits filed against websites, apps, and video content in 2025, with 36% of defendants reporting annual revenue over $25 million — a share that’s been climbing each year as plaintiffs’ firms move beyond only targeting large enterprises. Nearly 70% of filings target e-commerce, but healthcare, hospitality, and local service businesses show up too.
You don’t need to treat this as a legal-compliance exercise to take it seriously. Treat it the same way you’d treat a broken checkout flow: something that’s costing you real visitors, whether or not anyone ever files a complaint about it.
What can you check without any accessibility training?
Six things, and they map almost exactly onto what shows up most often in WebAIM’s error data. The Web Content Accessibility Guidelines (WCAG), maintained by the W3C, organize every requirement under four principles — content should be Perceivable, Operable, Understandable, and Robust (POUR) — but you don’t need to read the spec to catch the common failures. WebAIM’s homepage data shows the same six error types accounting for 96% of everything detected, seven years running: low-contrast text, missing alt text, unlabeled form fields, empty links, empty buttons, and missing document language.
Most of those map directly onto checks a non-expert can run in an afternoon: contrast, alt text, keyboard navigation, heading structure, form labels, and focus states. None of them require a screen reader license or a paid scanning tool. Here’s how to run each one.
How do you check color contrast without a designer?
Run every text-and-background color pairing through a free contrast checker and flag anything under a 4.5:1 ratio (3:1 is acceptable for large text — 18pt or 14pt bold and up). That threshold isn’t arbitrary — it’s the WCAG standard Nielsen Norman Group cites directly as the baseline for readable text against its background, and it’s the single most common failure on the web: low-contrast text appears on 83.9% of homepages in WebAIM’s most recent analysis, averaging 34 instances per page.
You don’t need design training to catch this. Paste each hex color pairing — body text, buttons, footer links, placeholder text in form fields — into a contrast checker and note anything that fails. Nielsen Norman Group also recommends a second, faster test: convert a screenshot of the page to grayscale. If any information disappears or becomes hard to distinguish once color is removed, that’s a sign the design is relying on color alone to communicate something — a common failure that light-gray body text and unstyled links share.
How do you test keyboard navigation in ten minutes?
Unplug your mouse and tab through the entire page. Every link, button, and form field should be reachable with the Tab key, operable with Enter or Space, and visibly show where focus currently sits — a highlighted outline or border around whatever’s selected. If you tab past something and can’t tell where you are, or you hit a control that a mouse click works on but Enter doesn’t, that’s a keyboard-accessibility failure.
This check matters more than it looks like it should. Keyboard navigation isn’t just for people who can’t use a mouse — it’s also how most screen reader users navigate, and it’s how the “Operable” principle in WCAG gets tested in practice. It’s a five-minute check with an outsized catch rate: broken tab order, invisible focus states, and dropdown menus that only open on hover (never on keyboard focus) are consistently among the most common issues flagged in accessibility reviews, and every one of them is catchable without any assistive technology of your own.
How should you check heading structure and image alt text?
Confirm your headings nest in order — one H1, then H2s, then H3s underneath the relevant H2, with no level skipped — and that every image carrying meaning has alt text describing what it shows. These two checks matter more than most founders assume: in WebAIM’s Screen Reader User Survey, 71.6% of respondents said headings are the primary way they find information on a long page, ahead of every other navigation method combined. If your headings skip from H1 straight to H4 for styling reasons, or a section uses a bold paragraph instead of a real heading tag, screen reader users lose the outline they rely on to skim your page the way a sighted visitor scans it visually.
Alt text is the other half of this check, and it’s missing on 53.1% of homepages according to WebAIM’s most recent scan — the second most common failure on the web after contrast. The fix doesn’t require a copywriter: look at each image and ask what it’s communicating. A product screenshot needs a description of what it shows; a decorative background pattern needs an empty alt attribute so screen readers skip it entirely instead of announcing a meaningless filename.
How do you turn what you find into fixes your developer can act on?
Pin each issue to the exact element it affects instead of describing it in a paragraph. “The contrast on the footer links is too low” forces your developer to hunt for which links, on which page, at what color value. A pinned comment on the specific link — with the failing color pair noted — removes the guesswork entirely. This is the same problem website annotation tools solve for any visual bug, and accessibility issues are visual bugs; they just fail a specific, checkable standard instead of a subjective one.
Simpl_Markup lets you click directly on the live page and drop a numbered pin on the exact element with the contrast, alt-text, or focus problem, then tracks that comment’s status — open, fixed, approved — until your developer resolves it. That’s a meaningfully different workflow from running the same review over a screenshot pasted into Slack, where “the third paragraph on mobile” is the most specific location anyone can manage. If your developer needs the task written up in a format they can act on immediately rather than interpret, that’s covered separately in how to turn website feedback into tasks a developer can actually execute — the same four-part structure (location, issue, fix, impact) applies directly to an accessibility finding.
None of this replaces a full accessibility audit if your business genuinely needs one — a real audit tests with actual assistive technology and real users, and Nielsen Norman Group’s own guidance is that five real users surface the issues an automated pass never will. But for the founder shipping a new site or reviewing a redesign before launch, six checks and a pinned comment for each finding catches most of what’s actually broken — which, per WebAIM’s numbers, is most of what’s out there.