Website Accessibility Checklist: WCAG Basics for Small Business Websites (2026)

Web accessibility means one simple thing: everyone can use your website — including people who navigate with a keyboard, who listen to the page with a screen reader, or who need stronger contrast to read comfortably. An accessible site reaches more customers, converts better, and is easier for search engines to understand.

The timing matters. The European Accessibility Act became enforceable on June 28, 2025, bringing accessibility obligations to private businesses selling to EU customers, with WCAG 2.1 Level AA as the technical benchmark. And yet the basics are still widely missed: the WebAIM Million 2026 analysis of the top one million home pages found low-contrast text on 83.9% of pages and missing alt text on 53.1%. Most failures are fundamentals, not edge cases.

This checklist covers the WCAG basics that matter most for a small business website, with a quick test for every item. You do not need to be a developer to run it. (General information only — not legal advice. If you have received a legal complaint about accessibility, talk to a lawyer first.)

Why a Small Business Should Care: Three Reasons

Legal risk is real, even if the rules differ by country. In the US, ADA-related web accessibility claims proceed through litigation with WCAG as the de facto standard. In the UK, the Equality Act 2010's "reasonable adjustments" duty is widely read as covering websites. In the EU, the European Accessibility Act now applies to private businesses serving EU customers (microenterprises are exempt).

You are leaving customers on the table. Every visitor who cannot read your text, operate your menu, or submit your form is a lost enquiry. Accessibility fixes help everyone: captions help people watching on mute, good contrast helps anyone reading a phone in sunlight, keyboard support helps power users.

Accessible markup is SEO-friendly markup. Proper headings, descriptive link text, alt text, and a declared page language are simultaneously accessibility wins and signals search engines use to understand your pages.

The Checklist

The checklist follows WCAG's four principles — Perceivable, Operable, Understandable, Robust. Work through it top to bottom.

Perceivable: Can Everyone Take In Your Content?

1. Every meaningful image has alt text; decorative images are marked empty. Screen readers announce images through alt text — describe informative images briefly, mark decorative ones empty so they are skipped. Test: run Lighthouse, WAVE, or axe DevTools (all free) and review every flagged image.

2. Text contrast meets the AA minimum: 4.5:1 for normal text, 3:1 for large text. The most failed check on the web — 83.9% of top home pages fail it (WebAIM Million 2026). Test: check your color pairs with a free contrast checker.

3. Information is never conveyed by color alone. "Required fields are in red" fails for anyone who cannot distinguish red — pair color with text or icons. Test: view the page in grayscale and confirm nothing important disappears.

4. Videos have captions; audio has a transcript. Spoken content needs accurate, synchronized captions (review auto-captions, do not trust them blindly); audio clips need transcripts. Test: play each video muted and confirm you can follow it fully.

5. The page reflows without horizontal scrolling, and text survives 200% zoom. At narrow widths the layout should collapse to a single column; zoomed to 200%, nothing should be cut off or overlapping. Test: zoom to 200% and scroll the whole page.

6. Headings follow a logical order. One H1 per page, then H2s and H3s in sequence — never skipping levels or using headings for styling. Screen reader users navigate by headings the way sighted users scan. Test: use a headings-map extension and read the outline like a table of contents.

Operable: Can Everyone Use Your Site?

7. Everything works with a keyboard alone — no mouse required. Every menu, button, link, field, slider, and modal must be reachable and operable by keyboard. Test: put the mouse away and Tab through the entire site. If you get stuck anywhere, you have failed this check.

8. The keyboard focus indicator is always clearly visible. As you tab, an obvious highlight must show where you are — never remove the focus outline in CSS for aesthetics. Test: during the keyboard run, confirm the focused element is always visible.

9. A "skip to main content" link is available. Keyboard users should not tab through the full navigation on every page. Test: press Tab on page load — the first focused element should offer to skip navigation.

10. There are no keyboard traps. If you can tab into a modal or widget, you must be able to tab out — with Tab, Shift+Tab, or Escape. Test: open every modal and confirm Escape releases you.

11. Tap and click targets are large enough and well spaced. Cramped links and tiny buttons are hard for everyone on mobile. Test: complete your main conversion (contact form, quote request) on a phone using your thumb.

12. Nothing important relies on hover or precise mouse movement. Hover-only dropdowns and vanishing tooltips exclude keyboard and touch users. Test: reach every menu and tooltip using only the keyboard and on a touchscreen.

13. No content flashes more than three times per second. Flashing can trigger seizures; rapid auto-playing carousels are the usual offender. Test: watch every animation on the site and remove anything that strobes.

Understandable: Can Everyone Make Sense of Your Site?

14. Every page has a descriptive, unique title. The browser-tab title is the first thing screen readers announce — "Plumbing Services in Austin | BrightFlow Plumbing" beats "Home". Test: read your browser tabs across the site; each should describe its page.

15. Link text makes sense out of context — no bare "click here." Screen reader users often list all links on a page; twelve "click here"s are useless. Test: extract all link text (WAVE lists them) and read it as a standalone list.

16. The page declares its language. A lang attribute on the <html> element tells screen readers which pronunciation rules to use — a one-line fix missing on 13.5% of top home pages. Test: view page source and confirm the attribute is present.

17. Form fields have visible, programmatically linked labels. Placeholder text is not a label — it vanishes when you type and screen readers may skip it. Every input needs a real label tied to it. Test: click each label; focus should jump to its field.

18. Errors are identified in text and explain how to fix them. Say which field failed and why in plain words ("Enter a valid email address"), not just a red border. Test: submit each form empty and with bad data; every error must be described in text.

19. Navigation and naming stay consistent across pages. Menus, buttons, and labels should appear in the same order with the same names everywhere. Test: compare the main menu and key buttons across five pages.

Robust: Is Your Code Built to Last?

20. The markup is valid and uses the right elements for the job. Buttons should be <button>, links <a>, headings real headings — not <div>s styled to look like them. Assistive tech relies on correct semantics. Test: the axe or WAVE scan flags misused roles.

21. Custom widgets expose a name, role, and state to assistive technology. A custom tab interface or accordion must announce what it is and its state (expanded, selected). Test: navigate custom widgets with a screen reader (NVDA is free on Windows; VoiceOver is built into Apple devices) and confirm each control is announced sensibly.

Seven Quick Tests You Can Run Today

Short on time? These seven tests catch most real-world failures — no coding required:

1. Automated scan with Lighthouse, WAVE, or axe DevTools — free, takes minutes. Catches missing alt text, contrast failures, missing labels, and structural issues. Note: automation finds roughly a third of issues; it is the starting line, not the finish.

2. Keyboard-only navigation. Mouse away, Tab through everything, operate every control, escape every modal.

3. Screen reader smoke test. NVDA (free, Windows) or VoiceOver (built into Apple devices) — listen to your homepage and try completing one key task.

4. Contrast spot-check on body text, headings, buttons, and text over images.

5. Caption check on every video with audio.

6. Form review — real labels and clear text error messages on every form.

7. 200% zoom — confirm nothing is cut off or overlapping.

The Most Common Failures (By the Numbers)

The most common failures are also the cheapest to fix (WebAIM Million 2026):

The top offenders are all basics — contrast, alt text, labels, link text. Fixing just these four puts a small business ahead of most of the web.

When to Get Professional Help

The DIY checklist covers the fundamentals, but some situations call for expert review: complex sites with custom interactive components, e-commerce checkouts where errors cost revenue, or a formal accessibility complaint (talk to a lawyer first, then remediate). Sometimes the honest result is that the site's foundations fight every fix — then the question is whether to remediate or rebuild, which our website redesign vs rebuild guide walks through. For budgeting, our business website cost guide gives realistic 2026 ranges, and custom web development done properly bakes accessibility in from day one.

Frequently Asked Questions

What is website accessibility?

Website accessibility means designing and building a website so that people with disabilities can perceive, understand, navigate, and interact with it — covering keyboard-only navigation, screen reader compatibility, sufficient color contrast, captions on video, labeled forms, and logical page structure. It benefits everyone, not just people with disabilities.

What is WCAG, and which version should I follow?

WCAG — the Web Content Accessibility Guidelines — is the international standard for web accessibility, published by the W3C, with conformance levels A, AA, and AAA. Level AA is the widely used target. WCAG 2.2 is the current W3C recommendation (since October 2023), while WCAG 2.1 Level AA remains the benchmark most regulations reference, including the EU's EN 301 549. For a small business, targeting WCAG 2.1 AA — ideally 2.2 AA — is the sensible goal.

Is my small business legally required to have an accessible website?

It depends on where you operate and who you serve — and this is general information, not legal advice. In the US, ADA-related web accessibility claims proceed through litigation with WCAG as the de facto standard. In the UK, the Equality Act 2010's "reasonable adjustments" duty is widely read as covering websites. In the EU, the European Accessibility Act (enforceable since June 28, 2025) applies to private businesses serving EU customers, with microenterprise exemptions. If unsure, consult a lawyer familiar with digital accessibility in your market.

What is the European Accessibility Act, and does it apply to me?

The European Accessibility Act (Directive EU 2019/882) requires many products and services — including e-commerce and digital services — to be accessible to people with disabilities. Enforceable since June 28, 2025, its technical benchmark (via EN 301 549) is WCAG 2.1 Level AA. It applies to businesses serving EU customers regardless of where they are based, with microenterprise exemptions. If you sell to the EU, assume it applies and verify with proper advice.

How do I check whether my website is accessible?

Start with the seven quick tests: a free automated scan (Lighthouse, WAVE, or axe DevTools), keyboard-only navigation of the whole site, a short screen-reader smoke test, contrast spot-checks, caption verification, a review of every form for real labels and clear errors, and a 200% zoom check. Automated tools catch roughly a third of issues, so the manual keyboard and screen-reader tests are essential, not optional.

What are the most common accessibility failures on business websites?

Per the WebAIM Million 2026 analysis of the top one million home pages: low-contrast text (83.9%), missing image alt text (53.1%), missing form labels (51%), empty links (46.3%), empty buttons (30.6%), and missing page language declarations (13.5%). The good news: these are all inexpensive fixes.

Do accessibility overlay widgets make my site compliant?

Most accessibility professionals say no. Overlays add a toolbar or script on top of your site but do not fix the underlying problems — missing labels, broken headings, keyboard traps — that this checklist targets, and they can interfere with the assistive technology people already use. Fix the underlying issues directly instead of buying a widget and calling the job done.

How much does it cost to make a website accessible?

It depends on the site's size and how deep the problems go. Fixing the basics — contrast, alt text, labels, headings, focus states — is often a modest project. Complex sites with custom components, or platforms that fight every change, cost more and sometimes justify a rebuild with accessibility built in from the start. Our business website cost guide gives realistic 2026 ranges for both fixes and rebuilds.

Make Your Website Work for Everyone

If this checklist turned up red flags, you are not alone — most are inexpensive to fix. Start with the highest-impact items: contrast, keyboard navigation, form labels, and headings.

We build websites and web apps with accessibility baked in from the first line of code, not bolted on at the end — so your site works for every visitor and meets the standards your market expects.

Get a free consultation — we will tell you exactly what your site needs and what it will cost.