Website accessibility for small business means making sure people with disabilities can use your site: read the text, understand the images, move through every page with a keyboard and submit your contact or booking form with a screen reader. The Department of Justice says the ADA applies to the goods and services businesses offer the public, and it points to WCAG, the Web Content Accessibility Guidelines, as the practical standard. For most small sites, fixing six common problems, testing your forms by hand and skipping the "one line of code" overlay widgets gets you most of the way.
This is not only a legal question. An inaccessible form is a form some customers cannot send, and every one of the fixes below also makes the site easier for everyone else to use on a phone, in sunlight or in a hurry.
What the ADA actually says about websites
There is no federal regulation that spells out website rules for private businesses yet. What exists is guidance. The Justice Department's Guidance on Web Accessibility and the ADA states that "the ADA's requirements apply to all the goods, services, privileges, or activities offered by public accommodations," and that businesses "have flexibility in how they comply," but "must comply with the ADA's requirements." The same page says existing technical standards, including WCAG and the federal Section 508 Standards, "provide helpful guidance."
You may have read about an April 2026 deadline. That rule covers state and local governments, not private companies. It uses WCAG 2.1 Level AA, and in April 2026 the Justice Department pushed its compliance dates back to April 26, 2027 for large public entities and April 26, 2028 for smaller ones; the notice says it does not address the Title III rules that cover businesses (Federal Register). Even so, WCAG 2.1 AA is the target most lawyers, auditors and web teams now aim for, so it is the sensible benchmark for a business site too.
The newest version is WCAG 2.2, which became a W3C Recommendation in October 2023 and added nine success criteria, including a minimum size for tap targets and rules for accessible logins (W3C). If you are building a new site, build to 2.2 AA; it includes everything in 2.1.
This is general information, not legal advice. If you have received a demand letter, talk to an attorney before you change or reply to anything.
The six problems on most websites
Every year WebAIM runs automated accessibility tests on the home pages of the top one million websites. The 2026 WebAIM Million report found detectable WCAG failures on 95.9% of home pages, with an average of 56.1 errors per page. Almost all of them fall into six types:
| Problem | Share of home pages | What it means for a visitor |
|---|---|---|
| Low contrast text | 83.9% | Light gray text on white is hard to read with low vision, on a dim phone or outdoors |
| Missing image alt text | 53.1% | A screen reader announces "image" or a file name instead of what the photo shows |
| Missing form labels | 51% | A blind visitor hears "edit text" and has no idea which box is name, phone or address |
| Empty links | 46.3% | Icon-only links, like a social logo, are announced with no destination |
| Empty buttons | 30.6% | A menu or submit button with no text label cannot be identified |
| Missing page language | 13.5% | Screen readers may pronounce the page with the wrong language rules |
WebAIM is clear that automated tests do not catch everything: "Absence of detected errors does not indicate that a page is accessible or conformant." The good news for a small business is that these six are cheap to fix, and fixing them removes most of what a scanning tool or a demand-letter firm would flag first.
Why accessibility overlays are not the answer
Overlays are the widgets that promise to make your site compliant by pasting one script into the header. They usually add a floating icon with options like bigger text or high contrast, and some claim AI repairs the page automatically.
The Federal Trade Commission tested that promise. In April 2025 it finalized an order requiring accessiBe, one of the best-known overlay vendors, to pay $1 million. The FTC alleged the company's claim that its widget "can make any website compliant" with WCAG was "false, misleading, or unsubstantiated," and the order bars it from making that claim without evidence (FTC).
Our view: an overlay can sit on top of a site, but it cannot rewrite a form that was built without labels, describe a photo it does not understand or fix a menu that traps keyboard users. Spend the same budget fixing the underlying code once.
A fix-first checklist for a small business site
Work through these in order. The first five can usually be done in an afternoon on most website builders.
- Raise text contrast. Body text should meet a 4.5 to 1 contrast ratio against its background under WCAG AA (W3C quick reference). Check your brand colors with a free contrast checker and darken light gray text, text on photos and pale buttons.
- Write alt text for meaningful images. Describe what matters in one short sentence: "Technician installing a heat pump in a Bridgewater basement." Decorative images get empty alt text so screen readers skip them.
- Label every form field. Use a visible label above each field, not just gray placeholder text that disappears when someone types. Error messages should say what is wrong in words, not only with a red border. Our guide to website contact form best practices covers the rest of a good form.
- Name your icon links and buttons. Phone, email, social and menu icons need a text label that screen readers can announce, such as "Call us" or "Open menu."
- Set the page language in the site settings or template so the page declares English.
- Test with only a keyboard. Unplug the mouse and press Tab through your home page, a service page and your contact form. You should always see where you are, reach every link and button, open the menu, close any popup with Escape and submit the form.
- Check headings. Each page should have one main heading and logical section headings in order. Screen reader users jump between headings the way sighted visitors skim.
- Caption your videos and make sure nothing autoplays with sound.
- Zoom to 200%. Text should reflow without overlapping or forcing sideways scrolling, and tap targets on mobile should be large enough to hit.
- Check third-party pieces. Booking widgets, chat bubbles, review carousels and payment forms are often the least accessible parts of a site. Test them like the rest and ask vendors for their accessibility documentation.
- Publish an accessibility statement with a phone number and email so anyone who hits a barrier can still reach you and get help.
Where AI helps and where it does not
AI tools are useful for parts of this work. A vision model can draft alt text for a gallery of 200 job photos in minutes, and an AI assistant can rewrite vague link text like "click here" into something descriptive. Automated scanners, including the accessibility audit built into Chrome's Lighthouse, will catch most contrast, label and empty-link problems.
What AI cannot do is judge whether the experience works. Someone still needs to review drafted alt text for accuracy, tab through the booking flow and confirm a screen reader can complete the form. When we build an AI-powered website, accessibility checks are part of the build, the same way we treat website speed: designed in from the start rather than patched later.
How accessibility affects leads and search
Most of these fixes overlap with what makes a site convert and rank. Clear labels and readable contrast reduce form abandonment for every visitor. Descriptive alt text and a clean heading structure help search engines understand your pages. Larger tap targets cut mis-taps on phones. If your site gets traffic but few form submissions, an accessibility pass is a reasonable place to look alongside the steps in our guide to small business website conversion rate.
A note for New Jersey businesses
Many New Jersey service businesses, from HVAC and plumbing to dental and law offices, serve a large share of older customers who use larger text, screen magnifiers or voice tools. For them, a hard-to-read estimate form is simply a reason to call the next company. If you serve the public in New Jersey, treat WCAG 2.1 AA as your working standard, keep a dated record of what you tested and fixed, and ask your attorney how state law applies to your situation.
Frequently asked questions
Does a small business website have to be ADA compliant? The Justice Department says the ADA applies to the goods and services businesses offer the public and points to WCAG as helpful guidance, but there is no federal website regulation for private businesses yet. Most businesses treat WCAG 2.1 AA as the practical target. Ask an attorney about your specific risk.
Will an accessibility widget or overlay make my site compliant? Not on its own. In 2025 the FTC finalized a $1 million order against an overlay vendor over claims that its tool could make any site WCAG compliant. Fixing the site's actual code, content and forms is the reliable route.
How much does it cost to make a small business website accessible? It depends on the size of the site and how it was built. A simple brochure site often needs only contrast, alt text, form label and keyboard fixes, while custom booking flows and many third-party widgets take more work. An audit first tells you what you are actually dealing with.
Should I follow WCAG 2.1 or WCAG 2.2? WCAG 2.1 AA is the level referenced in the Justice Department's government rule and in most legal discussions. WCAG 2.2 includes everything in 2.1 plus nine newer criteria, so a new site built to 2.2 AA covers both.
Get a clear answer on your site
Red Ridge AI builds and maintains websites for New Jersey businesses with accessibility, speed and lead capture designed in. If you want to know where your current site stands, our one-time website audits on the audits page come with a written fix list, or you can book a call and we will walk through your home page and contact form together. You can also see what ongoing website care includes on our pricing page.