A repeatable website accessibility audit helps a small business find barriers before they become customer-support problems. This checklist combines free automated tools with keyboard, responsive, and assistive-technology checks so you can review a website after redesigns, CMS updates, new content, and on a regular quarterly schedule.
Overview
Website accessibility means designing and maintaining pages that people with different abilities can use. An audit is not a single score or a one-time scan. It is a practical review of content, code, design, navigation, forms, media, and publishing workflows.
For a small business website, begin with the pages that affect visibility and revenue: the home page, contact page, service or product pages, pricing pages, booking or checkout flows, login screens, and any frequently visited landing pages. Review both the desktop and mobile experience. If the site is built with WordPress or another CMS, include reusable components such as menus, buttons, form blocks, pop-ups, and theme templates.
Use automated accessibility checkers as a starting point, not as proof that a site is fully accessible. A browser audit tool can identify some missing labels, contrast concerns, invalid markup, and other detectable patterns. It will not reliably judge whether alternative text is meaningful, whether a heading structure communicates the page correctly, or whether a keyboard user can complete a task. Those questions require human review.
Keep an audit record with the page URL, issue description, evidence, severity, owner, status, and date checked. A simple spreadsheet is enough. The record turns accessibility from an occasional concern into a manageable part of website maintenance.
What to track
1. Automated findings and page coverage
Run a reputable browser-based accessibility audit or an automated testing tool against representative pages. Record the tool, date, URL, and result rather than copying only the overall score. Recheck recurring templates after theme, plugin, framework, or component changes. A passing automated result does not replace manual testing, but repeated findings can reveal regressions quickly.
Prioritize issues that appear across many pages. One incorrectly coded button in a shared header may affect the entire site, while a single decorative image may affect only one page.
2. Keyboard navigation and focus
Unplug the mouse or avoid using it and complete common tasks with the keyboard. The Tab key should move through interactive elements in a sensible order. Shift+Tab should move backward, Enter or Space should activate controls where appropriate, and Escape should close dismissible dialogs when that behavior is provided.
Track whether every interactive element receives a visible focus indicator. Check menus, sliders, cookie notices, search fields, modal windows, date pickers, embedded forms, and checkout controls. A focus outline that disappears against the background is a usability defect even if keyboard navigation technically works.
3. Structure, labels, and text alternatives
- Headings: Confirm that each page has a clear main heading and that subheadings describe the sections that follow. Do not choose heading levels only to make text look larger.
- Links and buttons: Check that their names make sense out of context. Replace repeated, vague labels such as “Read more” when the destination is unclear.
- Form labels: Every input should have an associated, visible label or an equivalent accessible name. Instructions, required fields, and expected formats should be clear before submission.
- Alternative text: Describe the purpose of meaningful images. Mark purely decorative images appropriately so they are not announced unnecessarily. Avoid using file names or keyword-stuffed descriptions.
- Language and reading order: Check that the primary page language is set and that content makes sense when read from top to bottom without relying on visual placement.
4. Contrast, zoom, and responsive behavior
Use a contrast checker to review body text, headings, links, button labels, borders that convey information, and text placed over images. Test normal, hover, active, and disabled states separately. Do not rely on color alone to communicate an error, status, or required action.
Zoom the page and test it at narrow viewport widths. Text should remain readable without forcing users to scroll in two directions for ordinary content. Check whether menus, tables, banners, dialogs, and forms remain usable. A responsive layout can introduce clipped text, hidden controls, overlapping elements, or a focus order that no longer matches the visual order.
5. Media, errors, and task completion
Videos should provide captions when spoken information is necessary. Audio-only content needs an equivalent text alternative, and animated content should not create avoidable distractions or interfere with controls.
Submit forms with missing, invalid, and incorrectly formatted values. Error messages should identify the affected field, explain what needs to change, and remain available to people using a keyboard or screen reader. After correcting an error, confirm that the user does not lose entered information unnecessarily.
Issue-triage table
| Priority | Examples | Recommended response |
|---|---|---|
| Critical | A keyboard user cannot submit a form, open navigation, or reach essential content. | Fix before the next release or remove the blocked interaction temporarily. |
| High | Missing form labels, unusable focus states, unreadable contrast, or important images without useful alternatives. | Assign an owner and include the fix in the next planned maintenance cycle. |
| Medium | Unclear link text, inconsistent heading levels, or mobile layout problems on secondary pages. | Schedule, test, and verify across the affected template or page group. |
| Low | Minor wording, decorative markup, or isolated issues that do not block a task. | Group with related content or design improvements and document the decision. |
Cadence and checkpoints
Run a lightweight review monthly if the site publishes frequently or changes often. For a quieter small business website, a quarterly review is a reasonable baseline. In either case, repeat the audit immediately after a redesign, theme or CMS update, navigation change, new form, analytics or chat widget installation, or launch of a new landing-page template.
A practical monthly checkpoint can take less than an hour:
- Choose the home page, one conversion page, one form, and one recently changed page.
- Run an automated scan and record new or repeated findings.
- Complete the main visitor task using only the keyboard.
- Check headings, labels, alternative text, contrast, zoom, and mobile layout.
- Test one error state and one media element if the site uses them.
- Compare results with the previous audit and assign follow-up work.
For a larger site, divide coverage by template. Test a sample of pages from each content type rather than scanning only the home page. Keep a staging environment for fixes when possible, and verify the production page after deployment. Accessibility changes can interact with caching, JavaScript, CSS, and CMS plugins, so a successful staging test is not the final checkpoint.
How to interpret changes
Do not treat a higher or lower automated score as the only measure of progress. First ask whether the tested URLs, logged-in state, viewport, and tool configuration are comparable. A score may change because the tool changed, a third-party script loaded differently, or a new page was included.
Look for patterns. If many pages suddenly report missing labels, inspect the shared form component or theme template. If only one page changes, review its content block, custom HTML, embedded widget, or recent editor changes. If automated results remain stable but customers report that a task is difficult, prioritize the real task and reproduce it manually.
Track both defects and successful checks. Useful records include the number of pages reviewed, unresolved critical and high-priority issues, recurring template problems, keyboard task completion, and the date of the last screen-reader spot check. These measures show whether maintenance is reducing risk without pretending that accessibility can be summarized by one number.
For implementation work, coordinate accessibility checks with related site maintenance. Performance changes can affect keyboard behavior or script timing, while SSL, deployment, backup, and staging processes determine whether a fix reaches the live site safely. The staging environment guide explains how to test changes before publication, and the monthly maintenance checklist can help place accessibility checks in a broader routine.
When to revisit
Revisit this checklist monthly or quarterly, depending on how often the website changes. Also repeat it after a redesign, CMS or PHP update, theme or plugin replacement, migration, new marketing campaign, new form, navigation change, or addition of video and interactive content. A quarterly review should include a fresh sample of pages rather than repeating exactly the same URLs every time.
Before each review, update the testing tools, browser versions, assistive-technology methods, and internal references used by your team. Accessibility standards and practical testing guidance can evolve, and automated tools add or change rules. Check the current requirements that apply to your organization separately; this checklist is a quality-assurance workflow, not legal advice.
To start today, save four representative URLs, create an issue log, run one automated scan, and complete one important task with the keyboard. Fix the most disruptive issue, verify it on the live page, and record what changed. Then schedule the next review on the same maintenance calendar as backups, updates, uptime checks, and content reviews. For related technical checks, see the Core Web Vitals audit workflow and the website backup and restore strategy.