01
ADA compliance audit
A manual and automated audit of your key templates and journeys. Every issue comes with its WCAG criterion, severity, a screenshot and the fix.
FIG 01 · Website Accessibility
ADA compliance and website accessibility services
Manual and automated WCAG 2.2 AA audits, fixes in your code and content, screen-reader retests and checks on every release. Audit and remediation work, not legal advice, and no overlay widgets.
See how it works
FIG 02 · Quick answer
What are ADA compliance services?
ADA compliance services find and fix the barriers that stop disabled people from using your website. Elgrith audits your site against WCAG 2.2 AA with manual and automated testing, fixes issues in your code and content, retests with screen readers and keyboards, and checks each new release. We don’t sell overlay widgets.
- The WCAG level we audit and fix against
- 2.2 AA
- Projects delivered since 2015
- 1,000+
- Clients across the USA, UK and India
- 250+
- Overlay widgets: every fix goes into your code
- 0
FIG 03 · Why it matters
Most websites still fail basic accessibility checks.
From WebAIM’s 2026 analysis of the top one million home pages. Automated tests catch only part of the problem, so the real picture is worse.
01
95.9%
Of home pages had detected WCAG failures
WebAIM found that 95.9% of home pages had detected WCAG 2 failures in its 2026 study.
Source: WebAIM Million, 30 Mar 2026(opens in a new tab)02
56.1
Errors per page, on average
The same study found an average of 56.1 errors per home page.
Source: WebAIM Million, 30 Mar 2026(opens in a new tab)03
83.9%
Of home pages had low-contrast text
Low-contrast text was found on 83.9% of the home pages WebAIM tested. It is one of the easiest failures to fix.
Source: WebAIM Million, 30 Mar 2026(opens in a new tab)
FIG 04 · Plain English
What ADA compliance means for a website
The ADA doesn’t include a detailed technical standard for most business websites: ada.gov says “The Department of Justice does not have a regulation setting out detailed standards”. In practice WCAG 2.1 or 2.2 Level AA is the working benchmark, and the DOJ’s Title II rule for state and local governments uses WCAG 2.1 Level AA.
| What it is | Who it applies to | Technical standard | |
|---|---|---|---|
| ADA Title III | US civil rights law for places of public accommodation | Businesses open to the public | No detailed DOJ web regulation; WCAG AA is the common benchmark |
| ADA Title II | US civil rights law for public entities | State and local governments | WCAG 2.1 Level AA, from 26 April 2027 or 26 April 2028 |
| WCAG 2.2 | The W3C’s Web Content Accessibility Guidelines | Anyone who adopts it, and laws that reference it | Levels A, AA and AAA; AA is the usual target |
| Section 508 | US federal rule for information and communication technology | Federal agencies and the products they buy | Harmonized with WCAG 2.0 Level AA |
This is general information, not legal advice. We audit and fix against WCAG 2.2 AA, which covers 2.1 AA; your lawyer should advise on your legal obligations.
Read the ADA website compliance checklistFIG 05 · What you get
Our accessibility services
Audit, remediation and retesting from the team that builds websites, so fixes land in your code, not in a widget on top of it.
02
WCAG compliance services
Testing against WCAG 2.2 AA, including the criteria added in 2.2 such as focus not obscured, target size and accessible authentication.
03
Accessibility remediation
Fixes in your code and content: semantics, labels, contrast, focus, ARIA and forms, with PDFs and documents where agreed in scope.
04
Screen-reader and keyboard testing
Real journeys tested with NVDA, JAWS, VoiceOver and TalkBack, and by keyboard alone, not just with automated checkers.
05
Accessible design and redesign
Design systems, colour tokens and components built accessible from the start, so new pages don’t reintroduce old problems.
06
Monitoring and retesting
Automated checks in your release pipeline and manual retests of key journeys when you ship changes.
Deliverables
12
deliverables, in writing
Included in every build, written into your fixed quote before work starts.
FIG 06 · Common failures
The most common failures we fix
WebAIM’s 2026 report finds the same handful of errors on page after page, led by low-contrast text on 83.9% of home pages. These are the failures we look for first.
Low-contrast text
- WCAG
- 1.4.3 Contrast (Minimum)
- Affects
- People with low vision, and everyone in bright light
- Fix
- Colour tokens that meet AA contrast
Missing alt text
- WCAG
- 1.1.1 Non-text Content
- Affects
- Screen-reader users
- Fix
- Useful alt text, or empty alt for decoration
Unlabelled form fields
- WCAG
- 1.3.1, 3.3.2 and 4.1.2
- Affects
- Screen-reader and voice-control users
- Fix
- Visible labels tied to every input
Empty links and buttons
- WCAG
- 2.4.4 Link Purpose and 4.1.2 Name, Role, Value
- Affects
- Screen-reader users
- Fix
- Accessible names on icon links and buttons
Missing page language
- WCAG
- 3.1.1 Language of Page
- Affects
- Screen readers choosing a voice
- Fix
- The right lang attribute on every page
Keyboard traps and hidden focus
- WCAG
- 2.1.2 No Keyboard Trap, 2.4.7 Focus Visible
- Affects
- Keyboard and switch users
- Fix
- Visible focus rings and managed focus in menus and dialogs
Focus hidden under sticky headers
- WCAG
- 2.4.11 Focus Not Obscured (new in 2.2)
- Affects
- Keyboard users
- Fix
- Scroll padding and layered headers
Tiny tap targets
- WCAG
- 2.5.8 Target Size (Minimum) (new in 2.2)
- Affects
- People with tremors or limited dexterity
- Fix
- Larger targets or enough spacing
FIG 07 · Flagship build
Proof: fixes from the team that builds the product
Kenerate AI is our flagship build, an all-in-one AI image and video studio we designed and engineered. It is not an accessibility case study; it shows the front-end engineering our fixes come from.
- 23+ studios and tools in one product, from Image Studio to Director
- 200+ AI models behind one app, one login and one credit balance
- Up to 4K output, and credits that never expire
- 1,000+ projects for 250+ clients since 2015
Home: one prompt box for image, video and musicDesigned and engineered by Elgrith
- AI models in one app
- 200+
- Studios and tools
- 23+
- Maximum output
- 4K
- Guides
- 500+
FIG 08 · No overlays
Why we don’t sell accessibility overlays
In 2025 the FTC approved a final order barring accessiBe from “representing that its automated products can make any website WCAG-compliant”. ada.gov also warns that a “clean” report from an automated checker does not necessarily mean everything is accessible.
05principles
Overlays don’t change your code
The underlying problems stay in your templates, and come back in every new page.
Automated scans miss things
Checkers can’t judge whether alt text makes sense or a journey works by keyboard. People have to test it.
Users bring their own tools
Screen-reader and magnifier users already have assistive tech set up. A widget can get in its way.
Fix it once, in the source
Fixes in your components and design tokens carry through to every page that uses them.
Evidence you can show
An issue list, a fix log and retest results, instead of a badge.
FIG 09 · United Kingdom
Accessibility audits in the UK
GOV.UK says “All UK service providers have a legal obligation to make reasonable adjustments under the Equality Act 2010”, and public sector websites must meet WCAG 2.2 AA. Our UK audits test to that standard.
05principles
WCAG audit to 2.2 AA
A manual and automated audit of your key templates and journeys against WCAG 2.2 AA, the level GOV.UK sets for the public sector.
Assistive-technology testing
Journeys tested with NVDA, JAWS, VoiceOver and TalkBack, and by keyboard alone.
Evidence for your accessibility statement
An issue list and fix log your team can draw on when publishing the statement public sector bodies must keep.
Colour and design tokens
Brand colours checked and adjusted so text and controls meet AA contrast without losing your look.
Selling into the EU?
The European Accessibility Act has applied since 28 June 2025, including to e-commerce. We test against the same WCAG criteria.
FIG 10 · Go further
Accessibility across everything you ship
Accessibility lasts when it is part of design, development and maintenance. These services sit next to it.
05principles
Redesigning anyway?
Build accessibility into the new site instead of retrofitting it.
Website redesignAccessible storefronts
Shopify Plus themes and checkout extensions tested against WCAG 2.2 AA.
Shopify Plus developmentNative apps too
iPhone apps designed for VoiceOver and Dynamic Type from the first screen.
iOS app development
FIG 11 · Process · 7 steps
Test with real tools, then fix the code
A fixed written quote after scoping. You see every issue, every fix and every retest result.
- Step 01
Scope
We agree the templates, journeys, documents and apps to test, and the standard: WCAG 2.2 AA. You get a written scope and a fixed quote.
- Step 02
Automated scan
axe, WAVE and Lighthouse across the agreed pages to catch the machine-detectable issues quickly.
- Step 03
Manual and assistive-tech testing
Keyboard-only journeys and screen-reader testing with NVDA, JAWS, VoiceOver and TalkBack.
- Step 04
Report
A prioritized issue list with WCAG criterion, severity, screenshot and fix for each issue.
- Step 05
Remediation
We fix issues in your code, components and content, or guide your developers through the fixes.
- Step 06
Retest
Every fix is retested manually and with assistive technology before it is closed.
- Step 07
Monitoring
Automated checks in your release pipeline, plus manual retests when you ship major changes.
FIG 12 · What you get
Everything included
Written into your fixed quote, so you know exactly what you are paying for before work starts.
12items
- Written scope and fixed quote
- Automated scan results
- Manual and screen-reader test notes
- Prioritized issue list with WCAG criteria
- Screenshots and fix guidance per issue
- Code and content remediation
- Accessible colour and focus tokens
- Retest results for every fix
- Fix log for your records
- Automated checks in your pipeline
- Guidance for content editors
- All code and reports, yours
FIG 13 · Tech & tools
The tools behind the work
Proven, well-supported tools, chosen for your project and set up in accounts your business owns.
- WCAG 2.2
- WAI-ARIA
- axe
- WAVE
- Lighthouse
- NVDA
- JAWS
- VoiceOver
- TalkBack
- Keyboard testing
- Playwright
- Accessibility Inspector
- Next.js
- React
- WordPress
- Shopify
FIG 14 · Who it’s for
Accessibility work for every kind of site.
Audit and remediation guidance for US and UK organizations. Not legal advice, and never a guarantee of a legal outcome.
3 audiences
US businesses
Websites people with disabilities can use.
An audit against WCAG 2.2 AA, fixes in your code and retests, for businesses that want their site to work for everyone.
- Manual and automated testing
- Fixes in your own code
- Retests with screen readers
- Monitoring on each release
UK organisations
Audits to the standard GOV.UK sets.
WCAG 2.2 AA audits for UK businesses and public bodies, with evidence your team can use for accessibility statements.
- UK spelling and reporting
- WCAG 2.2 AA testing
- Assistive-technology testing
- London client partner
Online stores
Checkouts everyone can finish.
Product pages, filters, carts and checkout tested end to end, including for EU customers under the European Accessibility Act.
- Full purchase journeys tested
- Accessible filters and carousels
- Form and error messages fixed
- Shopify and WooCommerce
FIG 15 · Working with us from the USA and UK
Built in New Delhi. Run on your hours.
Every project gets a point of contact in New York or London and an engineering team in New Delhi. Here is how today’s working days line up, live.
New York
North America
--:--ET
New Delhi team Your working day- Shared working time
- ≈ 3 hours today
- New Delhi is
- 10.5 h ahead
- Live calls, your time
- 9 a.m. to 12 p.m. ET
London
UK & Europe
--:--UK
New Delhi team Your working day- Shared working time
- ≈ 4.5 hours today
- New Delhi is
- 5.5 h ahead
- Live calls, your time
- 9 a.m. to 1:30 p.m. UK
Three ways to work together
- 01
Fixed-scope project
A written scope, one fixed price and a dated plan. Suits websites, apps and MVPs.
- 02
Dedicated team
Designers and engineers on your roadmap every month, billed monthly.
- 03
White label
For US and UK agencies: our work, your brand, unbranded deliverables.
Every engagement
- Fixed quote in USD, GBP or INR after a free 30-minute call
- NDA before discovery. You own all code, designs and content
- A working demo every sprint, not status slides
- Reply within one business day, calls inside your hours
Book a call
Calls on ET or UK hours
FIG 16 · Law
Accessibility law in the US, UK and EU
A plain-language summary of the main rules, checked on ada.gov, GOV.UK and AccessibleEU in October 2026. It is not legal advice.
| Law | Who it covers | Standard or duty | Key dates |
|---|---|---|---|
| ADA Title II (US) | State and local government websites and apps | WCAG 2.1 Level AA | 26 April 2027 for populations of 50,000+; 26 April 2028 for under 50,000 and special districts |
| ADA Title III (US) | Businesses open to the public | No detailed DOJ web regulation; WCAG AA is the common benchmark | In force; no web-specific date |
| Equality Act 2010 (UK) | All UK service providers | A legal obligation to make reasonable adjustments | In force |
| Public sector accessibility regulations (UK) | Public sector websites and apps | WCAG 2.2 AA | In force |
| European Accessibility Act (EU) | Products and services such as computers, smartphones and e-commerce | Mandatory accessibility requirements | Applies from 28 June 2025 |
The Title II dates reflect the DOJ’s interim final rule of 20 April 2026; some older pages still show 2026 dates. Ask your lawyer how these rules apply to you.
Read the ADA website compliance checklistFIG 17 · Compare
Manual audit, automated scan or overlay widget?
| Manual + automated audit (Elgrith) | Automated scan only | Overlay widget | |
|---|---|---|---|
| What it finds | Machine-detectable issues plus keyboard, screen-reader and content problems | Machine-detectable issues only | Claims to find and fix issues automatically |
| Fixes | In your code, components and content | None: a list of errors | A script on top of your site; the code is unchanged |
| Evidence | Issue list, fix log and retest results | A scan report | A badge or statement from the vendor |
| Ongoing | Checks in your pipeline and manual retests | Repeat scans | A monthly subscription |
| Legal position | Audit and remediation guidance, not legal advice | A “clean” report doesn’t mean everything is accessible (ada.gov) | The FTC barred one vendor from claiming its product makes sites WCAG-compliant |
FAQ
Frequently asked questions
Straight answers about Website Accessibility with Elgrith.
Ours include an audit against WCAG 2.2 AA using automated tools plus manual keyboard and screen-reader testing, a prioritized issue list with the WCAG criterion, severity, a screenshot and the fix for each issue, remediation in your code and content, retesting, and monitoring on new releases. We describe this as audit and remediation work, not legal advice.
FIG 18 · Related
Keep exploring
Free 30-minute call
Find the barriers. Fix them in the code.
Tell us about your site. After a free call you get a written scope for the audit and fixes, and a fixed quote.
Pick a day for your call
OpenPick a day. You'll choose a time in your own time zone on the next step.