Conversion & Lead Capture
Your site, made usable by everyone, and defensible if anyone asks.
For US businesses whose site already exists but has never been checked against a real accessibility standard, and who would rather fix it properly than bolt on a widget and hope.
Every engagement is directed by a technical specialist and reviewed before delivery.
What this is
An Accessibility Compliance Pass is a full WCAG 2.2 AA audit of your existing website, followed by the actual remediation, with the fixes made in the code and then re-verified. A specialist tests every page type the way a real user with a disability would: by keyboard alone, with a screen reader, at high zoom, and against color-contrast ratios, checking the parts automated scanners cannot reach. You get a plain-English findings register that maps each barrier to the specific success criterion it fails and how we resolved it, the corrected front end, and a re-test that confirms your site now conforms. This is not an overlay or a plugin painted over broken markup. It is the underlying HTML, focus order, labels, contrast and interaction fixed at the source, so your site is genuinely operable for every visitor and holds up to scrutiny. You end up with a site that works for everyone, and a documented record that proves it.
The problem
Why this matters now
Most small-business sites were never built to an accessibility standard. Yours can look fine on the surface while a visitor using a screen reader hits unlabeled buttons, a keyboard user gets trapped in a menu that will not close, and someone with low vision cannot read gray text on a paler gray background. These are not edge cases. They are the difference between a customer who can book and one who leaves.
The legal exposure has grown real and specific. In the US, courts treat business websites as places of public accommodation under the ADA, and demand letters and filings have climbed year over year. If you touch EU customers, the European Accessibility Act has applied since June 2025. A plaintiff does not need to prove intent, only that a barrier exists, and an unlabeled checkout or an inaccessible form is barrier enough.
The common shortcut makes it worse. Accessibility overlay widgets promise instant compliance from a single line of script, and they do not deliver it. They sit on top of broken code instead of fixing it, they frequently interfere with the assistive technology they claim to help, and they hand a plaintiff visible proof that the real barriers were never addressed. Regulators have started to treat those compliance claims as deceptive.
What actually resolves this is unglamorous and durable: test the site properly, fix the underlying markup and interaction, and verify the result. That is remediation, and it is what a Compliance Pass is.
How it works
The mechanism, made checkable
- 01
Scope and baseline audit
A specialist inventories your page types and templates, then runs a full audit against WCAG 2.2 AA. This combines automated scanning with the manual testing that automated tools cannot do: keyboard-only operation, screen-reader passes, zoom and reflow, focus visibility and order, and color-contrast measurement. This matters because industry testing shows only around 30 percent of WCAG success criteria can be caught by automated tools alone, so a scanner-only report misses most of what actually blocks people.
- 02
A findings register mapped to the standard
Every barrier we find is written up in plain English and mapped to the exact WCAG 2.2 success criterion it fails, its conformance level, where it occurs, and its severity for a real user. The result is a register you can read and act on, not a raw scanner dump of thousands of duplicate flags. This is the document that turns a vague worry into a concrete, prioritized list of work.
- 03
Remediation at the source
We fix the issues in the code, not over it. That means real semantic structure and landmarks, labels and names for every control, a logical and visible focus order, keyboard operability for every interaction, sufficient contrast, target sizes that meet the 2.2 minimum, and accessible forms and error handling. No overlay is installed, because an overlay does not fix broken markup and often makes the experience worse for the people it claims to serve.
- 04
Contrast, content and media checks
We check text and interface contrast against the WCAG ratios, a minimum of 4.5 to 1 for normal text per the W3C guidelines, and flag anything that fails. Image alternative text, video captions and transcripts, heading structure, link purpose, and reading order are all reviewed, so your content is technically present and actually understandable to someone using assistive technology.
- 05
Verification re-test
After the fixes ship, we re-run the audit against the same standard and the same methods. Nothing is called done on assertion. The re-test confirms each finding is resolved and catches anything a fix introduced, so the result you get is verified rather than hopeful.
- 06
Documentation and an accessibility statement
You get the closed findings register showing what was found and how it was resolved, and a drafted accessibility statement for your site describing its conformance and how visitors can report an issue. This is the record that demonstrates the work was done properly, which is exactly what a demand letter or an EAA obligation asks a business to show.
What is included
What is delivered
- A full WCAG 2.2 AA audit across every page type and template, combining automated scanning with manual keyboard and screen-reader testing
- A plain-English findings register mapping each barrier to its WCAG success criterion, conformance level, location and severity
- Remediation of the issues in the source code: semantic structure, labels and names, focus order, keyboard operability and target sizes
- Color and interface contrast checked against the WCAG ratios, with failing pairings corrected
- A review of alternative text, captions, transcripts, headings, link purpose and reading order for assistive-technology users
- Accessible forms and error handling across contact, booking and checkout paths
- A verification re-test against the same standard after the fixes ship, confirming each finding is closed
- A drafted accessibility statement for the site, and a handover of the corrected front end and the closed register
The outcome
What it moves
- A site a keyboard-only user, a screen-reader user, and a low-vision visitor can all actually operate, from the first page to the checkout or booking step
- Barriers fixed in the underlying code, so the accessibility holds instead of sitting on a widget that can be stripped away or that breaks assistive technology
- A documented findings register that maps every issue to the WCAG 2.2 criterion it failed and shows how it was resolved
- An accessibility statement drafted for your site, giving visitors a clear route to report a problem and giving you a record of the standard you met
- Color, contrast, focus and forms brought to WCAG 2.2 AA, the level US and EU expectations now converge on
- A verified result, re-tested after the fixes, rather than a scan report handed over with the hard part left undone
What you get
What you get, and how it is priced
What a Compliance Pass costs follows how the site was actually built and how far it currently sits from the standard. A clean, custom marketing site may need a light touch. A plugin-heavy build or a store with forms and a checkout will need real remediation. The standard tested against and everything the pass delivers are published, then the exact work is scoped against the pages and the figure confirmed in writing before anything begins. The levels below describe the depth of the work, and the right one is settled once a specialist has seen the site.
| Audit and Findings. A complete WCAG 2.2 AA audit of your site with the plain-English findings register mapped to the standard, plus a remediation plan your own developer can act on. The right level when you have technical hands in-house and need the expert assessment and the prioritized list. Scoped to your page types, quoted after a short conversation. | Quoted |
| Full Compliance Pass. The audit plus the remediation plus the verification re-test: we find the barriers, fix them in the code, and re-test to confirm the site conforms, then hand over the closed register and a drafted accessibility statement. The level most businesses need. Scoped to how your site is built and how far it starts from the standard. | Quoted |
| Compliance Pass with Monitoring. The full pass, plus a defined cadence of re-checks so the site stays conformant as you add pages, run promotions and change content. For sites that change often or carry real transactional risk. Scoped once we have seen how the site is maintained and how quickly it changes. | Quoted |
You see the full deliverables and cadence first, then a price built for your business, confirmed in writing.
Straight answers
Questions about Accessibility Compliance Pass
Can I just install an accessibility widget or overlay instead?
Installing one will not make your site compliant, and it can create new problems. Overlays sit on top of broken code rather than fixing it, they frequently interfere with the screen readers and keyboards they claim to help, and they give a plaintiff visible proof that the underlying barriers were never resolved. In 2025 the US Federal Trade Commission ordered a major overlay vendor to pay one million dollars for falsely claiming its tool could make any site conform. A Compliance Pass fixes the actual code, which is the only thing that holds up.
Is this real testing, or just an automated scan you re-badge?
It is real testing. A scanner is one input, and on its own it catches only around 30 percent of WCAG issues, because most success criteria require a human to judge them. A specialist operates your site by keyboard, listens to it through a screen reader, checks focus order and contrast, and reviews the content the way an assistive-technology user experiences it. A specialist directs the work and reviews it before delivery. The result is expert judgement backed by tooling, not a raw scan dump.
Do you actually fix the site, or just hand me a report?
That depends on the level you choose, and we state it explicitly. Audit and Findings gives you the assessment and a prioritized plan for your in-house developer to act on. The Full Compliance Pass means we make the fixes in the code directly and then re-test to confirm they worked. Remediation is never called done on assertion. The verification re-test against the same standard is what separates a finished pass from a report with the hard part left undone.
You bill in USD, but where is the work done, and does that affect compliance?
Billing is in USD by RavenGroup Global Tech Private Limited, with no surprise conversion. Where the work is done does not change what it is measured against. Your site is tested to WCAG 2.2 AA, the same public standard US and EU expectations reference, and the result is verifiable: the checks can be re-run against the closed register. A named specialist owns the outcome and reviews it before delivery.
We are a small business. Are we really at legal risk?
Enough small businesses receive demand letters and filings each year that it is worth treating as real rather than remote. US courts widely treat business websites as places of public accommodation under the ADA, and a plaintiff does not need to prove intent, only that a barrier exists. If you serve EU customers, the European Accessibility Act has applied since June 2025. This is not legal advice, but the practical protection is the same either way: fix the barriers and keep a record of it.
Do you guarantee we will not be sued?
No. Nobody controls whether a demand letter arrives. What a Compliance Pass gives you is the thing that matters if one does: a site tested and remediated to WCAG 2.2 AA and a documented record of the work. That is a defensible position rather than a widget and a hope. Your site is built to the standard, verified against it, and the record is yours to keep.
Why is this scoped instead of a price on the page?
Because the work depends entirely on how your site was built and how far it sits from the standard. A clean custom site might need a light pass, while a plugin-heavy store with forms and a checkout needs real remediation, and one published number for both would be a fiction. Pricing by how large a business looks would be worse. What the pass includes is published in full, the work is scoped against your pages, and the figure is confirmed in writing before anything starts.
Will this hurt how the site looks or how fast it loads?
No. Almost all accessibility work is invisible to a sighted mouse user: labels, focus order, semantic structure and contrast adjustments that a designer would call good practice anyway. Where a contrast fix changes a color, the work stays within your existing brand and is flagged before it ships. Accessible markup is generally cleaner and lighter than the overlay scripts businesses bolt on, so if anything your site gets leaner, not heavier.
Related
Where this connects
Website Build
When the site is too far gone to patch, a rebuild that is engineered to WCAG 2.2 AA from the first line rather than remediated after the fact.
ExploreConversion Optimization
The same clarity that makes a site accessible tends to lift conversion. Turn a usable site into a measurably better-converting one through shipped tests.
ExploreThe Machine-Readiness Score
Accessibility is part of the technical foundation the Machine-Readiness Score is built on. See how a clean, operable site strengthens your whole visibility picture.
ExploreProvenance
Sources
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2, published 5 October 2023: WCAG 2.2 became a Recommendation, adding nine success criteria including focus appearance, target size minimum and accessible authentication; minimum contrast of 4.5:1 for normal text.
- Multiple 2026 WCAG audit references (Level Access, TheWCAG, DigitalApplied, accessed July 2026): only roughly 30 percent of WCAG success criteria are fully detectable by automated tools; the majority require manual testing.
- US Federal Trade Commission action, April 2025 (reported by 216digital and Kha Creation, accessed July 2026): a major accessibility-overlay vendor ordered to pay one million dollars for falsely claiming its tool could make any website WCAG compliant.
- UsableNet / AudioEye web accessibility litigation reporting, 2025-2026 (accessed July 2026): a substantial share of US web accessibility lawsuits in 2025 targeted sites that had an overlay widget installed.
- European Accessibility Act, applicable since 28 June 2025; EN 301 549 maps closely to WCAG 2.1 AA (Level Access, OneTrust, accessed July 2026).
- US Department of Justice, ADA Title II final rule adopting WCAG 2.1 Level AA for state and local government web content, 2024.
Begin with where the business stands.
No obligation. The deliverable is a measured starting position and the corrections that move it most.