Website Accessibility Checklist for Small Business Owners

By Dave TanguayPublished Editorial draft

Quick Answer

Start with a few important tasks: navigate the site with a keyboard, read it at a larger size, complete a form, and use the main shopping or inquiry controls. Record barriers with the exact page and steps. These checks help owners find problems and commission repairs, but they do not establish full accessibility conformance.

You do not need to inspect code to notice that a menu cannot be reached, an error message gives no useful instructions or a floating banner covers a button. A short owner review can uncover those barriers before a customer has to report them.

Use this checklist alongside W3C’s Easy Checks resource. W3C explicitly describes these as limited initial checks: a page can appear to pass them and still contain significant barriers.

Choose tasks and record your setup

Pick a service page, contact form and key navigation path. For a store, include a product with options and the cart. Use an authorized test arrangement for submissions or orders. Note the page URL, browser, device, date and any zoom or assistive technology settings.

Review the task from beginning to completion. A form that is easy to fill in can still fail when its validation message is inaccessible. Revisit shared controls such as menus, dialogs and consent notices on more than one page type.

1. Try the journey without a mouse

Use Tab and Shift+Tab to move through interactive elements. Watch where focus goes and whether you can see its indicator. Activate links and controls using their appropriate keyboard commands, such as Enter for a link and Enter or Space for a button. Some widgets use arrow keys as well.

  • Can you reach and operate the navigation, search and main action?
  • Does focus move through controls in a sequence you can follow?
  • When a dialog opens, can you use its controls and close it?
  • Can you continue after a menu, banner or popup without becoming trapped?
  • Is the focused control visible rather than covered by a sticky element?

If you are unfamiliar with the expected behavior of a particular widget, record that uncertainty for a reviewer. W3C’s keyboard guidance explains the broader requirement and its exceptions. A mouse click alone does not test keyboard access.

2. Enlarge the page and inspect the layout

Increase browser zoom and see whether text, controls and instructions remain usable. Check narrow layouts too. Look for clipped labels, overlapping text, disappearing actions and content hidden behind fixed banners.

Flag paragraphs that require repeated sideways scrolling to read each line. Some content, such as a data table or map, may need two-dimensional layout; that does not give unrelated text the same exception. W3C’s reflow guidance explains the technical criterion. Your owner review records symptoms for a proper evaluation.

3. Review page information, images and media

Check that page titles distinguish pages and headings describe their sections. Link text should make the destination or action understandable in context. Repeated vague labels can be hard to distinguish.

Ask whether an informative image has an alternative that conveys its purpose. Decorative images can appropriately have empty alternative text. A chart needs its important information in an accessible form, not a long list of visual details. An automated “alt text present” result cannot judge whether the wording is useful.

Check relevant videos for accurate captions and meaningful visual information that needs a spoken or text alternative. Review audio content for an appropriate transcript. Do not assume automatically generated captions are accurate without checking them.

4. Complete a form, including an error

Use a safe test submission. Confirm that fields have understandable labels, required information is identified, and instructions appear before they are needed. Then intentionally omit a required value or enter an invalid format.

Can you identify the affected field and understand how to correct it? Does the form preserve appropriate entries? After correction, is completion clear? W3C’s form notification guidance covers useful success and error feedback, including how it can be exposed to assistive technology. A visual check cannot confirm all of that programmatic behavior.

5. Check contrast and information conveyed by color

Inspect text on buttons, images, banners and muted backgrounds. Use a contrast tool for relevant color pairs rather than judging by eyesight alone. Apply the appropriate criteria for the text or control being checked; W3C’s text contrast guidance explains thresholds and exceptions.

Check whether an error, status or selected option is communicated through wording or another cue as well as color. A red border without an explanation leaves the visitor to guess what happened.

Turn observations into repair requests

For each barrier, save the task, exact URL, setup, steps, observed behavior and expected outcome. A screenshot or short recording can help when it shows the problem, but remove personal data before sharing it.

Illustrative record: “At increased browser zoom, the contact form’s submit button is covered by the fixed consent banner. The fields can be completed, but the button cannot be reached visually.” A developer can reproduce and investigate that report. It is more useful than “make the site accessible.” This is an example, not an audit result for this website.

Prioritize barriers that prevent important tasks, then retest the repaired component and related page types. Arrange a broader accessibility review when you need manual assistive technology testing, standards-based evaluation or a defined remediation scope. Our website audits can also help connect these findings with functional and content issues.

Key Takeaways

  • Follow complete visitor tasks rather than checking isolated screens.
  • Try keyboard navigation, larger text, forms, media and relevant contrast checks.
  • Record reproducible barriers and retest actual repairs.
  • Use initial checks to inform a broader evaluation, not to claim certification.

Frequently Asked Questions

Does passing this checklist prove WCAG conformance?

No. These are initial owner checks. Full evaluation needs an agreed scope, applicable criteria, appropriate expertise and additional testing. A clean automated scan is also insufficient.

Can an accessibility tool fix everything automatically?

A tool can assist with some checks or features. It cannot independently judge every interaction, alternative text decision or assistive technology experience. Evaluate the underlying website and verify repairs with appropriate manual review.

When should I repeat these checks?

Repeat relevant tasks after changes to shared navigation, forms, templates, apps or important content. Keep unresolved findings and retest results in a maintained record so later updates do not quietly restore a barrier.

Archives