Most accessibility advice assumes you have a developer on retainer and a spare quarter in the budget. You don't. This is a pragmatic plan for small business website accessibility that orders the work by impact, so the first afternoon you invest removes the problems most likely to block a real customer or trigger a complaint, and the cosmetic polish waits until later.
You don't need a full rebuild, a consultant, or an expensive overlay widget. You need a baseline, a short list of high-impact fixes, and a sensible way to handle the legal side. Here is that path, in order.
Start with a free scan to find the cheap wins
Before you change anything, get a baseline. Automated tools only catch part of all issues, but the ones they do catch tend to be the cheapest to fix: missing image descriptions, low colour contrast, form fields with no labels, and pages missing a language attribute. Run your homepage and one or two money pages (a key product page, your contact form) through a checker first.
Use the free AccessScan scan to get a prioritised list in a couple of minutes. Treat the output as a worklist, not a grade. A single number means little; a specific line like *button has no accessible name* tells you exactly what to fix and where. Re-run it after each batch of changes so you can watch the count drop.
The four fixes that block real customers
Accessibility is built on four WCAG principles: content must be Perceivable, Operable, Understandable, and Robust. In practice, four recurring failures cause most of the harm on small business sites. Clear these and you have removed the barriers that genuinely cost you sales and carry the most legal exposure.
1. Images without text alternatives
Every meaningful image needs alt text a screen reader can announce. A product photo should describe the product ("navy wool overcoat, front view"), not say "image123.jpg". Decorative images should have an empty alt attribute (alt="") so they are skipped. This is free to fix and you can do it yourself; see how to write alt text for the rules on logos, charts, and buttons-as-images.
2. Colour contrast that's too low
Pale grey text on white is the single most common failure. The thresholds are concrete: 4.5:1 for normal text, and 3:1 for large text (at least 18pt, or 14pt bold) and for UI components like button borders and form outlines. Fixing this is usually a one-line CSS change, and the same darker palette helps every customer reading on a phone in sunlight. The colour contrast requirements guide has the exact ratios.
3. Forms you can't fill in without a mouse
If your contact or checkout form has placeholder text but no real label tied to each field, screen reader users hear nothing useful, and the placeholder vanishes the moment someone types. Connect each visible label to its field, mark errors with text (not colour alone), and test that you can tab through the whole form and submit it using only the keyboard. See accessible forms and keyboard accessibility.
4. Things that only work on click
Dropdown menus, modals, and "add to cart" controls built as plain div elements often can't be reached by keyboard or announced to assistive tech. Using real button and link elements fixes most of this for free. If you run a custom theme or builder, this is the area most likely to need a developer.
Match the work to your platform
How you apply these fixes depends on what your site runs on, and most of the heavy lifting is theme and content work rather than custom code:
- WordPress: choose an accessibility-ready theme, fix headings and alt text in the editor, and audit your form plugin. See accessibility for WordPress.
- Shopify: most fixes live in theme settings and product content; check your checkout and quick-add buttons. See accessibility for Shopify.
- Wix, Squarespace, or Webflow: use the built-in alt text and contrast controls, and test keyboard navigation on interactive blocks. See the guides for Wix, Squarespace, and Webflow.
Whatever the platform, avoid "one-click" accessibility overlay widgets. They bolt a script onto a broken page instead of fixing the underlying HTML, and they have a poor track record of actually satisfying either users or regulators.
What the law actually requires (and where you might be exempt)
For businesses selling into the EU, the European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025. The technical baseline it points to is WCAG 2.2 Level A and AA, referenced through the European standard EN 301 549. That is the same checklist the four fixes above come from, so practical work and legal compliance pull in the same direction.
There is real relief for the smallest businesses. Microenterprises that provide services with fewer than 10 staff and under EUR 2,000,000 in annual turnover are largely exempt for those services. The exemption is narrower for products, and US ADA-style expectations run on a separate track, so if you sell internationally don't assume you're fully off the hook. The ADA vs WCAG vs EAA guide explains which regime applies to whom.
On penalties: enforcement and fines vary by member state, and can reach tens of thousands of euros. But for a small business the more common trigger is a customer complaint, not a regulator sweep, and the cheap fixes above are exactly what defuses those.
Document what you've done, then keep it from sliding back
Once you've cleared the high-impact issues, publish an accessibility statement. It shows good faith, gives users a way to report problems, and is expected under EN 301 549. You don't need a lawyer: the accessibility statement generator produces a starting draft, and what to include in an accessibility statement covers the required parts.
Then make it routine. Work through the accessibility checklist once for the whole site, add alt text and labels to new content as you publish it, and re-scan after any redesign or theme update. Accessibility degrades quietly every time someone adds an unlabelled image or a low-contrast banner, so a five-minute monthly check is what keeps the bill from ever getting large again.