All guides
Education 21 min read Updated

Accessibility: what we found on 100 small-business sites

Readable text, useful labels and controls that work without a mouse help more people use your website. We reviewed 100 small-business sites. Here is what the checks found and what to test yourself.

We looked at 100 small-business websites
20.7%

of the things we looked at got in some visitor's way.

Maybe the text is too faint to read. Maybe the booking form confuses their screen reader. Maybe a flashing animation makes them feel sick. They do not email you to complain. They just leave, and you never know they were there.

People browse in different ways: with a keyboard, a screen reader, larger text or reduced motion. Accessibility work helps them reach the same information and complete the same tasks. Start with the actual page and the controls a customer needs.

Here is the big picture. Across everything we looked at on these sites:

79.7%
mean site pass rate among evaluated checks (median 83.3%)
41%
of sites had three or more recorded failures
10%
of sites had no recorded failures; unchecked results are not passes

253 of 1,221 evaluated accessibility checks failed, or 20.7%. Forty-one sites had three or more recorded failures and ten had none. “No recorded failures” means this checklist found none among evaluated results; it is not a statement that the whole site meets an accessibility standard.

Three reasons to care, and none of them are abstract:

  • Real customers. A barrier can stop someone reading, asking a question or buying.
  • Requirements depend on context. Check the rules that apply to your service and location. This guide is not a legal assessment.
  • Clearer structure. Clear structure and labels make the page easier to understand. That is useful work even without a promised search or sales result.

Some fixes you can do yourself. A few are technical and best handed to whoever built your site. We will be clear about which is which.

How we did this

The findings come from a June 25, 2026 batch of 103 audit records for 100 distinct website addresses. We use the latest record for each address, against checklist version 2026-06-24l. Percentages use passes plus failures; not-applicable and unchecked results do not count as passes. These checks identify issues to investigate, not a full manual assessment. The sample does not establish how all businesses perform. Diagrams below illustrate the issues.


Reading, color, and motion: can people take your page in?

This group covers the most basic thing a website does: show information so a human can actually take it in. If the words are too faint, the captions are missing, or the motion is overwhelming, the content might as well not be there.

Color contrast people can actually read

49 of 90 evaluated sites failed the contrast check, about 54%. Ten were unchecked. Look for text that is hard to distinguish from its actual background, including button labels and words placed over photos.

See the counts behind the findings

Failed / evaluated means failures divided by passes plus failures. On a small screen, scroll the table sideways to see all columns.

June 25, 2026 audit counts
CheckFailed / evaluatedFailure rateNot applicableUnchecked
Color contrast meets WCAG AA49 / 9054.4%010
Site is navigable by keyboard alone18 / 9020.0%010
Links are descriptive — not just 'click here'1 / 971.0%30
Forms have proper labels, not just placeholder text12 / 4924.5%510
Page has a descriptive title0 / 900.0%010
Page language is declared (html lang)4 / 904.4%010
Images and icons have accessible text alternatives20 / 9022.2%010
Buttons and links have accessible names47 / 9052.2%010
Form fields have programmatic labels4 / 904.4%010
ARIA roles and attributes are valid8 / 908.9%010
Lists are structured correctly8 / 908.9%010
Page can be zoomed (viewport scaling not disabled)12 / 9013.3%010
No other automated WCAG A/AA violations11 / 9012.2%010
Heavy animation respects prefers-reduced-motion34 / 5265.4%480
Embedded video has captions21 / 2391.3%770
Form option groups use fieldset/legend4 / 1040.0%900
Hard to read

Call us today: (555) 010-2024

Pale gray on white, vanishes in daylight
Easy to read

Call us today: (555) 010-2024

Dark text, clear for everyone
Same phone number. One you can read at a glance; the other your most important customers cannot.

A contrast result needs the actual foreground and background colors, plus the text size and weight. Check the important text in its real state, including hover, focus and validation messages. Do not assume all gray text fails or all dark text passes.

Why it matters: your most important words are often the ones people cannot read. Your phone number. Your hours. Your prices. Your main button. Faint text there quietly costs you calls and sales.

How to fix it: Adjust text and background colors, then measure the combination with a contrast checker. If words sit over a photo, use a stable background behind them or move them. In Frontpage, ask for that change and review the result. A generated theme still needs checking.

Captions on your videos

21 of 23 evaluated sites failed the captions check, about 91%. Seventy-seven were not applicable. This is a finding about the checked videos, not a percentage of all 100 businesses.

Sites with video that left it uncaptioned91%
Of the 23 sites that used video, all but two had no captions at all.

Why it matters: if your video explains your service or your offer, an uncaptioned version only reaches the people who turn the sound on. Not every viewer will hear it. Captions also give search engines text to read, which helps you get found.

How to fix it: on YouTube, turn on auto-generated captions, then edit them so names and prices are correct, because auto-captions get details wrong. For video on your own site, ask whoever manages it to add a caption file (a small text file, usually ending in ".vtt," that holds the words and their timing). And if a video does not really need to be a video, a short written version works for everyone instantly.

Heavy animation that respects "reduce motion"

34 of 52 evaluated sites failed the reduced-motion check, about 65%. Forty-eight were not applicable. A visitor who asks the device for less motion should not have to sit through large sweeping effects to read your page.

Ignores "reduce motion"

Everything slides, zooms, and auto-plays

Big parallax and autoplay run even for visitors who asked for calm
Respects "reduce motion"

The same page quiets down automatically

No dizziness, no nausea, no one driven off
34 of 52 evaluated sites failed the reduced-motion check. Review the page with the device’s reduced-motion preference enabled.

Why it matters: a visitor who feels sick on your homepage leaves. They will not push through nausea to read your menu. Large sweeping animations, parallax scrolling (where the background slides at a different speed from the foreground), and auto-playing motion are the usual culprits.

How to fix it: this one is mostly technical, so hand it over. Ask whoever built the site to respect the "prefers-reduced-motion" setting, which automatically reduces or removes big animations for visitors who have asked for calmer pages. It is a small, well-known piece of code. In the meantime, they can dial back anything that moves the moment the page loads.

Free site rebuild

See what your site needs

Submit your website URL and we will rebuild your site for free within 48 hours, then reach out when it is ready.

Rebuild my site free

Buttons, links, and labels: can people tell what things are?

This group is about meaning. A button that says nothing. An image with no description. A form field with no label. To a person using a screen reader (software that reads the page aloud for people who cannot see it), these are blank spaces. The page can look fine and still be useless by ear.

Buttons and links that announce themselves

47 of 90 evaluated sites failed the accessible-name check, about 52%. Ten were unchecked. An icon-only button needs a name that explains its action to assistive technology; a visible word next to the icon often helps everyone.

What a screen reader hears
⌕ ▢ ≡
"button… button… button." No idea what any of them do.
What a screen reader hears
"Search. Cart, 2 items. Open menu."
SearchCart (2)Menu
Same three icons. One set is silent; the other tells the visitor exactly where each one leads.

Why it matters: your "Call now," "Book," "Add to cart," and "Send" controls are exactly where you make money. If a blind or low-vision customer reaches one and hears nothing useful, that is a lost sale at the finish line.

How to fix it: Give each control a useful name. For a search icon, that might be an accessible label of “Search.” Use visible text when it fits. Ask Frontpage to label a named control, then inspect or test it rather than assuming the label is present.

Images and icons with text alternatives

20 of 90 evaluated sites failed the text-alternative check, about 22%. Ten were unchecked. A meaningful image needs an appropriate text alternative; a purely decorative image should not add distracting narration.

What a screen reader hears
🖼 🖼 🖼
"image… image… image." No idea what any of them show.
What a screen reader hears
"Slice of pepperoni pizza on a wooden board."
Described aloudFound by Google
An informative photo needs a useful text alternative. Describe what matters in context; decorative images can use empty alt text.

Why it matters: if a photo carries information (your dish, your finished work, a map of how to find you), the people who most need that description are the ones who cannot get it. Alt text gives people who cannot see the image its useful meaning.

How to fix it: for every image that means something, write one short, plain sentence describing what it shows, for example "Slice of pepperoni pizza on a wooden board." Most builders have an "alt text" box where you upload the image. For purely decorative images, mark them as decorative or leave the alt text empty on purpose, so the screen reader skips them.

Forms with real labels, not just gray placeholder text

12 of 49 evaluated sites failed the visible-form-label check, about 24%. Fifty-one were not applicable. Placeholder text disappears as the visitor types, so it should not carry the only explanation of what a field needs.

Placeholder as the only label
Phone number
Vanishes the moment you start typing
A real, lasting label
Phone number
555 012 3456
The label stays put for everyone
24% of sites with a form leaned on gray hint text instead of a label, so the reminder vanishes the second someone clicks in.

Why it matters: your contact and booking forms are how leads reach you. If a customer forgets which box was for their phone number, or a screen reader cannot announce the field at all, they abandon the form and you never learn they tried. That gray placeholder text usually fails the contrast test too, so it is a double problem.

How to fix it: Give the field a visible label and connect it in the markup. Keep placeholder text for an optional example. Check labels in the actual form, including after a validation error.

Illustrative label markup

<label for="contact-email">Email address</label>
<input id="contact-email" name="email" type="email" autocomplete="email">

The visible label stays when you type. Matching for and id connects it to the field. This snippet shows the association; it is not a deployed form. See the W3C form-label guidance.

Form fields with programmatic labels

4 of 90 evaluated sites failed the programmatic-label check, about 4%. Ten were unchecked. This is a separate automated rule from the visible-label check above, so the denominators differ. A label beside a field still needs an association that software can read.

Why it matters: without that connection, a screen reader user hears an unlabeled box and has to guess. On a checkout or booking form, guessing means errors and abandoned orders.

How to fix it: hand whoever built the site the notes above and ask them to connect each label to its field in the code (commonly by matching a "for" attribute to the field's id).

Form option groups with proper grouping

4 of 10 evaluated sites failed the grouped-options check, or 40%. Ninety were not applicable. A fieldset and legend can give related options a shared question, such as “Which service do you need?”

What a screen reader reads
"Haircut. Color. Beard trim."
Three loose options, with no idea what they belong to.
What a screen reader reads
"Pick a service: haircut, color, beard trim."
Grouped under a heading
40% of sites with grouped options did not bundle them, so the customer cannot tell what they are choosing.

Why it matters: without the grouping, a screen reader reads off a string of loose options with no idea what they belong to, so the customer cannot tell what they are choosing.

How to fix it: ask whoever built the form to wrap each set of related radio buttons or checkboxes in a fieldset with a legend that states the question.


The page's structure and behavior: can people move through it?

This last group is about getting around the page and the structure underneath it. Many of these are technical and best handed to your developer. But several were near-perfect across the sites we looked at.

Could not be used by keyboard alone20%
Blocked pinch-zoom on phones13%
Other smaller automated issues12%
Broken behind-the-scenes labels (ARIA)9%
Lists not built correctly9%
Page language not declared4%
Vague link wording like "click here"1%
This last group fared better than the rest. Keyboard access was the biggest gap at 20%, and most of these are quick, mostly technical fixes for whoever built your site.

Navigable by keyboard alone

18 of 90 evaluated sites failed the keyboard check, or 20%. Ten were unchecked. Test whether you can reach, operate and leave important controls without a mouse. An automated result cannot establish every keyboard interaction.

Jumbled tab order
3 · Logo1 · Book4 · Menu2 · Footer
Tab leaps around the page
Logical tab order
1 · Logo2 · Menu3 · Book4 · Footer
Tab moves top to bottom
18 of 90 evaluated sites failed the keyboard check. Try the important controls without a mouse and check that focus stays visible.

Why it matters: if pressing Tab jumps around in a jumbled order, or a customer cannot reach your "Book" button without a mouse, those visitors cannot finish the task. Keyboard access is also the foundation most screen readers rely on, so breaking it breaks more than one group at once.

How to fix it: test it yourself in two minutes. Open your site, put the mouse away, and press Tab over and over. The highlight should move through links and buttons in a sensible top-to-bottom order. If it leaps around, hand the page to whoever built your site and ask them to fix the tab order so it follows the page from top to bottom.

The page can be zoomed

12 of 90 evaluated sites failed the zoom-setting check, about 13%. Ten were unchecked. Check that the page does not deliberately disable scaling, then try the content at increased zoom as a separate manual task.

Why it matters: many people, especially older customers and anyone reading fine print like your hours or address, rely on pinch-to-zoom. Blocking it tells a large, loyal group that your site is not for them, on the device most of your traffic uses.

How to fix it: ask whoever built the site to stop disabling zoom, by removing the settings that lock the scale or set "user-scalable" to no. It is a one-line change, and there is almost never a good reason to keep it.

No other automated WCAG violations

11 of 90 evaluated sites had other recorded automated accessibility violations, about 12%. Ten were unchecked. Read the actual findings before deciding severity. A problem outside the named groups is not necessarily minor.

Why it matters: these leftover issues are exactly the small barriers a customer cannot name but can feel, and they tend to be the cheapest to fix.

How to fix it: give your builder the specific notes (the count of elements is the clue) and ask them to resolve each flagged item. Because these come straight from an automated checker, the fixes are usually quick.

Valid ARIA roles and attributes

9% of sites had broken behind-the-scenes labels. Fewer than one in ten, which is encouraging. These are extra labels developers add to help screen readers understand custom parts, like a slider or a pop-up menu, that are not ordinary buttons or links. Used correctly they help. With a mistake or a typo, they confuse the screen reader instead.

Why it matters: a broken label here is worse than no label at all. It can take a button that would have worked fine and make it announce nonsense, leaving the customer stuck.

How to fix it: this is purely technical. Ask your developer to check these labels and either fix or remove the broken ones.

Lists structured correctly

9% of sites had lists that were not built correctly. A small group had lists that were technically broken in the page's code. When a list (your services, your menu, your features) is built correctly, a screen reader says "list of 5 items" and lets the visitor move through them cleanly. When it is broken, that structure falls apart.

Why it matters: lists are how you present the things people came to see. If the structure is broken, a screen reader user loses the "5 items" framing and the content gets harder to follow.

How to fix it: this is a tidy-up for your builder. Share the notes and ask them to correct the list markup so each list is properly formed.

Page language is declared

4 of 90 evaluated sites failed the page-language check, about 4%. Ten were unchecked. Declare the actual language of the page so assistive technology can choose an appropriate reading voice.

Why it matters: without the language declared, a screen reader may mispronounce your whole page. It also gives search engines a clearer signal about who your content is for.

How to fix it: this is a one-time, one-line fix for whoever built the site: set the page's language attribute (for example, "lang" set to "en" for English). Set it once and it covers the whole page.

Links that describe where they go

1 of 97 evaluated sites failed the descriptive-link-text check, about 1%. Three were not applicable. Link text such as “View our menu” gives more context than a page full of identical “Click here” links.

Vague wording
click here read more here
A link list reads "click here, read more, here" and says nothing
Names its destination
View our menu Book an appointment Read our story
Every link says exactly where it goes
Just one site fell short here, but it is one of the easiest wins: make the meaningful words themselves the link.

Why it matters: clear link wording helps screen reader users navigate, helps everyone scan your page faster, and gives search engines useful context. It is one of the easiest wins in this report.

How to fix it: rewrite vague links to name their destination. "Click here to book" becomes "Book an appointment," and "Read more" becomes "Read our story." Make the meaningful words themselves the link.

A win worth celebrating: descriptive page titles

All 90 evaluated sites passed the descriptive-title check. Ten were unchecked. That is a good finding for the evaluated group. Check that a person opening your page can tell which page it is from the browser title.

100%
of the 90 evaluated sites passed the descriptive-title check. Ten sites were unchecked. Keep checking titles when you add pages.

Try the main task without a mouse

  1. Use Tab and Shift+Tab to move through links, buttons and fields. Check that focus stays visible.
  2. Open the menu with the keyboard. Check that you can use and leave it without getting stuck.
  3. Increase browser zoom to 200%. Check that text remains readable and useful controls remain reachable.
  4. Try the form’s labels, instructions and error messages. Check its success state with a test submission.
  5. Enable the device’s reduced-motion preference and review large animations.

These are starting checks. W3C explains the limits of a first review in Easy Checks. A complete assessment needs more than an automated pass.

What to fix first

Start with barriers to the main task, then use these evaluated failure rates to guide the remaining checks:

Caption your videos91%
Add a calmer "reduced motion" option65%
Fix color contrast54%
Give buttons and links real names52%
Put real labels on form fields24%
Add alt text to meaningful images22%
Make the site work with a keyboard alone20%
Stop blocking zoom on phones13%
Rounded failure rates among evaluated sites. Denominators differ: contrast failed on 49 of 90; captions on 21 of 23. Use the full counts above and your own task checks to choose a priority.
  1. Fix color contrast, 49 of 90 evaluated sites failed this check (54%).
  2. Caption your videos, 21 of 23 evaluated sites failed this check (91%).
  3. Give your buttons and links real names, 47 of 90 evaluated sites failed (52%).
  4. Add a calmer "reduced motion" option for heavy animation, 34 of 52 evaluated sites failed (65%).
  5. Add alt text to meaningful images, 20 of 90 evaluated sites failed (22%).
  6. Put real labels on your form fields, 12 of 49 evaluated sites failed (24%).
  7. Make the site work with a keyboard alone, 18 of 90 evaluated sites failed (20%).
  8. Stop blocking zoom on phones, 12 of 90 evaluated sites failed (13%).

After those, mop up the smaller, mostly technical items: the other small accessibility issues (12%), properly connected form labels (4%), grouped form options (40% of sites with grouped options), behind-the-scenes labels (9%), list structure (9%), the page language setting (4%), and the lone vague-link issue (1%). Hand the technical ones to whoever built your site. Most are quick.

Keep improving

Build and check your page

Ask Frontpage for a specific accessibility fix, then test the result. Keep labels, contrast, keyboard behavior and motion settings on the review list when you add a form or widget. This is ongoing work, not a compliance certificate.

Start building free

Why this is worth your time

Start with a task: read the service details, open the menu, complete the contact form. Use a keyboard and increased zoom, then check any barriers the audit flagged. Some changes are small; others need the person who built the feature.

The aim is a page more people can use. Accessibility requirements depend on the place and service involved; this guide does not determine which laws apply to your business. A passed automated check is not proof of legal compliance.

Keep a short list of the barriers you find, fix the ones that block important tasks, and retest. A free Website Audit can give you a starting list. For a fuller review, use manual testing and involve people who use assistive technology.

Free website audit

Get your score

Enter your website, email, and phone number and we'll run the audit for you. You'll get the full results, your score and exactly what to fix, accessibility included, delivered straight to your inbox.

Free audit · No credit card required


Historical findings from a limited checklist. Use them to choose checks for your own site, not as a certificate that a site is accessible.

Frequently asked questions

What does website accessibility mean for a small business?

It means people can use your site whether they browse with a keyboard, a screen reader, larger text, or reduced motion. Practical pieces include readable contrast, labeled form fields, alt text on meaningful images, captions on video, and buttons that work without a mouse.

What accessibility fixes can I do myself without a developer?

Raise text contrast, add descriptive alt text, label form fields clearly, write link text that names the destination, avoid relying on color alone, and add captions or transcripts for marketing video. Hand complex keyboard traps and ARIA issues to whoever built the site.

How do I know if my site is accessible enough?

Start with automated findings, then try the main tasks using a keyboard and increased zoom. Include assistive-technology testing where possible. W3C’s Easy Checks are a first review, not a complete assessment. Recheck after adding or changing features.

Build it while the idea is fresh.

Describe the site you want and watch Frontpage build it live, in front of you.