Website accessibility basics for small businesses

The standard behind the checklist

The Web Content Accessibility Guidelines (WCAG 2.2) from the W3C are the widely used reference. They're detailed; the WCAG quick reference lets you filter them, and the W3C's Easy Checks are a good first pass for non-specialists. The checklist below covers common issues on small service-business sites. It isn't a full audit.

*Not legal advice. Requirements vary by country and sector.*

Content

• Images have text alternatives. Meaningful images have alt text that says what matters ("Technician servicing an outdoor AC unit"); decorative images have empty alt text so screen readers skip them.
• Text isn't in images. Phone numbers, prices and offers are real text.
• Links make sense out of context. "See water heater pricing" rather than "click here".
• Headings are in order. One H1, then H2s for sections, H3s within them — not chosen for size.
• Plain language. Short sentences, common words, explained jargon.
• Videos have captions if you use them.

Visual design

• Text contrast is high enough against its background. Light grey on white is a common failure.
• Colour isn't the only signal. Error fields have a message, not just a red border.
• Text can be enlarged to 200% without content being cut off or overlapping.
• Layouts work on narrow screens without sideways scrolling.

Keyboard and interaction

• Everything works with a keyboard. Tab through the page: can you reach the menu, links, form fields and buttons?
• Focus is visible. You can see where you are as you tab.
• No keyboard traps. You can tab out of menus, pop-ups and embeds.
• Pop-ups can be closed easily, including with the Escape key.
• Nothing moves or flashes without a way to pause it.
• Tap targets are big enough on mobile.

Forms

• Every field has a visible label, not just placeholder text.
• Required fields are marked in text, not only by colour or an asterisk without explanation.
• Errors are explained next to the field, in words.
• No puzzle CAPTCHA without an alternative; see form spam protection.

The W3C forms tutorial covers each of these.

How to check it yourself in 20 minutes

1. Tab through your homepage and contact page with the keyboard only.
2. Zoom the browser to 200% and check nothing breaks.
3. Turn on your phone's screen reader (VoiceOver or TalkBack) and try to find your phone number and submit the form.
4. Run a free automated checker for a first list of issues — remembering automated tools catch only some problems.

Prioritise the paths that matter

For a service business, the critical paths are: finding what you do, finding how to contact you, calling, and submitting a quote request. Fix anything that blocks those first.

On MendRev sites

MendRev builds mobile-first with readable text and big tap targets, and Website Pro includes a speed and accessibility pass. We don't claim formal certification against any standard unless that has been specifically scoped and tested.

Questions

Sources and further reading

• WCAG 2.2 w3.org
• WCAG quick reference w3.org
• Easy Checks w3.org
• W3C forms tutorial w3.org

Official documentation changes. Check the current version before you rely on a rule, limit or setting.