Website Accessibility for Small Business: WCAG Guide
By Nemanja Vukmirović, Lizzard Solutions. Last updated 11 November 2026.
Some of your visitors can’t use a mouse, can’t see low-contrast grey text, or hear your website through a screen reader. If your menu, contact form or checkout fails them, they leave, and you never find out why.
This guide explains website accessibility for small business in plain language: what WCAG asks for, when EU law applies to you, a 15-minute self-test, and the fixes that solve most problems. No legal jargon, no invented numbers.
TL;DR
- Website accessibility means people with disabilities can perceive, use and understand your site, with a keyboard, a screen reader or zoom.
- WCAG 2.2 level AA is the practical target. The most common failures are low contrast, missing alt text, unlabeled forms and keyboard traps.
- The European Accessibility Act covers e-commerce and some other consumer services from 28 June 2025, but exempts micro-enterprises that provide services.
What Is Website Accessibility?
Website accessibility is the practice of building a site so that people with visual, hearing, motor or cognitive disabilities can use it fully. In practice it means text alternatives for images, enough color contrast, full keyboard control, clear form labels, captions for video and content that still works when zoomed to 200%.
The global standard is the Web Content Accessibility Guidelines (WCAG), published by the W3C. W3C’s WCAG overview groups every rule under four principles, often shortened to POUR:
| Principle | What it means | Small business example |
|---|---|---|
| Perceivable | Content can be seen or heard in more than one way | Alt text on product photos, captions on your promo video |
| Operable | Everything works without a mouse | The menu and contact form work with Tab and Enter |
| Understandable | Text and behavior are predictable | Form errors say what is wrong and how to fix it |
| Robust | Works with assistive technology | Buttons are real buttons, not clickable images |
WCAG has three levels: A (minimum), AA (the usual legal and contractual target) and AAA (strictest). Aim for AA. The current version is WCAG 2.2.
Key takeaway
Accessibility is not a separate “version” of your site. It is how the normal site is built: semantic HTML, contrast, labels and keyboard support.
Action for today: write down the three pages that earn you money, usually the homepage, a service or product page, and the contact or checkout page. Test those first.
Does the European Accessibility Act Apply to My Business?
The European Accessibility Act (Directive 2019/882) sets accessibility requirements for certain products and services sold to consumers in the EU. For services, it applies to those provided after 28 June 2025. Covered services include e-commerce, banking, e-books, electronic communications and parts of passenger transport, such as websites and ticketing.
- You sell online to EU consumers (a webshop or online booking with payment): your e-commerce service is likely in scope.
- You are a micro-enterprise providing services, meaning fewer than 10 employees and annual turnover or balance sheet total of no more than €2 million: the Directive exempts you from the service requirements.
- You only sell business-to-business or run a brochure site with no consumer transactions: the EAA e-commerce rules generally don’t target you.
- You are a Serbian company: the EAA is EU law, but it can matter when you sell to consumers in EU countries. Check national rules where you trade.
Note
This section is general information, not legal advice. Scope depends on what you sell, to whom and where. Confirm your situation with a lawyer if you run a webshop for EU customers.
Even when no law forces you, the business case holds. An accessible form is easier for everyone, including people on a phone in bright sunlight.
Action for today: answer two questions: do you sell to EU consumers online, and are you above the micro-enterprise threshold? If both are yes, put an accessibility review on this quarter’s list.
A 15-Minute Accessibility Self-Test
You don’t need special software to find the biggest problems. These steps are based on W3C’s Easy Checks, which anyone can run in a browser.
- Unplug the mouse. Press Tab through the homepage. Can you see where focus is at every step? Can you open the menu, reach every link and submit the contact form?
- Zoom to 200%. Press Ctrl and + a few times. Text should reflow without overlapping or forcing sideways scrolling.
- Check contrast. Paste your text and background colors into WebAIM’s contrast checker. Normal text needs a ratio of at least 4.5:1 for AA.
- Read the image alt text. Use your browser’s inspector or an accessibility extension. Informative images need a short description, decorative ones an empty alt.
- Submit the form empty. Does the error message say which field is wrong, in text, not only in red?
- Play a video. Are captions available? Does anything autoplay with sound?
Example: a typical problem we see on small business sites is a contact form with placeholder text instead of labels. It looks clean, but the hint disappears when you start typing, and a screen reader may announce only “edit text”. Adding a visible label fixes both.
Action for today: run steps 1 and 3 on your contact page and note every failure.
The 10 Most Common Accessibility Fixes
Most issues come from a short list. Fix these and you cover a large share of what an audit would flag.
| Problem | Fix | Who fixes it |
|---|---|---|
| Low-contrast text | Darken text or lighten backgrounds to reach 4.5:1 | Designer |
| Images without alt text | Describe informative images; empty alt for decoration | Content editor |
| Form fields without labels | Visible <label> tied to each input | Developer |
| No visible focus outline | Never remove focus styles; style them instead | Developer |
| Clickable divs instead of buttons | Use real <button> and <a> elements | Developer |
| Skipped heading levels | One H1, then H2 and H3 in order | Content editor |
| Links that say “click here” | Descriptive link text | Content editor |
| Video without captions | Add captions and a transcript | Content editor |
| Pop-ups that trap focus | Close with Esc; return focus after closing | Developer |
| Missing page language | Set lang="en" (or "sr") on the page | Developer |
Some fixes also help search. Descriptive headings, alt text and link text are part of good technical SEO for small business websites, because search engines read structure the same way assistive technology does.
Watch out
Accessibility overlay widgets promise one-line compliance. They don’t fix broken HTML underneath, and they can get in the way of the screen readers people already use. Fix the source instead.
Action for today: pick the two fixes in the table that a content editor can do without a developer and do them on your main pages.
Forms, CAPTCHAs and Checkout: Where Customers Get Stuck
Forms are where accessibility turns into revenue. A visitor who can’t submit a quote request is a lost lead, not a statistic.
- Label every field and mark required fields in text, not only with color or an asterisk.
- Explain errors next to the field and keep what the user already typed.
- Avoid puzzle CAPTCHAs. Prefer invisible or low-friction checks. Our guide to contact form spam protection covers options that stop bots without blocking people.
- Don’t time out silently. If a session expires, warn first and allow more time.
- Test payment and login steps with a keyboard. Third-party widgets are frequent offenders.
Action for today: fill in your own contact form using only the keyboard, then submit it with one field left wrong.
How to Build Accessibility Into Your Website
Fixing accessibility after launch costs more than building it in. Whether you use WordPress, Webflow or a custom build, the same rules apply. Our comparison of WordPress, Webflow and custom builds notes that themes and templates vary a lot, so test before you commit.
- Before design: choose brand colors that pass contrast, including button text.
- During build: require semantic HTML, keyboard support and labels in the brief or contract.
- Before launch: add accessibility checks to your website launch checklist.
- After launch: re-test key pages after every redesign, new plugin or new form.
- Publish an accessibility statement with a contact for people who hit a barrier.
For a broader health check, our website audit checklist puts accessibility next to speed, SEO and security, so you can prioritize in one pass.
Action for today: add one line to your next website brief: “The site must meet WCAG 2.2 level AA on all public pages.”
Website Accessibility for Small Business: FAQ
What is WCAG 2.2 level AA?
WCAG 2.2 is the current version of the W3C’s Web Content Accessibility Guidelines. Level AA is the middle of three conformance levels and the usual target in laws, public contracts and procurement. It includes requirements such as 4.5:1 text contrast, keyboard access, visible focus, form labels and captions for prerecorded video.
Is website accessibility a legal requirement for small businesses?
It depends on where and what you sell. In the EU, the European Accessibility Act covers e-commerce and some other consumer services provided after 28 June 2025, but micro-enterprises providing services are exempt. Public sector sites have their own rules. This is general information, so confirm your case with a lawyer.
Can an accessibility plugin make my site compliant?
No plugin can make a site compliant on its own. Overlays and widgets add a toolbar on top, but missing labels, broken keyboard navigation and poor heading structure remain in the code. Plugins that help authors add alt text or check contrast are useful. The real fix is in the HTML, design and content.
How do I test my website for accessibility?
Start with a manual check: navigate with only the keyboard, zoom to 200%, check color contrast and review alt text and form labels. Automated tools catch some issues quickly, but not all of them. For a webshop or a site in a regulated sector, add testing with a screen reader or an expert review.
Want a second pair of eyes? Our free website audit flags technical problems on your key pages and tells you what to fix first.
Need your website to work for every visitor?
We can review your key pages against WCAG 2.2 AA and fix the issues in your theme or code.
Book a free consultation