Five Accessibility Mistakes Service Business Websites Make (That Are Easy to Miss)
Five quiet accessibility failures that look fine in a visual review but block users from completing tasks: form labels, focus indicators, contrast, link text, and alt text. Automated scans catch some of them, and none of the five is fully settled by a scan.
Updated with additional research.
The accessibility failures that make headlines are dramatic: a federal lawsuit, a cease-and-desist, a story about a major retailer’s inaccessible checkout. Those failures happen. They are also not the typical accessibility picture for a small service business.
The typical picture is quieter. A website looks good, was built by a competent developer, has no glaring problems, and still blocks some users from tasks they came to do. Carelessness is rarely the cause. Accessibility needs a specific kind of attention that many web projects do not apply. The WebAIM Million 2026 analysis, an automated scan of 1,000,000 home pages, detected WCAG 2 failures on 95.9% of them.
Five failures show up often on service business websites and are easy to miss in a visual review. The guide to website accessibility for small businesses places them in the wider picture.
Missing or Misleading Form Labels
Forms are where most inquiries start on a service business site: the contact form, the booking form, the intake questionnaire. They are also where accessibility failures cost the most.
The failure pattern is a form field with placeholder text but no visible label. The field for “Email address” shows “[email protected]” inside the input box, with no persistent label outside it. Visually, this can look clean and modern.
Placeholder text disappears once typing starts, so the field then has no visible label. Placeholders are also not a dependable programmatic label, so a screen reader user filling out a multi-field form may have no reliable way to know what each field expects. The WebAIM Million 2026 analysis found that 51% of the 1,000,000 home pages had missing form input labels.
The fix is a visible label: a <label> element associated with its input through for and id attributes, or wrapped around the input. Placeholder text is supplementary.
Focus Indicators That Are Invisible
Keyboard users, who navigate with Tab, Shift+Tab, Enter, and arrow keys because they cannot use a mouse, rely on the focus indicator to know which element is selected. The indicator is typically a border or highlight around the focused element.
Some designs suppress the default browser focus indicator with outline: none in the CSS because the default ring looks inconsistent with the design. This fails WCAG Success Criterion 2.4.7, Focus Visible (Level AA), and it is a significant usability barrier.
A keyboard user on a site with no visible focus indicator can press Tab and move through the page but cannot tell where focus is. Finding a specific link, button, or form field means guessing and backtracking.
The fix does not require keeping the default ring. It requires a visible alternative: a high-contrast border, a background change, or a custom highlight that stands out against the surrounding content.
Low Contrast in Secondary Text
Low-contrast text was the most common failure in the WebAIM Million 2026 analysis, found on 83.9% of 1,000,000 home pages.
WCAG 2.2 requires a contrast ratio of 4.5:1 for normal text and 3:1 for large text, meaning 18 point, or 14 point bold. The requirement covers body copy, navigation text, labels, helper text, error messages, and placeholder text, not just headings.
The failure pattern is a lighter gray for secondary content such as captions, subheads, navigation items, and footer links. Gray text on a white background is a common combination to check.
The specific numbers matter. A ratio of 3.8:1 fails AA for normal text, though it would pass for large text. Contrast checking takes a tool, not a visual judgment. The WebAIM Contrast Checker or a browser accessibility inspector produces the exact ratio for any color pair.
Non-Descriptive Link Text
“Click here.” “Learn more.” “Read more.” “Get started.”
These phrases appear on many websites. Generic link text can fail WCAG Success Criterion 2.4.4, Link Purpose (In Context), when the surrounding context does not explain the destination. Screen readers can list all the links on a page, and a list reading “Click here (×4), Learn more (×6), Read more (×3)” says nothing about where the links go.
Descriptive link text names the destination or the action: “Read our accessibility services overview,” “Schedule a 15-minute introductory call,” “Download the accessibility audit checklist.” This helps screen reader users and clarifies the page for everyone else.
The fix is often only editing the link text. Links generated by templates, buttons, or CMS components may need a developer. A small site takes a few hours.
Images with Generic or Missing Alt Text
Alt text gives users who cannot see an image a text alternative, which screen readers read aloud in its place. In the WebAIM Million 2026 analysis, 53.1% of home pages had images missing alternative text.
The failure has two forms. The first is no alt attribute at all, which can cause a screen reader to announce the filename. The second is generic alt text such as “image.jpg” or “photo,” or the same alt text used for every image on the page.
Both fail WCAG Success Criterion 1.1.1 on informative images. The fix is alt text that describes the meaningful content or function of each image. For decorative images, which provide no information, the correct markup is an empty alt="", which tells the screen reader to skip the image. For informational images, the alt text should say what the image communicates, not what it depicts. “Bar chart showing a 40% increase in review volume after implementation” says more than “chart.”
Automated scans can detect a missing alt attribute. They cannot judge whether the text describes the image well. That part is judgment work, and it is the part that tends to go unfixed.
The Common Thread
None of these failures takes exceptional skill to create. They are easy to miss in a visual design review. Automated scans flag missing labels and many contrast failures, but they cannot judge whether alt text or link text is meaningful, and none of the five is fully settled by a scan.
Together, they describe a site that may look polished and convert well for visitors without assistive technology needs, while creating barriers for others.
If any of these patterns sound familiar on your site, a 15-minute conversation about COREaccess™ is a practical place to start building the picture.