Website accessibility usually enters a service business owner's life as a demand letter: a law firm asserting that the site does not comply with the Americans with Disabilities Act and offering to settle. Whether or not that letter is ever coming, the fixes it describes are the same fixes that make a site work better for every visitor, and most of them are cheap.
Here is what accessibility means in practice for a contractor, cleaner, or clinic website, and what to do about it.
The legal picture in brief
Title III of the ADA covers places of public accommodation. The Department of Justice has taken the position that websites of businesses open to the public are covered, and courts have generally agreed, though the details vary by circuit. There is no federal regulation that names a technical standard for private business websites. In practice, the Web Content Accessibility Guidelines (WCAG) version 2.1 at the AA level are the reference nearly everyone uses, including the DOJ in its settlements.
This is not legal advice, and if you have received a letter you should talk to a lawyer. The point is that the standard to aim for is known, and it is not exotic.
What actually fails on service business sites
Having looked at a lot of these sites, the failures cluster.
Images without alt text. Every meaningful image needs a short text description. A photo of a technician installing a water heater gets alt text that says so. Decorative images get an empty alt attribute so screen readers skip them. This is also what tells Google what the image shows.
Low-contrast text. Light gray text on white, white text over a photo, thin fonts on colored backgrounds. WCAG AA specifies a minimum contrast ratio, and free checkers will test any two colors. Most brand palettes need one or two adjustments.
Forms without labels. A contact form where the field name is only shown as placeholder text inside the box, which disappears when you start typing, is unusable with a screen reader and hard for everyone. Every field needs a visible, associated label. Error messages need to say what is wrong, not just turn the box red. This overlaps entirely with good contact form design.
Buttons and links that say nothing. "Click here," "Learn more," "Read more" repeated ten times on a page. A screen reader user navigating by links hears ten identical links. "Book an AC tune-up" is better for them and better for search.
No keyboard navigation. Try tabbing through your site without a mouse. If you cannot reach the phone number, the form, and the menu, or if you cannot see where the focus is, the site fails for anyone who cannot use a mouse.
Heading structure that is decoration. Headings should describe the page's structure: one H1, H2s for sections, H3s within them. Sites built in page builders often use headings for font size, producing an outline that makes no sense. Screen readers navigate by headings. So do search engines.
Auto-playing video and carousels. Motion that cannot be paused is a WCAG failure and an annoyance. Sliders also do not convert, so removing them helps twice.
Chat widgets and popups that trap focus. A chat bubble or a discount popup that cannot be closed by keyboard, or that steals focus from the page, is a common failure introduced by third-party scripts rather than the site itself.
What to do, in order
Run an automated check. Free tools (browser extensions, Google's Lighthouse in Chrome DevTools) flag the mechanical failures: missing alt text, contrast, missing labels, missing language attribute. Automated checks catch a minority of real issues, but they catch the ones a demand letter will cite.
Fix the forms and the phone number first. These are the paths to revenue. If a screen reader user cannot call you or submit the form, the site has failed at its only job.
Fix contrast and alt text. Usually a day of work on a typical service site.
Test with a keyboard. Tab through every page. Fix anything unreachable.
Then review the third-party scripts. Chat, booking widgets, review widgets, popups. Each one is either accessible or it is not, and the vendor should be able to tell you.
Add an accessibility statement. A short page saying the business is committed to accessibility, which standard you aim for, and how to contact you if something does not work. It is not a legal shield, but it signals good faith and gives a real user a way to reach you before a lawyer does.
What about overlay widgets?
There is a category of product that promises one line of code to make any site compliant. They add a toolbar for adjusting contrast and font size. They do not fix underlying failures, several have been named in accessibility lawsuits themselves, and the accessibility community broadly advises against them. Fix the site.
The upside
Every one of these fixes improves the site for people who are not disabled: clearer forms, readable text, sensible headings, descriptive links, no auto-play. Several are direct search signals. An accessibility pass is one of the few website projects that improves legal exposure, conversion, and SEO in the same afternoon, which is why it is part of every site we build rather than an add-on.
Ask us about it on a call if your site has never had a pass.
Frequently asked questions
Does my small business really need to worry about this?
The legal exposure exists regardless of size. The practical exposure depends on the industry and the state. The usability benefit is universal.
Is a WordPress theme that says "accessibility ready" enough?
It is a start. The theme's own markup may be fine, and then the content, images, forms, and plugins added afterward break it. The standard applies to the finished site.
How do I check PDFs and documents?
Untagged PDFs are inaccessible. If you publish service agreements or price sheets as PDFs, provide the same information as a web page.
Who is responsible if my web developer built it wrong?
The business is the defendant. Contracts can allocate the cost, but the exposure is yours. Ask your developer what standard they build to and how they test.