Accessibility
ADA website accessibility services: WCAG 2.2 AA audits, fixes and builds
Our ADA website accessibility services cover three jobs: auditing your site against WCAG 2.2 Level AA, fixing what the audit finds in your own code, and building new sites that meet it from the first sprint. We test with automated tools, a keyboard and real screen readers. We do not certify a site as ADA compliant; that legal judgement belongs to your counsel.
- We build and test to
- WCAG 2.2 Level AA
- Testing
- axe, keyboard, NVDA, VoiceOver
- Fixes
- In your source code, not an overlay
- Pricing
- Fixed quote after discovery
Updated · By the Codebrix team
Audit, remediation or rebuild: which one you need
How much work you face depends on where the problems sit. A failure in a shared header, form or colour palette is fixed once and repaired on every page. A failure in hundreds of PDFs or uncaptioned videos is content work, item by item.
| Service | What you get | When it fits |
|---|---|---|
| Audit | A WCAG 2.2 AA review of each template and key journey (booking, sign-up, checkout, login), each failure mapped to a criterion, the affected code and a fix | You need to size the problem before you budget |
| Remediation | Fixes in your repository or CMS theme, each re-tested, with a report of what changed and what is left | The site is sound but carries accessibility debt |
| Accessible build or rebuild | A new site designed and built to WCAG 2.2 AA, with checks in every weekly sprint | The platform blocks fixes, or a redesign is due anyway |
If your theme outputs markup you cannot change, patching can cost more than a website redesign.
What US law asks, depending on who you are
For businesses open to the public (Title III), the Department of Justice's guidance on web accessibility, dated 18 March 2022, says the DOJ has no regulation setting detailed standards and that businesses can currently choose how to make their online offerings accessible, while still meeting the ADA. It names WCAG and the Section 508 Standards as helpful guidance, and states that the guidance itself is not legally binding.
State and local governments (Title II) have a specific rule. The DOJ's fact sheet says it was published on 24 April 2024 and sets WCAG 2.1 Level AA for web content and mobile apps. An interim final rule of 20 April 2026 moved compliance to 26 April 2027 for governments serving 50,000 or more people, and 26 April 2028 for smaller ones and special districts. It covers content a contractor provides too: the DOJ's example is a county page built by a local web design company.
| Who you are | What applies | Standard named |
|---|---|---|
| Business open to the public | ADA Title III; DOJ 2022 guidance, no detailed regulation | WCAG and Section 508 as helpful guidance |
| State or local government, or a vendor building for one | ADA Title II; DOJ 2024 rule | WCAG 2.1 AA, by 26 April 2027 or 26 April 2028 |
| Vendor selling ICT to federal agencies | Revised Section 508 Standards | WCAG 2.0 Level A and AA, incorporated by reference |
The last row is from the Access Board's ICT standards. Which row applies to you is a question for counsel.
Why we build to WCAG 2.2 AA
W3C published WCAG 2.2 on 5 October 2023, adding nine success criteria and removing 4.1.1 Parsing as obsolete. The WCAG overview says content that conforms to 2.2 also conforms to 2.1 and 2.0, so one target covers every row above. The new A and AA criteria that change design and build:
- 2.4.11 Focus Not Obscured (Minimum): sticky headers, cookie banners and chat bubbles must not hide the focused element.
- 2.5.7 Dragging Movements: anything dragged, such as sliders or sortable lists, also works with a single click or tap.
- 2.5.8 Target Size (Minimum): pointer targets at least 24 by 24 CSS pixels, or spaced apart.
- 3.2.6 Consistent Help and 3.3.7 Redundant Entry: help in the same place on every page, and no asking for the same information twice.
- 3.3.8 Accessible Authentication (Minimum): sign-in without puzzles or transcription; password managers and paste must work.
Most of these are settled in design, so our UI/UX design work checks them in Figma first. W3C lists all nine in What's New in WCAG 2.2.
How we test: tools first, people second
W3C's advice on selecting evaluation tools is blunt: tools cannot determine accessibility, they can only assist, and human judgement is required. So every audit and every build runs through five passes:
- Automated scan of every template with axe-core, wired into CI on builds we deliver so a new failure blocks the merge.
- Keyboard-only pass: tab order, visible focus, a skip link, no focus traps, and menus, modals and date pickers usable without a mouse.
- Screen reader pass with NVDA on Windows and VoiceOver on macOS and iOS: headings, landmarks, control names, announced form errors.
- Zoom and phone-width pass: nothing overlaps, clips or forces sideways scrolling.
- Content pass: useful alt text, captions, link text that makes sense alone, and documents.
Each finding is logged with the criterion, steps to reproduce, severity and component, so whoever fixes it can re-run the same steps.
Why an overlay is not the fix
The DOJ's own guidance says automated checkers and overlays that identify or fix problems “can be helpful tools”, but that they “need to be used carefully”, and that a clean report “does not necessarily mean everything is accessible”. It recommends pairing a manual check with automated checkers.
An overlay is a script running on top of the page; the HTML, PDFs, videos and widgets underneath stay as they were. We fix the source: native buttons, labelled fields, managed focus in dialogs, correct heading order. If you already run an overlay, we audit with it on and off.
Remediation that stays fixed
| Where the issue lives | Typical example | How we fix it |
|---|---|---|
| Design tokens | Pale grey text, focus ring removed | Change the tokens once; every page inherits it |
| Shared components | Unnamed icon buttons, custom dropdowns, modals losing focus | Rebuild on native elements or a tested ARIA pattern |
| Page templates | No main landmark, skipped headings | Fix in the layout, once |
| Content | Missing alt text, “click here” links | Your editors, with a short guide and required alt text fields |
| Third-party embeds | Booking widgets, chat, maps | Report to the vendor, or replace |
Fixes regress when the next feature ships, so the automated checks stay in your pipeline. A periodic re-test can sit inside a maintenance retainer.
VPAT and ACR for selling to government
Section508.gov describes an Accessibility Conformance Report as a document explaining how a product meets the Revised 508 Standards, and recommends vendors produce one for anything marketed to the federal government. Its VPAT guide says the usual way is the IT Industry Council's VPAT template, in the Revised Section 508 or International edition for federal sales.
We produce the test evidence and draft remarks from what the tests show. You publish the ACR under your company's name, after counsel reviews it.
Cost, timeline and what you provide
We have not published a separate price for audits or remediation, because the work scales with templates, journeys, components, embeds and documents. A rebuild falls inside our indicative ranges: $1,500 to $4,500 for a marketing website over 2 to 6 weeks, or $5,500 to $22,000 for a web application over 6 to 16 weeks. Re-testing fits our support retainer, indicatively $550 to $1,800 a month. The fixed quote comes after a discovery call. From you we need staging access, your key journeys, CMS access and, with counsel's agreement, any demand letter or earlier audit. We work remotely from Noida; see our page for US businesses.
Frequently asked questions
Will you make our website ADA compliant?
We build and test to WCAG 2.2 Level AA and document what we tested and fixed. We do not issue compliance certificates, because whether a site meets the ADA is a legal judgement. Your counsel decides the standard you hold yourself to; we deliver the technical work and the evidence behind it.
Which WCAG version should a US business aim for?
Title III sets no version for businesses. State and local governments must meet WCAG 2.1 AA under the DOJ's 2024 rule, and federal procurement uses WCAG 2.0 A and AA through Section 508. Content meeting WCAG 2.2 AA also meets 2.1 and 2.0, so 2.2 AA is our default.
Do accessibility overlay widgets solve the problem?
The DOJ's 2022 guidance says automated checkers and overlays can be helpful but need to be used carefully, and that a clean report does not mean a site is accessible. An overlay does not change your underlying HTML, documents or embedded widgets. We fix those at the source and test with the overlay both on and off.
Can you fix an existing WordPress or Shopify site?
Usually, where the theme and templates are editable. Most fixes go into the theme, shared components and colour settings, and some into content your editors manage. Where a plugin produces markup nobody can change, we report it to the vendor or suggest a replacement.
Do mobile apps need to be accessible too?
The DOJ's Title II rule covers mobile apps that state and local governments provide, not only websites. Private businesses should raise their apps with counsel too. In apps we test with VoiceOver on iOS and TalkBack on Android, plus large text settings and touch target sizes.
Can you produce a VPAT for our product?
We can test the product against the VPAT's Revised Section 508 edition and draft the remarks from the results. The finished Accessibility Conformance Report is your company's own statement, so we write only what the tests support and your counsel reviews it before any bid.
Sources
- ADA.gov: Guidance on Web Accessibility and the ADA (18 March 2022)
- ADA.gov: Fact sheet, rule on web content and mobile apps of state and local governments
- W3C: What's New in WCAG 2.2
- W3C: WCAG 2 Overview
- W3C: Selecting Web Accessibility Evaluation Tools
- U.S. Access Board: ICT Accessibility 508 Standards
- Section508.gov: Accessibility Conformance Report (ACR)
- Section508.gov: How to Create an ACR with a VPAT
Related
United States
An offshore web development company in India for US businesses
Offshore web development company in India for US businesses: USD pricing, Stripe or wire payment, IP assigned to you, and a planned ET and PT overlap.
Read moreWebsite redesign
Website redesign services that protect the search traffic you already have
Website redesign services that audit first, map every URL and 301-redirect old pages so the search traffic you have earned is carried to the new site.
Read moreUI/UX design
A UI/UX design agency in India that designs what will be built
UI UX design agency in India: user research, wireframes, Figma screens, a design system and a clickable prototype, designed by the team that builds it.
Read moreMaintenance
Website maintenance services that keep your site patched, backed up and improving
Website maintenance services on a monthly retainer: updates, backups, uptime monitoring, security patches and small features. Indicatively ₹15,000–50,000.
Read moreMedical practices, US
Medical practice website design for US practices that keeps PHI out of the wrong places
Medical practice website design for US clinics: booking and patient forms planned around PHI, no ad pixels on PHI pages, honest reviews and WCAG 2.2 AA.
Read moreLaw firms, US
Law firm website design for US practices, built around the advertising rules
Law firm website design for US firms: practice-area pages, intake forms built around Rule 1.18 and copy checked against your state's advertising rules.
Read more