← All articles

Websites

Website accessibility for small businesses: a practical WCAG checklist

A 20-point accessibility checklist you can run on your own site with a keyboard, a phone and your browser's zoom, based on WCAG and the W3C's own easy checks.

5 min read

You can find most of your website's accessibility problems yourself in under an hour, with no special software: tab through the page with your keyboard, zoom to 200%, read your image descriptions, check your forms and captions, and look hard at text contrast. The 20 checks below are based on the Web Content Accessibility Guidelines (WCAG), the international standard, and on the W3C's own "easy checks" for a first review. They won't make you fully compliant on their own, but they catch the problems that show up on almost every small-business site.

Why this is worth an hour

Accessibility problems are the norm, not the exception. WebAIM's 2026 scan of the top one million home pages found detectable WCAG failures on 95.9% of them, with an average of 56.1 errors per page. The most common problems were low-contrast text (83.9% of pages), missing image descriptions (53.1%), unlabelled form fields (51%), empty links (46.3%), empty buttons (30.6%) and a missing page language (13.5%).

Every one of those is cheap to fix, and each one is a customer who can't read your offer, can't fill in your quote form or can't find your phone number. Accessible sites also tend to be easier for everyone: older visitors, people on a small phone in bright sunlight, someone with a broken wrist.

There can be a legal side too. In Ontario, for example, the AODA requires businesses and non-profits with 50 or more employees to make public websites meet WCAG 2.0 Level AA (with exceptions for live captions and pre-recorded audio description). Other provinces and countries have their own rules, so check what applies where you operate.

Which WCAG, which level

WCAG has three levels: A (the minimum), AA (the usual target in laws and contracts) and AAA (the highest, rarely required for a whole site). The current version is WCAG 2.2, published in October 2023. Newer versions add to older ones, so a site that meets 2.2 AA also covers 2.0 AA. WCAG 3 is still an early draft. For a small business, aim for WCAG 2.2 Level AA.

The 20-point checklist

Run these on your homepage, your main service page and your contact or booking page. Those are the pages where problems cost you the most.

Keyboard and focus

  1. Tab through the whole page. Click in the address bar, then press Tab repeatedly. Every link, button and form field should be reachable, in a logical order.
  2. You can always see where you are. A visible outline or highlight should show which element has focus. If it disappears, keyboard users are lost.
  3. Nothing traps you. You should be able to tab into and out of menus, pop-ups, maps and chat widgets. If you get stuck in a cookie banner or a booking widget, that's a serious problem.
  4. Menus open with the keyboard. Dropdown menus should open with Enter or Space, not only on mouse hover.
  5. Pop-ups close with Escape and return you to where you were.

Text and colour

  1. Zoom to 200% (Ctrl or Cmd and the plus key). Text should grow without overlapping, getting cut off or forcing you to scroll sideways to read a sentence.
  2. Contrast is strong enough. WCAG asks for at least 4.5:1 between normal-size text and its background. Light grey text on white and white text on a photo are the usual failures. A free online contrast checker gives you the ratio in seconds if you're unsure.
  3. Colour is never the only signal. Required fields, errors and links should not rely on colour alone. Add an asterisk, a word or an underline.
  4. Text is real text. Prices, hours and phone numbers inside images can't be read by screen readers, enlarged cleanly or found by Google.

Images and media

  1. Informative images have descriptions. Your alt text should say what the image tells the visitor ("Technician installing a heat pump on a brick house"), not "image1.jpg."
  2. Decorative images are skipped. Background textures and dividers should have empty alt text so screen readers don't announce them.
  3. Videos have accurate captions. Automatic captions are a start, but the W3C's guidance is to check them, because errors in names, prices and technical terms are common.
  4. Nothing plays sound on its own without a clear way to stop it.
  5. Moving content can be paused. Sliders, carousels and animated banners need a pause or stop control, and nothing should flash more than three times per second.
  1. Each page has a clear, unique title in the browser tab ("Drain cleaning in Hamilton | Smith Plumbing," not "Home").
  2. Headings follow a logical order. One main heading, then sub-headings. Text that looks like a heading should be marked up as one.
  3. Link and button text makes sense alone. "Book a consultation" beats "Click here." Icon-only buttons (a phone icon, a hamburger menu) need a hidden text label, or a screen reader announces an empty button.
  4. The page language is declared. Your developer can confirm that the page code states English or French, so screen readers use the right pronunciation. Bilingual sites need it on each language version.

Forms

  1. Every field has a visible label that stays visible while typing. Placeholder text that disappears is not a label.
  2. Errors are clear and specific. "Please enter a phone number with 10 digits" is useful. A red outline with no words is not.

On phones, also check that buttons are large enough to tap. WCAG 2.2 Level AA sets a minimum target size of 24 by 24 CSS pixels, with some exceptions such as links inside a sentence.

What to fix first

Not all problems are equal. A practical order:

  1. Anything that blocks a contact or a sale: a form you can't complete by keyboard, a booking widget that traps focus, a phone number that's only in an image.
  2. Contrast and text size on your main pages, since they affect the most people.
  3. Alt text and captions on images and videos that carry real information.
  4. Headings, titles and link text across the site.

When a manual check isn't enough

This checklist catches a lot, but not everything. Bring in a specialist when:

  • you have a legal obligation to meet a standard and need to document compliance;
  • your site has complex features: online booking, a client portal, e-commerce checkout or embedded third-party tools;
  • you've received a complaint or an accessibility request;
  • you're about to redesign, which is the cheapest moment to build it in.

Be wary of "one-line overlay" products that promise instant compliance by adding a widget. They don't fix the underlying code, and they can't write meaningful alt text or captions for you.

How PNE handles accessibility

When PNE Solutions builds a site through our website design service, contrast, keyboard navigation, form labels, page language on both FR and EN versions and image descriptions are part of the build rather than an add-on. If you already have a site, the checklist above is a good way to judge whether it needs fixes or a rebuild.

Sources

Free website review

Want a site that brings in calls?

Tell us about your business and your current site. We’ll reply with what we would change first.

Prefer to talk? Book a free 30-minute call or call (647) 388-2843.

Keep reading