Website accessibility for small business: what to build in, and what the law actually says

You are partway through commissioning a website or a rebrand, and someone drops the word “accessibility.” Maybe they say “ADA compliance.” Maybe they mention a lawsuit a friend’s business got hit with. Suddenly a design project feels like a legal risk. Worse, most of the advice you find online is either written for developers or written to sell you something.

Here is the calmer version. More than 1 in 4 US adults lives with a disability, according to the CDC. So accessibility is not a niche concern. It is a big share of your customers. Getting it right is mostly about decisions you make early, in design and copy, not obscure code you will never see. This piece gives you a plain-English map. You will learn what accessibility actually means, what the law truly requires of a business your size, and what to build in from the start so you are not paying to fix it later.

This is general information, not legal advice. Accessibility law depends on your situation and where you operate. For advice about your specific business, talk to a qualified attorney.

The short version

• Accessibility means more people can actually use your site, including people who navigate by keyboard, screen reader, or captions.
• The ADA applies to your business. Still, it does not force one specific technical checklist on private companies.
• WCAG (the Web Content Accessibility Guidelines) 2.1 or 2.2 at Level AA is the practical standard to aim for. No federal rule mandates it for private business, but it is the benchmark that matters in practice.
• The 2027 government “deadline” you may have heard about applies to state and local governments, not to you.
• Most of what matters is decided in design and content choices, so you have more control than you think.
• A companion checklist you can hand to your designer is on the way.

What accessibility actually means, in plain English

Web accessibility means your site works for people with a range of abilities. Think of someone with low vision who enlarges text. Or someone who cannot use a mouse and tabs through with a keyboard. Or someone who is deaf and needs captions. It also covers temporary limits, like a broken arm or bright sunlight on a phone screen.

The guidelines boil down to four plain ideas. People need to perceive your content, operate your site, understand what is going on, and rely on it working with assistive technology. In other words, can your customers see it, use it, follow it, and reach it with the tools they already use? That is the whole game. Better still, most of it is common sense once someone points it out.

What the law actually says (and what it doesn’t)

This is where the noise gets loudest, so let’s be precise. The rules for government websites and private-business websites are genuinely different. Yet a lot of online advice blurs the two.

The ADA applies to your business

If your business is open to the public, the Americans with Disabilities Act (ADA) applies to what you offer online, not just your physical location. The Department of Justice has said this clearly. The goods and services you provide to the public, including online, need to be accessible to people with disabilities. So “there is no law” is simply wrong.

There is no single checklist the government forces on private businesses

Here is the part the scare pages skip. For private businesses, the DOJ has not adopted a specific technical standard. In its own web accessibility guidance, the department says businesses “have flexibility in how they comply.” It points to WCAG as “helpful guidance,” not a required specification. That means no federal rule says your company must hit WCAG 2.2 Level AA by a certain date. You still have the general duty to be accessible. However, you get to decide how you meet it.

The 2027 deadline you may have heard about is for governments, not you

There is a real, dated deadline floating around, and it is easy to misread. In 2024 the DOJ issued a binding rule requiring state and local governments to meet WCAG 2.1 Level AA. In April 2026 the DOJ extended those deadlines. Governments serving 50,000 or more people now have until April 26, 2027. Smaller government entities have until April 26, 2028. Notice the key word throughout: governments. If you run a private business, that specific deadline is not yours, even though plenty of vendor pages imply otherwise.

Why WCAG AA is still the number to aim for

So if nothing is mandated, why bother? Because the risk is real even without a codified standard. In practice, courts and settlement agreements have widely treated WCAG 2.0 and 2.1 Level AA as the yardstick for whether a private site is accessible. Lawsuits are common too. UsableNet, a firm that tracks these cases, counted nearly 5,000 digital-accessibility lawsuits in the US in 2025, and small and mid-sized businesses are frequent targets. Some states raise the stakes further. California’s Unruh Civil Rights Act, for example, can attach statutory damages to an accessibility failure. So building toward WCAG 2.1 or 2.2 Level AA is the smart, defensible goal. As a bonus, it serves more than a quarter of your customers at the same time.

Where accessibility shows up in your project

Accessibility is not a task you bolt on at the end. Instead, it runs through the whole project, and the choices split between you and the people you hire. Once you know which is which, you can brief the work clearly and catch gaps before they get expensive.

Some of it is yours. Your brand palette decides whether text has enough contrast to read, and your copy decides whether a page is clear and logically structured. Because these are design and content calls you already make, building them in costs nothing extra at the start. They only get pricey when you try to change colors or restructure pages after launch.

Other parts belong to the team you hire. Whether the site works with a keyboard alone, whether forms carry proper labels and helpful error messages, whether images include alt text: that is build work. You do not need to know how any of it is coded. Still, you do need to know it is not optional, so ask for it up front.

The rest is shared. Images, video captions, and link wording sit between you and your team, since you supply the intent and they wire it in. That is exactly why the cheapest version of accessibility is a conversation at the brief stage rather than a fix after a complaint.

You do not have to memorize any of this to hold the work to a standard. A companion checklist turns each of these areas into a plain-English list you can hand over or run yourself, and it is on the way.

What to ask the designer or developer you hire

The cheapest time to build accessibility in is before anyone starts, so put it in the brief. A few plain questions will tell you most of what you need to know.

Start by asking whether they build to WCAG 2.1 or 2.2 Level AA, and treat a blank stare as an answer. Next, find out how they test, because good teams use a mix of automated tools and real keyboard and screen-reader checks, not one plugin. Then ask to see an accessible site they have built, and settle who owns fixes if an issue turns up after launch. One red flag is worth naming here: be wary of anyone who promises instant compliance from a single overlay widget or line of code, because those bolt-ons do not actually make a site conform and have drawn lawsuits of their own. As we cover in what clients get wrong about AI and creative quality, the shortcut that sounds too easy usually is. For more on reading these signals, our guide on how to tell if the creative team you’re hiring has their systems in order walks through what good process looks like. And if you are starting from scratch, our take on startup website design covers where accessibility fits alongside everything else.

The bottom line

Accessibility built in from the brief is cheaper, calmer, and better than accessibility bolted on after a complaint. The law gives you flexibility. Your customers give you a reason. Best of all, most of the important choices happen in design and copy, where you already have a say. Aim for WCAG AA, hire people who take it seriously, and you turn a source of anxiety into a real competitive edge.

Building or rebuilding a site and want accessibility handled properly from day one? See how The Blue Mango works with clients. We match you with vetted creators, scope the work clearly, and build accessibility in from the brief, not after the fact.