Website accessibility basics for a small business
An accessible website is one that people can use whether they see the screen, hear audio, use a mouse or move through the page with a keyboard or a screen reader. Many of your customers rely on at least one of those: people with low vision, colour blindness, hearing loss, tremors, or simply a small phone screen in bright sunlight. A site that works for them usually works better for everyone.
Accessibility also has a legal side. In the United States, businesses have faced lawsuits claiming their websites were not usable by people with disabilities, and many of those claims point to the Web Content Accessibility Guidelines (WCAG) as the measure. This guide is not legal advice; it covers the practical checks we run on small business sites against WCAG 2.1 at level AA, the level most often referred to.
What WCAG asks, in plain words
WCAG is published by the World Wide Web Consortium (W3C). It groups its requirements under four ideas: content must be perceivable (people can see or hear it in some form), operable (people can use every control), understandable (text and behaviour are clear and predictable) and robust (it works with the tools people use, such as screen readers). Level AA is a middle level that covers the problems that block people most often.
1. Text alternatives for images
Every image that carries meaning needs alternative text that says what it shows or does: "Red leather handbag, front view", not "IMG_2041". A logo that links home should say the business name. Images that are only decoration should have empty alternative text, so screen readers skip them. Pictures of text, such as a banner with the sale details baked in, should be avoided, or the same words should appear as real text on the page.
2. Colour and contrast
WCAG 2.1 AA asks for a contrast ratio of at least 4.5 to 1 between normal text and its background, and 3 to 1 for large text and for the parts of controls people need to see, such as the outline of a form field. Pale grey text on white and white text on a bright photo are the usual failures. Never use colour alone to carry meaning: a form that marks errors only in red should also say what is wrong in words.
3. Everything works with a keyboard
This is the single most useful test you can run yourself. Put the mouse aside, press Tab to move through the page and Enter or Space to use what is selected.
- Can you reach every link, button, menu and form field?
- Can you always see where you are? A clear focus outline should move with you; many sites remove it for looks.
- Does the order make sense, top to bottom and left to right?
- Can you open and close menus, pop-ups and image sliders, and does a pop-up let you leave with the Escape key?
- Are you ever trapped somewhere you cannot Tab out of?
4. Forms people can complete
Each field needs a visible label that stays in place, not only grey hint text inside the box that disappears when you type. Labels must be connected to their fields in the code so screen readers announce them. Error messages should say which field is wrong and how to fix it, and should not clear what the person already typed. Required fields should be marked in words, not only with colour.
5. Structure: headings, links and language
Screen reader users often move through a page by its headings, so use one main heading and real heading levels in order, rather than bold text that only looks like a heading. Link text should make sense on its own: "Read the shipping policy" rather than "click here". Set the page language in the code so the reader pronounces words correctly.
6. Video, audio and motion
Videos with speech need captions; auto-generated captions are a start but should be checked and corrected. Audio-only content needs a transcript. Anything that moves, flashes or plays by itself for more than a few seconds, such as a slideshow or a background video, needs a way to pause it, and nothing should flash more than three times a second.
7. Zoom and small screens
People should be able to zoom text to twice its size without losing content or functions, and the page should work on a narrow phone screen without scrolling sideways. Do not disable zoom in the page settings.
How to test without a big budget
- The keyboard test from step 3, on every page type: home, a product or service page, the contact form and the checkout.
- A free automated checker such as the accessibility audit built into Chrome's Lighthouse, or the WAVE tool from WebAIM. They find missing alternative text, low contrast and unlabelled fields quickly.
- A screen reader for ten minutes: VoiceOver is built into Apple devices and NVDA is free for Windows. Listen to your home page and try to submit your contact form.
- Zoom to 200 percent and use the site on a phone.
What a clean scan does not prove
Automated tools catch only part of the problems. They can tell that an image has alternative text, not whether the text is any good; they cannot judge whether a form makes sense or a menu works by keyboard. A page with no automated errors can still be unusable. Treat the scan as the first check, not the last.
Keep it from slipping
Accessibility drifts as pages change. Add the keyboard test and an automated check to your routine whenever a new page, theme or app goes live, publish an accessibility statement with a way for people to tell you about a problem, and fix what they report quickly.
The short version
Give meaningful images real alternative text, keep text contrast at 4.5 to 1 or better, make every control work and stay visible with a keyboard, label every form field and explain errors in words, use real headings and clear link text, caption video and let people pause motion, and allow zoom. Test with a keyboard, a free checker and a screen reader, and remember that a clean scan is a start, not proof.