Website Accessibility Checklist for Small Businesses

Try using your website without a mouse. Can you open the menu, find a service, complete a form, and close a popup? If not, a customer who relies on a keyboard may encounter the same obstacle. Accessibility is easier to understand when you begin with a task someone needs to complete rather than a badge you hope to display.

This checklist is a practical starting point, not a legal opinion or a declaration of compliance. The W3C WCAG 2.2 reference provides detailed requirements and techniques. The obligations that apply to a particular business should be reviewed with appropriate specialists.

Follow the whole customer journey

Choose a few important tasks, such as finding service details, reading an article, and submitting an enquiry. Check each page and interaction in that journey. An accessible homepage does not compensate for a form or checkout that excludes people later.

Include menus, dialogs, media controls, validation messages, and confirmations. Third-party tools are part of the experience even when someone else supplies them. Record the specific obstacle, the affected task, and who can address it. That makes the review actionable instead of producing a vague statement that the site needs to be more accessible.

Check keyboard operation and visible focus

Use Tab and Shift+Tab to move through interactive controls. You should be able to tell which control has focus. Follow the order and ask whether it makes sense. Decorative elements should not interrupt the sequence, and important actions should not require a pointer or hovering.

Open a dialog, interact with it, and close it. Check that the user is not trapped and that focus returns to a sensible place. Menus and custom controls need appropriate keyboard behavior, not just a clickable shape. If a design uses familiar standard controls, preserve the behavior people expect instead of recreating it incompletely.

Make headings describe the structure

Use a clear page heading followed by meaningful section headings. Choose heading levels to communicate the relationship between sections, not merely to obtain a preferred font size. A screen reader user may navigate by headings, so a page full of bold paragraphs is not equivalent to a properly structured article.

Descriptive headings also help people scanning a long page. “How to request a repair” is usually more useful than “The next chapter.” Review the language with your audience in mind. Our website design brief guide can help make content structure part of the requirements before the page is designed.

Review contrast and information conveyed by color

Text and controls need enough contrast against their backgrounds for their intended use. Check the actual combinations, including text over images, muted descriptions, error messages, and disabled states. A brand palette that works on a poster may need adjustments for small interface text.

Don't use color alone to explain a state. A field outlined in red should also have an understandable message. A chart should provide labels or another way to distinguish categories. Follow the applicable WCAG criteria rather than assuming that one contrast measurement covers every element and interaction.

Label forms and explain errors

Every field needs an understandable label. Placeholder text disappears during entry and is not a dependable substitute. Explain required information and any format that a user must follow. Keep instructions near the relevant field rather than hiding them in a separate page.

When validation fails, identify the field and explain how to correct it. Preserve information already entered where appropriate. The visitor should know whether the submission succeeded and what happens next. An alert that appears visually but is not announced to assistive technology can leave some users uncertain about the result.

Use alternative text with a purpose

Describe informative images according to what they contribute in context. A photograph illustrating a process may need a concise description; a decorative flourish may need no spoken description. Repeating a caption or stuffing keywords into alternative text can make the experience more cumbersome rather than more accessible.

For linked images, consider what the link does. A logo leading to the homepage needs an appropriate accessible name. Complex charts may require a nearby explanation or data representation, not an extremely long image description. Image accessibility is a content decision as well as a technical one.

Make video and audio information available another way

A video explaining a service should not be the only place where essential information appears. Plan captions, transcripts, and other alternatives appropriate to the content. Captions should represent the relevant speech and sounds accurately, rather than relying unquestioningly on an unreviewed automated transcript.

Review autoplay, flashing, motion, and control access. A visitor should be able to understand and use the page without unexpected audio or a visual effect that obstructs the task. If movement communicates information, consider how that information remains available when motion is reduced or the media cannot be played.

Check text enlargement and small screens

Increase text size and review whether content remains readable without being cut off or overlapping controls. Use representative small screens and pay attention to menus, dialogs, and long form labels. A layout can appear responsive while still preventing someone from using larger text settings.

Avoid instructions that depend only on position, such as “click the button on the right,” when the layout changes. Make links and controls identifiable by their purpose. The website launch checklist puts these checks alongside the other tasks needed for a functioning release.

Combine tools with human review

Automated scanning can identify selected problems, but it cannot establish that every meaningful task is accessible. Keyboard testing, assistive-technology review, and feedback from people with disabilities can reveal issues a scan misses. Treat a clean scan as one result, not as proof that the website is universally usable.

Accessibility overlays or widgets do not replace improvements to underlying content and controls. Review any tool against its actual capabilities and limitations. Our accessibility risk-reduction service page is a starting point for discussing the work; no widget or general checklist should be described as a guarantee against legal claims.

Common accessibility questions

Can accessibility be added after launch?

Improvements can be made later, but planning headings, controls, forms, and media early often avoids rework. Include the main journeys in the initial requirements and review them whenever functionality changes.

Does an automated score prove compliance?

No. Automated tools cover only part of the evaluation. Compliance and usability require a broader assessment appropriate to the website and applicable requirements.

What should a small business fix first?

Prioritize obstacles that prevent people from completing essential tasks, such as inaccessible navigation or forms. Follow with content, media, and broader improvements through a documented plan rather than assuming one quick fix resolves everything.

Make accessibility part of routine maintenance

Recheck when content, forms, plugins, or connected tools change. Discuss your website's accessibility needs and keep a record of issues, owners, and completed improvements. The aim is a usable customer experience, not a one-time decoration on the footer.