ADA & WCAG Website Accessibility
Websites that work for people who use screen readers, keyboards, magnification or captions — audited by hand against WCAG 2.2, fixed in the code, and documented for anyone who asks.
- Standard
- WCAG 2.2 AA (2.1 AA for Title II)
- Method
- Automated plus manual, by hand
- Fixes
- Made in the code, not an overlay
- Deliverable
- Report, fixes, statement
Overview
An inaccessible website turns away customers you never knew you had — and increasingly, it turns up in a demand letter.
A meaningful share of your visitors use the web differently: a screen reader that speaks the page, a keyboard instead of a mouse, text magnified three times, captions instead of sound. A site that is not built for them is not merely awkward; it can be impossible — a form with unlabelled fields, a menu that cannot be reached without a mouse, a video with no captions, a button that is a picture of text. The Americans with Disabilities Act is applied to websites by the courts, and for state and local governments the Department of Justice's Title II rule now sets explicit WCAG deadlines.
We audit against WCAG 2.2 at level AA the way a person experiences it: automated tooling first to catch the obvious, then a manual pass with a screen reader and a keyboard through the real journeys — finding a service, filling in the form, checking out. Issues are ranked by how badly they block someone, fixed in the site's code and templates so they stay fixed, and documented in an accessibility statement that says what was done and how to report a problem. Content guidance covers the things a developer cannot fix: alt text, headings, PDFs.
We do not install overlay widgets. They do not fix the underlying code, they interfere with the assistive technology people already use, and they appear by name in the lawsuits they were bought to prevent.
Capabilities
What's included
- WCAG 2.2 auditAutomated scan plus a manual pass with a screen reader and keyboard through the journeys that matter, ranked by impact.
- Remediation in the codeTemplates, components, forms, navigation and media fixed at the source, with changes documented.
- Accessibility statementWhat standard the site meets, known limitations, and how to report a barrier — the document regulators look for.
- Content and document guidanceAlt text, headings, link text and accessible PDFs, with a short guide for the people who publish.
- Design system fixesColour contrast, focus states, target sizes and motion settings corrected once, everywhere.
- Ongoing monitoringAutomated checks on every release and a periodic manual re-test, so new content does not undo the work.
How We Work
Our approach
- 01
Audit
Automated and manual testing of the real user journeys, returned as a ranked, plain-English report.
- 02
Fix
Code and template changes on staging, verified with the same assistive technology that found the problem.
- 03
Document
Accessibility statement published; content guide delivered; the record kept for anyone who asks.
- 04
Maintain
Checks on each release and a periodic re-audit, because sites change.
What You Get
Commitments
Fixes are made in the code, where the problem is.
A person with a screen reader and a keyboard, not only a scanner.
What was found, what was fixed, and how to report a barrier.
To Get Started
What we need from you
- Access to the website's code and CMS, or a developer who can make changes.
- The user journeys that matter most — finding a service, the contact form, the checkout, the payment portal.
- For public bodies, which Title II deadline applies to you.
- A person who can publish the accessibility statement and own the report-a-barrier inbox.
Common Questions
Questions we get asked
Does the ADA actually apply to our website?
Courts have repeatedly applied the Americans with Disabilities Act to the websites of businesses open to the public, and demand letters citing it are common for small businesses, not only large ones. For state and local governments, the Department of Justice's Title II rule removes the ambiguity: web content must meet WCAG 2.1 AA by deadlines in 2026 and 2027 depending on population. We are not lawyers; we make the site meet the standard the law points at.
Can we just install an accessibility overlay plugin?
We advise against it. Overlays add a widget on top of the page without fixing the code underneath, often conflict with the screen readers and settings disabled people already use, and have been named in accessibility lawsuits against the sites that installed them. The work that holds up is fixing the templates, forms and content themselves.
What does the Title II rule mean for a city, county or school district?
Web content and mobile apps must conform to WCAG 2.1 level AA, with the deadline set by the population served — April 2026 for larger entities and April 2027 for smaller ones and special districts — and with specific exceptions for archived content and some third-party material. Most local-government sites we audit have the same handful of blocking issues, and they are fixable within the timeline.
How long does an audit and remediation take?
An audit of a typical small-business or local-government site takes one to two weeks and comes back as a ranked report. Remediation depends on what it finds and how the site is built: a well-constructed WordPress theme can often be fixed in a few weeks; a page-builder site may need its templates rebuilt. The report tells you which before you commit to the fixes.
Do you only report problems, or do you fix them?
We fix them, which is the reason to use a developer rather than a scanning service. The audit is the first step; remediation in the code is the second; and the statement and ongoing checks are what keep the site compliant as content changes. If you have your own developer, we can hand them the ranked report with the fixes specified instead.
Will accessibility changes alter how the site looks?
Rarely in ways a sighted mouse user would notice. Contrast adjustments, visible focus outlines and slightly larger tap targets are the most visible changes, and they tend to improve the design for everyone. Most of the work — labels, structure, keyboard order, alternative text — is invisible until you need it.
Works for everyone.
Documented for anyone.
Tell us what you have and what it needs to do. We respond within one business day with a scope and a price.