Accessibility Audit Checklist for Small Business Websites
A step-by-step accessibility checklist to find and fix common issues on small business websites — from alt text to forms — before they cost you customers.
One in four U.S. adults lives with a disability — roughly 61 million people who may struggle to use your website if it has accessibility problems. These are not obscure edge cases. They are buttons that cannot be clicked with a keyboard, images with no descriptions, and text that is nearly invisible against its background.
The WebAIM Million report, which tests the home pages of the top one million websites annually, found an average of over 50 detectable accessibility errors per page in 2024. Small business sites built quickly on templates tend to fare worse.
The good news: the most impactful fixes are straightforward. You do not need to be a developer. This checklist walks you through what to look for, why it matters, and how to fix the problems that affect real people and real revenue.

Why Accessibility Matters for Small Businesses
You are losing customers right now. People who cannot navigate your site leave without explanation. They go to a competitor. This includes people with permanent disabilities, temporary injuries, aging eyes, or situational limitations like holding a baby while trying to book an appointment on their phone.
Legal risk is real and growing. The Department of Justice has confirmed that the Americans with Disabilities Act applies to websites. ADA-related web accessibility lawsuits have increased every year since 2018, and small businesses are not exempt. A single demand letter typically seeks $5,000 to $25,000 in settlement.
Accessibility improves your site for everyone. Proper heading structure helps SEO and Core Web Vitals scores. Good color contrast makes text easier to read in sunlight. Keyboard navigation helps power users. These are not extras — they are basic usability.
Before You Start
- A computer with a keyboard (for testing keyboard navigation)
- Your website open in Chrome or Firefox
- About 60 minutes for a thorough first pass
- A spreadsheet or document to log issues
Everything in this checklist can be tested manually or with free browser tools.
The Checklist
1. Keyboard Navigation
Test: Can someone use your entire website without a mouse?
Put your mouse aside. Starting from your home page, press Tab repeatedly. You should see a visible outline move from link to link, button to button, through your navigation and page content.
Check for these problems:
- ☐ Can you see where the focus is at all times? (If the outline disappears, your CSS may be hiding it)
- ☐ Can you reach every link, button, and form field by tabbing?
- ☐ Can you open and navigate dropdown menus with the keyboard?
- ☐ Can you close pop-ups and modals by pressing Escape?
- ☐ Does the tab order follow a logical sequence (left to right, top to bottom)?
Example: A hair salon has a "Book Now" button built with a <div> styled to look like a button instead of an actual <button> element. A customer using voice control software — which relies on proper button semantics — literally cannot book an appointment.
Fix: Use real HTML elements for interactive things. Buttons should be <button>, links should be <a>, form fields should be <input>, <select>, or <textarea>. If your site builder lets you choose element types, always pick the semantic option.

2. Images and Alt Text
Test: Does every meaningful image have a text description?
Right-click any image on your site and select "Inspect" to see its HTML. Look for the alt attribute.
- ☐ Does every informational image have descriptive alt text?
- ☐ Are decorative images (backgrounds, dividers) marked with empty alt text (
alt="")? - ☐ Do alt descriptions actually describe the content, not just say "image" or "photo"?
- ☐ Are images of text avoided where real text could be used instead?
Good vs. bad alt text:
| Bad | Good |
|---|---|
alt="image1" | alt="Front entrance of Garcia's Bakery on Main Street" |
alt="photo" | alt="Three-tier wedding cake with white fondant and pink roses" |
alt="banner" | alt="Summer sale: 20% off all services through August" |
| (missing entirely) | alt="Team photo of five staff members in the workshop" |
Screen readers announce images by reading alt text aloud. Without it, a blind user hears "image" or nothing. Your product photos and informational graphics become invisible.
If your site has many images, a free site audit can quickly flag which ones are missing alt text so you do not have to inspect them individually.
3. Color Contrast
Test: Is your text readable against its background?
WCAG requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (18px bold or 24px regular).
- ☐ Is body text clearly readable against the background?
- ☐ Are links distinguishable from surrounding text (not just by color alone)?
- ☐ Do buttons have sufficient contrast between text and background?
- ☐ Is placeholder text in form fields readable?
- ☐ Does the site remain usable for someone who cannot perceive color differences?
A problem you probably have: Light gray text on a white background. That elegant #999999 on #FFFFFF has a contrast ratio of 2.8:1 — well below the 4.5:1 minimum.
Fix: Darken your gray text to at least #767676 for 4.5:1 on white. Better yet, use #595959 or darker for comfortable reading.
4. Headings and Page Structure
Test: Does your page have a logical heading hierarchy?
Headings (H1 through H6) are not just visual styling. Screen readers use them to build a page outline that lets users jump directly to sections.
- ☐ Does every page have exactly one H1?
- ☐ Do headings follow a logical order (H1 → H2 → H3, no skipping)?
- ☐ Are headings used for structure, not just to make text bigger?
Broken heading structure:
H1: Welcome to Our Site
H3: Our Services ← skipped H2
H2: About Us
H4: Contact ← skipped H3
Correct heading structure:
H1: Garcia's Plumbing — Licensed Plumbers in Austin
H2: Our Services
H3: Emergency Repairs
H3: Water Heater Installation
H2: Service Areas
H2: Contact Us
Most website builders let you set heading levels in their text editor. If you have been using headings just because they look bigger, switch to proper heading hierarchy and control the visual size with your builder's style settings.
5. Forms and Labels
Test: Are your forms usable without seeing the screen?
- ☐ Does every form field have a visible label (not just placeholder text)?
- ☐ Are labels programmatically connected to their fields?
- ☐ Are required fields indicated with text, not just color?
- ☐ Do error messages explain what went wrong and how to fix it?
- ☐ Can you complete and submit every form using only a keyboard?
The placeholder trap: Many sites use placeholder text as the only label. The text inside the field ("Enter your email") disappears the moment someone starts typing. A person who looks away and looks back has no idea what that field was for.
Fix: Add a visible label above or beside each field. Keep the placeholder as supplementary help, but never as the sole identifier.

6. Links and Buttons
- ☐ Does every link clearly describe where it goes? (No "click here" or "read more" without context)
- ☐ Do links that open in a new tab warn users? (Add "opens in new tab" text or an aria-label)
- ☐ Are links visually distinguishable from regular text?
- ☐ Do buttons describe their action? ("Submit appointment request" beats "Submit")
Before: "To learn about our pricing, click here. For our hours, click here."
After: "View our pricing. Check our business hours."
Screen reader users often navigate by pulling up a list of all links on a page. Five links that all say "click here" are useless.
7. Video and Audio Content
If your site has video or audio content:
- ☐ Do videos have captions?
- ☐ Do audio-only files have transcripts?
- ☐ Does no media auto-play with sound?
- ☐ Can all media players be controlled with a keyboard?
Auto-playing video with sound is one of the most disruptive accessibility failures. It disorients screen reader users and is problematic for people with cognitive disabilities. If you auto-play video, keep it muted with visible controls.
8. Mobile and Touch
- ☐ Are touch targets at least 44×44 pixels?
- ☐ Is content readable without zooming on mobile?
- ☐ Does the site work in both portrait and landscape orientation?
- ☐ Can users pinch-to-zoom? (Never disable this)
If your phone number link is tiny 12px text, people with motor impairments and people with large fingers alike will struggle to tap it.
Putting It Into Practice: A Restaurant Website Audit
Let us walk through this checklist on a typical small restaurant site built two years ago on a template.
Keyboard test (5 minutes): Tabbing through the home page reveals the hamburger menu only responds to mouse clicks. The "Order Online" button never receives focus. Two critical failures immediately.
Image check (10 minutes): The food gallery has 12 photos, none with alt text — the template left them blank. The logo says alt="logo" instead of alt="Garcia's Kitchen logo". A screen reader user gets zero information from your most persuasive content.
Contrast check (5 minutes): The "Reservations" button uses white text on light orange — ratio of 2.1:1. Footer links are gray on dark gray at 2.5:1. Both fail WCAG minimums.
Headings (5 minutes): The home page has three H1 tags (the template used H1 for every section title). The menu page has no H1 at all.
Forms (5 minutes): The reservation form uses placeholder-only labels. Required fields are marked with red asterisks but no text explanation.
Total: 30 minutes, over a dozen concrete issues found. Each has a specific fix. None require hiring a developer for most website builders.
Prioritizing Your Fixes
Fix first (blocks access entirely):
- Keyboard navigation failures on primary actions (booking, purchasing, contacting)
- Missing form labels on critical forms
- Auto-playing media with sound
Fix second (degrades experience significantly):
- Missing alt text on informational images
- Low contrast on body text and buttons
- Broken heading hierarchy
Fix third (important but lower friction):
- Vague link text
- Missing new-tab warnings
- Small touch targets
Keeping Accessibility on Track
Every time you add content, change your theme, or install a plugin, new issues can appear. Build these habits:
- Add alt text every time you upload an image
- Check color contrast before approving design changes
- Tab through any new page or form before publishing
- Test with your phone regularly
- Run an automated scan quarterly to catch regressions
Automated tools catch roughly 30 to 40 percent of accessibility issues — they are excellent for flagging missing alt text, contrast failures, and structural problems. Manual testing, especially keyboard navigation, catches the rest.
Run a free audit of your site with FreeSiteAudit to get an instant snapshot of accessibility, performance, and SEO issues. It takes less than a minute and gives you a prioritized list of what to fix first.

Quick-Reference Mini Checklist
Print this or bookmark it for your next content update:
- ☐ Every image has descriptive alt text (or empty alt for decorative)
- ☐ Text contrast ratio is at least 4.5:1
- ☐ All interactive elements are keyboard accessible
- ☐ Every form field has a visible, connected label
- ☐ Headings follow a logical H1 → H2 → H3 order
- ☐ Links describe their destination
- ☐ No media auto-plays with sound
- ☐ Touch targets are at least 44×44 pixels
- ☐ The site works without a mouse
Your website is your storefront. Every barrier you remove is a customer you keep.
Sources
- W3C Web Accessibility Initiative — WCAG Overview: https://www.w3.org/WAI/standards-guidelines/wcag/
- WebAIM — The WebAIM Million (annual accessibility analysis): https://webaim.org/projects/million/
- U.S. Department of Justice — Web Accessibility and the ADA: https://www.ada.gov/resources/web-accessibility/
- Google — Web Vitals: https://web.dev/articles/vitals
Check your website for free
Get an instant score and your top 3 critical issues in under 60 seconds.
Get Your Free Audit →