WCAG accessibility in Alabama: audits, fixes, and sites built to pass
Some of your visitors navigate with a keyboard, a screen reader, or zoom set to 200%. We find what's blocking them, fix it in your theme and content, and help keep it fixed. We work on Drupal, WordPress, and other platforms, and we write our own accessibility tools. Based in Chelsea, we help organizations across Alabama, from Birmingham to Montgomery, with WCAG and ADA website compliance.
Why accessibility is real work for us
Accessibility isn't a side service for us. We've built our own open-source accessibility tool, dd_wcag, because the tools we had weren't good enough for daily development. It checks color pairs against WCAG and APCA, suggests the nearest passing color when a pair fails, and, as of version 0.5.0, generates a WCAG-checked color palette file that goes straight into a theme.
That says something about how we work: we fix accessibility where it starts, in the design system and the templates, so it doesn't come back with every new page.
Our WCAG accessibility services
Audits
Start with the free audit: an automated scan of two pages against WCAG 2.2, reviewed by a developer, with every issue given a priority level. When you need the full picture, our paid audit runs through professional third-party tools such as Level Access, Deque, or UsableNet. It includes full-site automated scanning, manual user testing (including screen reader testing), full audit reports, and a progress dashboard so you can track fixes over time. Paid audits are quoted per site.
Remediation
We fix the problems we find. That usually means:
- Templates and components: headings, landmarks, form labels, focus states, and keyboard traps.
- Color and type: contrast fixes that still look like your brand.
- Content patterns: alt text guidance, link wording, and tables that make sense to a screen reader.
- Third-party pieces: embeds, forms, and widgets that fail, and what you can do about them.
Need PDFs or other documents fixed too? We can take those on when you request it.
Accessible builds
On new Drupal and WordPress sites, accessibility is part of the build, not a separate phase. Components are tested as we make them, so editors can't easily publish something inaccessible by accident.
Keeping it accessible
A site that passes today can fail next month after a new carousel or a vendor's updated chat widget. Periodic accessibility re-checks using professional third-party tools are available as a care plan add-on.
ADA and Title II deadlines
For state and local governments, the DOJ's ADA Title II rule requires web content and mobile apps to meet WCAG 2.1 Level AA. Entities with 50,000 or more people must comply by April 26, 2027. Smaller entities and special districts have until April 26, 2028. The free audit page has the full breakdown and source.
Businesses, non-profits, and healthcare organizations have their own exposure under other parts of the ADA and federal health rules, and demand letters don't wait for a deadline. WCAG 2.1 AA is the practical target for nearly everyone, and we aim for 2.2 when we build.
General information, not legal advice. For compliance questions specific to your organization, talk to an attorney.
Case study: accessibility built into a healthcare rebuild. A regional healthcare provider needed one site that worked for everyone it serves, from patients and families to community members and donors, including people with disabilities. We led all of the accessibility work and made it part of the rebuild from the start, not a fix at the end, so the new Drupal site was built to accessibility standards on phones and desktops alike. We handled the development too, and the migration ran with zero downtime. After launch, the site saw about 20% more traffic and about 40% more time on site. Read the full case study
FAQ
What's the difference between WCAG and the ADA?
The ADA is the law. WCAG (Web Content Accessibility Guidelines) is the technical standard that spells out what "accessible" means for a website. The Title II rule for governments names WCAG 2.1 Level AA directly.
Should we target WCAG 2.1 or 2.2?
Our default is 2.1 AA, because that's what the Title II rule names, but we always aim for 2.2. It adds criteria for things like focus visibility and target size, and building to it now costs little extra. Our free audit already tests against 2.2.
Can an overlay or accessibility widget fix our site?
We don't recommend them. A script laid over the page doesn't fix the underlying code, and many screen reader users find overlays get in the way. Real fixes happen in the theme and content.
Do you test with screen readers?
The free audit is an automated scan, so no. Our paid audit does: it runs through professional tools such as Level Access and includes manual user testing with screen readers, along with full-site automated scanning, full audit reports, and a progress dashboard. It's quoted per site.
Can you fix a site you didn't build?
Yes. What we test is the page your visitors actually receive, so the platform matters less than you might think. Deeper fixes go fastest on Drupal and WordPress, where we do most of our work.
How long does remediation take, and how is it priced?
It depends on how many templates and how much content are involved. We price fixes by the level of effort and the type of work, and the audit gives us what we need to give you a realistic scope, timeline, and estimate.
Find out where you stand
The fastest first step is the free WCAG audit: you'll get a report within 48 business hours. If you already know you need help, tell us about your site.
Related: Pantheon hosting & DevOps · API integrations · Care plans