Getting your site accessible comes down to a few steps: know the standard, identify the problems, fix them in the right order, and keep it that way. On a well-built site, it's often less work than people expect. Here's the path, start to finish.
By Brent Kirby (opens in a new tab). Updated .
Know your standard
For almost every US rule, it's WCAG 2.1 Level AA: the ADA's rule for state and local government, HHS's Section 504 rule for healthcare, and what courts look to for businesses. Section 508 uses WCAG 2.0 AA, which 2.1 includes. Not sure which rule applies to you?
Identify the problems
Start with a quick check of your own, then test the whole thing: every type of page, every form, and the tasks people come to do, like booking a visit or paying a bill, with a keyboard, zoom, and screen readers. That's what an accessibility audit is for.
Fix what matters most first
Rank issues by how badly they block people. A checkout button a keyboard can't reach comes before a contrast tweak on a footer link. Many issues are small, like a missing label or a menu that won't open from the keyboard, and an experienced developer can often work through them faster than you'd expect.
Check what your vendors give you
The rules cover what you offer through other companies too: booking tools, payment pages, patient portals, themes, and plug-ins. Ask each vendor for its accessibility report (an ACR, sometimes called a VPAT), and test the parts your visitors use.
Publish an accessibility statement
Say what standard you're working toward, what you know still needs work, and how someone can reach you if they run into a problem. Then answer those messages quickly.
Retest, then keep it up
Once the changes are in, test again to confirm they hold, and keep a record of what was tested and when. After that, check new pages, forms, and plug-ins before they go live, since that's where new problems slip in.
Accessibility widgets, sometimes called overlays, promise compliance with one line of code. They try to patch your site in the browser after it loads, but they don't fix the underlying problems in its code, and whatever they miss still stops people.
Sites using them still get sued. And if the law requires your site to meet WCAG 2.1 AA, as it does for state and local governments and many healthcare providers, a widget alone is unlikely to get you there. Accessibility has to be built into the site itself, which is what the steps above get you.
Send us your website and we'll do a free preliminary audit so you know where you stand. You'll get an email with what we found and an estimate for a full audit, usually within 2 to 3 business days.
We'll only use your email and phone number to follow up when we're done.
Don't see yours?
Is there an ADA compliance certificate?
No. There's no official ADA certification, from the government or anyone else. What you can have is a record: an audit against WCAG 2.1 AA, the changes made, and a retest confirming they hold.
Can we do this ourselves?
Some of it. The quick checks and many of the changes are things an experienced developer can handle. It gets harder when you need to test whole tasks with screen readers and know how WCAG applies to your site, which is where an audit helps. Start with the quick checks.
Will a new website fix it?
Only if it's built and tested for accessibility. A redesign is a great time to get it right, but new themes and templates bring problems of their own. Test before launch, not after. If you're interested in a redesign, .

To know the road ahead, ask those coming back. We test with the same tools your users do.