If you run a small business, you have probably heard the phrase ADA compliance tossed around, usually followed by a scary story about a lawsuit. The good news? Making your website accessible is not as complicated (or expensive) as agencies want you to believe. You do not need to hire a specialist to cover the fundamentals.
This guide walks you through how to make a website ADA accessible, step by step, using plain English. By the end, you will know exactly what to fix, how to test it, and how to avoid the most common legal traps in 2026.
What Does ADA Accessible Actually Mean?
The Americans with Disabilities Act (ADA) requires businesses to provide equal access to people with disabilities. Since 2024, the Department of Justice has formally referenced the WCAG 2.1 Level AA standard as the technical benchmark for web accessibility, and most legal experts now recommend aiming for WCAG 2.2 Level AA to stay ahead of the curve.
In plain terms, your site needs to be usable by people who:
- Cannot see the screen and rely on screen readers
- Cannot use a mouse and navigate with a keyboard
- Have low vision or color blindness
- Have cognitive or motor difficulties
- Are deaf or hard of hearing
Why Small Businesses Should Care (Beyond Lawsuits)
Yes, ADA lawsuits against small business websites have kept climbing every year. But there is an upside most guides forget to mention:
- Bigger audience: Roughly 1 in 4 U.S. adults live with some form of disability.
- Better SEO: Google rewards clean HTML, alt text, and proper heading structure.
- Higher conversions: Clear contrast and readable text help every visitor, not just those with disabilities.
How to Make a Website ADA Accessible: 7 Practical Steps
1. Fix Your Color Contrast
Low-contrast text (light gray on white, for example) is the single most common accessibility failure. WCAG requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text.
How to check it: paste your text and background hex codes into a free tool like WebAIM Contrast Checker. If it fails, darken the text or lighten the background.
| Example | Ratio | Pass? |
|---|---|---|
| #777777 on #FFFFFF | 4.48:1 | Fails (barely) |
| #595959 on #FFFFFF | 7.0:1 | Passes AA and AAA |
| #FFFFFF on #F1B434 | 1.9:1 | Fails |
2. Write Meaningful Alt Text for Every Image
Alt text is what screen readers announce when they encounter an image. It also shows up if the image fails to load. tamu.edu makes the same point with more data.
Bad: alt="image1.jpg"
Better: alt="Woman in a wheelchair using a laptop at a coffee shop" Background reading: https://ada.jeffer.com.
Rules of thumb:
- Describe what the image means in context, not just what it shows
- Keep it under 125 characters
- For purely decorative images, use empty alt text:
alt="" - Never start with “Image of” or “Picture of” (the screen reader already knows)
3. Make Everything Work with a Keyboard
Many users navigate using only the Tab, Shift+Tab, Enter, and arrow keys. Try it yourself right now: put your mouse away and tab through your homepage.
Ask yourself:
- Can I reach every link, button, and form field?
- Can I see a visible focus indicator (a box or outline) as I tab?
- Can I open menus, close pop-ups, and submit forms without a mouse?
If your theme removes the focus outline with outline: none, put it back. This is one of the top reasons small business sites fail audits.
4. Use Proper Headings and Structure
Screen readers let users jump from heading to heading. If your page uses a single giant H1 followed by random bold text pretending to be headings, blind users are lost.
- One H1 per page (usually the page title)
- H2 for main sections, H3 for subsections, and so on
- Never skip levels (do not jump from H2 to H4)
- Do not use headings just to make text bigger
5. Add ARIA Labels Where Needed (But Don’t Overdo It)
ARIA (Accessible Rich Internet Applications) labels give extra context to screen readers when the HTML alone is not enough.
Common uses:
- Icon-only buttons:
<button aria-label="Close menu">✕</button> - Search inputs without visible labels:
<input type="search" aria-label="Search the site"> - Navigation regions:
<nav aria-label="Main navigation">
Warning: the first rule of ARIA is do not use ARIA if a native HTML element does the same job. A real <button> is always better than a <div role="button">.
6. Label Every Form Field
Every input needs a visible label tied to it with a for attribute:
<label for="email">Email address</label>
<input type="email" id="email" name="email">
Placeholder text alone is not a label. It disappears as soon as the user types and is often too light to read. ada.gov walks through the specifics.
7. Add Captions and Transcripts to Video and Audio
If you use video on your homepage or product pages:
- Add closed captions (YouTube auto-captions are a starting point, but review them)
- Provide a text transcript for podcasts and audio clips
- Never autoplay video with sound
Free Tools to Test Your Website
You do not need to buy expensive software to run a first audit. These free tools will catch 80% of issues:
| Tool | What It Does |
|---|---|
| WAVE (wave.webaim.org) | Visual browser scan for missing alt text, contrast, and heading issues |
| Lighthouse (built into Chrome DevTools) | Automated accessibility score with actionable fixes |
| axe DevTools | Free Chrome extension trusted by developers |
| NVDA (Windows) or VoiceOver (Mac) | Free screen readers to test your site the way blind users experience it |
What About Accessibility Overlays and Widgets?
You have probably seen ads for one-line-of-code “accessibility widgets” that promise instant compliance. Be careful. Multiple class-action lawsuits in the past two years have specifically targeted businesses that relied only on overlays. They can help, but they do not replace fixing the underlying code. It is worth seeing how custom-web-promotions.com handles it.
A Realistic Roadmap for Busy Business Owners
- Week 1: Run WAVE and Lighthouse on your top 5 pages. List every issue.
- Week 2: Fix alt text, contrast, and form labels (the easy wins).
- Week 3: Test keyboard navigation and repair focus states.
- Week 4: Add ARIA labels where needed, publish an accessibility statement, and set up a feedback email for users who spot issues.
- Ongoing: Re-test every time you launch new pages or redesign.
Final Thoughts
Making your website ADA accessible is not a one-time project, it is a habit. Start with the fundamentals in this guide, test with real tools, and document what you have done. That paper trail alone can protect you if a demand letter ever lands in your inbox.
If you would rather have a professional handle it, our team at Legionary Studio builds and audits accessible websites for small businesses every day. Reach out and we will point you in the right direction, even if you do not become a client.
Frequently Asked Questions
What makes a website ADA accessible?
A website is considered ADA accessible when it conforms to the WCAG 2.1 (or 2.2) Level AA standard, meaning it can be used effectively by people with visual, auditory, motor, and cognitive disabilities. Key ingredients include sufficient color contrast, alt text on images, keyboard navigation, labeled forms, and proper heading structure.
How much does it cost to make my website ADA compliant?
For a small business site of 5 to 20 pages, DIY fixes cost nothing but time. A professional audit and remediation typically runs between $1,500 and $8,000 depending on complexity. Compare that to the average ADA settlement, which often exceeds $20,000.
What happens if my website is not ADA compliant?
You risk demand letters and lawsuits under Title III of the ADA. Even small local businesses have been sued. Beyond legal risk, you are also excluding roughly a quarter of your potential customers.
Is ADA compliance mandatory for all websites?
The ADA applies to “places of public accommodation,” which courts have broadly interpreted to include most business websites. If you sell to the public, you should assume it applies to you.
Can I just install an accessibility widget and be done?
No. Widgets and overlays can supplement your efforts but do not fix the underlying code. Courts have consistently ruled that overlays alone are not enough to demonstrate compliance.
How often should I re-audit my website?
Run a quick automated scan every quarter and a full manual audit at least once a year, or any time you redesign or add major new features.