Accessibility Services,
Explained Plainly
Every service we offer is described below in plain language — what it is, what it delivers, and why it matters legally. We do not use jargon to obscure what you are buying.
Compliapoint works on WordPress (including WooCommerce) and Shopify sites.
Why Source-Level Fixes Are the Only Fixes That Count
There are two ways to approach website accessibility. One of them works. The other creates the appearance of compliance while leaving actual violations in place.
❌ The Overlay Approach
- A JavaScript widget runs on top of your existing HTML
- Attempts to patch accessibility at render time in the browser
- The script guesses at what your content means; the violations stay in your code
- In 2025 the FTC ordered accessiBe to pay $1 million over its accessibility claims
- accessibility professionals signed a public statement against overlays
- In 2024, 1,023 companies sued over web accessibility had a widget live on their site (UsableNet)
- Cancel the subscription and every apparent "fix" disappears immediately
- Does not produce a legally defensible record of compliance
✓ The Source Remediation Approach
- Violations are fixed in your actual HTML, CSS, and template files
- Screen readers and assistive technologies interact with corrected code
- Fixes live in a child theme, a site-specific plugin, or your Liquid source — never in files an update overwrites
- No runtime dependency — works without any script running
- Every fix is documented with before/after evidence
- A complete audit trail exists if your compliance is ever challenged
- A dated accessibility test record is issued upon completion
- One-time project cost — not a recurring subscription masking unresolved problems
We wrote the software. That’s why we can answer for it.
Most firms run someone else’s scanner and forward you the output. Ask how a finding was reached, or why a page passed, and the honest answer is that they don’t know — the tool doesn’t say. We built ours: the scanner, the evaluation engine, the reports. Every answer has a source.
Findings name the rule, not a grade
No score out of a hundred. Each issue is reported against the WCAG success criterion it fails and that criterion’s level — so your developer knows what to change, and your counsel knows what it means.
Nothing is quietly skipped
Every Level A and AA success criterion is covered, each by an automated check or a reviewer’s question. The software will not report a site clean on a criterion nobody examined. It stops and says so instead.
We follow the W3C’s own method
Defined scope. Structured exploration. A deliberate sample and a random one. Then a comparison step that tests whether the sample was representative — and sends us back for more pages when it wasn’t. That last step is what makes a sample mean anything.
Your report can be proven genuine later
When an evaluation completes, the evidence is sealed and fingerprinted, and the report carries that fingerprint. A record altered afterwards cannot pass as the original — the difference between a document and evidence, on the day someone asks you to prove what you were told and when.
The documents buyers actually ask for
VPAT and ACR in the WCAG, Section 508, EN 301 549 and International editions, and a conformance claim that names exactly which pages it covers rather than gesturing at “the site”.
And it refuses to overstate. It will not produce a conformance claim the evidence doesn’t support, call a site conformant on criteria nobody checked, or put a standard’s name on a report that didn’t follow it. Those refusals are deliberate — a document you cannot defend is worth less than no document at all.
Every Service, Fully Explained
A Complete Package is the audit, remediation, deliverable report and 30-day recheck bought together — $4,750, $9,995 or $19,995 by site size. The lower prices below marked ‘within a Complete Package’ apply within one.
What It Is
A WCAG 2.2 evaluation of the distinct screens of your website, with their images, links, forms, tables, video, PDFs and interactive elements. We test against the success criteria at Levels A and AA, the level the DOJ’s Title II rule, Section 508 and EN 301 549 name.
We audit by template, not by URL. A WordPress site with 400 posts does not have 400 distinct accessibility problems; it has one archive template, one single template, a handful of builder layouts and whatever the plugins emit, repeated 400 times. A Shopify store is the same story across product, collection, cart, search and page templates plus the theme’s sections and snippets. We enumerate the templates, test every unique one, and tell you how many live pages each finding actually affects — which is what makes a fixed price possible.
What You Receive
- Full written audit report organized by page and issue type
- Every issue listed with its WCAG criterion and severity level
- Screenshots and code examples for every identified failure
- Remediation recommendations for every issue
- Findings mapped to the template, theme file, plugin or app that produces them
- A count of how many live pages each finding affects
- Executive summary suitable for leadership review
Why It Is Always the Starting Point
Without an audit, there is no reliable way to scope remediation. Anyone who offers to "fix your accessibility issues" without first documenting exactly what is broken is guessing — and guessing does not produce a defensible compliance record. The audit is the foundation of everything else.
What It Is
We go into your site's actual source files — HTML templates, CSS, JavaScript, and theme files — and correct the issues identified in the audit, in the pages, templates and components covered by your written scope. This is not a script applied on top of your site. These are structural changes to the code itself.
Where the fix goes matters as much as the fix. On WordPress we work in a child theme or a small site-specific plugin, never in parent theme files, because the next theme update overwrites them. Markup produced by a third-party plugin is corrected through that plugin’s own filters and hooks where they exist, and where they do not, in a site-specific plugin that adjusts the output — never by editing a plugin you still need to be able to update. On Shopify we work in your theme’s Liquid sections and snippets and hand back the exact diff, so replacing the theme later is a re-apply you can see. Markup injected by a Shopify app sits outside your theme; we identify it, tell you which app produces it, and say plainly whether it can be fixed or needs replacing.
What You Receive
- All audit violations corrected in source code
- Before/after documentation for every fix
- Tested against major screen readers (NVDA, JAWS, VoiceOver)
- Keyboard navigation verified across all interactive elements
- Color contrast corrections applied where needed
- ARIA roles and landmark regions properly implemented
- Form labels, error messages, and focus management corrected
What It Does Not Cover
Remediation addresses violations found in the audit. It does not automatically cover new pages added after the project, new features added post-remediation, or PDFs and video (those are separate services). This is why Accessibility Monitoring exists.
What It Is
Every PDF document hosted on your site must be tagged with a logical reading order, proper heading structure, alternative text for images, and navigable bookmarks so that screen readers can process them correctly. An untagged PDF is functionally inaccessible to a blind user regardless of what the rest of your site does.
What You Receive
- Documents in scope tagged with semantic structure
- Reading order corrected to match visual layout
- Images within PDFs given appropriate alternative text
- Form fields in fillable PDFs made keyboard-accessible
- Document language and title metadata set correctly
What It Is
WCAG Success Criterion 1.2.2 requires captions for all prerecorded audio and video content at Level A — the most basic required conformance level. We provide accurate, synchronized captions for your video content.
Delivery differs by platform. On WordPress, SRT and VTT files attach directly to the core video block. On Shopify they cannot: the native video_tag filter emits no track element, so captions have to be wired through a theme-level video element or an external player that supports them. We do that wiring rather than handing you files that will not load.
What You Receive
- Accurate captions synchronized to audio
- Files delivered in SRT and VTT formats for any platform
- Speaker identification included for multi-speaker content
- Sound effects and relevant non-speech audio noted
What It Is
A Voluntary Product Accessibility Template (VPAT) — formally called an Accessibility Conformance Report (ACR) — is a standardized document that describes how your site conforms to WCAG and Section 508 criteria, criterion by criterion. It is the standard format expected by government purchasing officers, university procurement teams, and enterprise vendor qualification processes.
Who Requires It
- Vendors to federal agencies, under Section 508 procurement rules, and to state and local agencies whose own law or contracts adopt it
- Vendors to universities and federally funded institutions
- Enterprise software and SaaS vendors responding to procurement RFPs
- Organizations required to demonstrate compliance to clients or partners
What It Is
An Accessibility Statement is a published page on your site that declares your organization's commitment to accessibility, identifies the standard you are conforming to, describes any known limitations, and provides a contact method for users who encounter barriers. It is the public-facing description of your accessibility commitment.
Why It Matters
Several U.S. state accessibility laws explicitly require a published accessibility statement. Courts and regulators view its presence as evidence of good faith. Its absence, conversely, can be used to demonstrate that no effort was made. After remediation, publishing an accurate statement is straightforward. The Accessibility Statement is included with every audit — we draft one that is accurate, complete, and legally appropriate.
A statement is also where platform limits belong. If you are on Shopify, your checkout is Shopify’s code and no vendor can remediate it; saying so is both accurate and protective, and it is the opposite of what an overlay vendor’s badge implies. We draft yours naming your platform, your theme, and the known limitations that genuinely apply to you.
What It Is
A dated record of exactly what we tested, what we found and what we changed, against WCAG 2.2 AA. It identifies the scope of work, the standard applied, the platform and theme versions in place on the test date, the date of completion, and the issuing party. It states what was verified rather than certifying an outcome no one can guarantee.
Where It Is Used
- Legal defense — demonstrates documented due diligence
- Enterprise sales — included in vendor qualification responses
- Government contracts — supports Section 508 compliance representations
- Client-facing credibility — published or shared on request
- RFP responses — answers "do you have documented accessibility compliance?"
What It Is
A comprehensive written record of the entire engagement: every issue identified in the audit, every fix applied during remediation, the methodology used, tools employed, and what testing found on your site at project completion.
Why It Matters
If your accessibility is ever challenged in litigation, a regulator review, or an enterprise audit, the Deliverable Report is your documented evidence that remediation was performed properly and completely. It is not a summary — it is a full technical record. Organizations that cannot produce this documentation in a legal context are at a significant disadvantage.
What It Is
A recurring monthly scan of your site against WCAG 2.2 AA standards, delivered as a written report identifying any new violations that have appeared since the last scan. Accessibility degrades naturally over time as content is updated, pages are added, plugins are changed, and themes are modified.
What You Receive Monthly
- Full re-scan of your site against WCAG 2.2 AA
- Written report of any new issues identified
- Categorized by severity
- Remediation recommendations for any new failures
- Option to add remediation as a separate project if issues are found
When It Makes Sense
Organizations that publish new content frequently, operate e-commerce platforms with changing product pages, or operate in regulated industries where ongoing compliance documentation is required will benefit most from monitoring. It is not necessary for static sites that rarely change.
On WordPress and Shopify the trigger is rarely new content — it is an update. A plugin auto-updates and re-emits the markup we corrected. A theme upgrade replaces the files a fix lived in. A newly installed app injects its own unlabeled controls. Monitoring exists to catch those the month they happen rather than the day a demand letter arrives, so our reports name which update introduced a finding, not just that one appeared.
What It Is
Rush Processing moves your engagement to the front of the queue and commits to delivery within 1–3 business days. Standard turnaround is 7–10 business days.
When It Is Appropriate
- You have received an ADA demand letter with a response deadline
- You have an upcoming product launch or site deployment
- You have a government contract audit or certification deadline
- An enterprise client has required compliance documentation by a specific date
- You are responding to an RFP with a submission deadline
Rush Processing applies to the entire engagement scope. It is $638 ($600 within a Complete Package), whatever the size of the project.
What It Is
After your team applies remediation fixes — whether your own developers or an outside contractor — we re-test every corrected issue and record the result.
Why It Matters
An accessibility test record can only state that issues were resolved once they have actually been verified as resolved. Validation Testing is the step that bridges the gap between "we fixed it" and documented, defensible proof that the fixes held. Without it, the record has no evidentiary foundation.
When You Need It
- Your development team completed their own remediation from our audit report
- You hired an outside contractor to apply fixes and need independent verification
- You need a dated accessibility test record but did not use Compliapoint for remediation
What It Is
Direct access to our accessibility specialists for developer Q&A, fix validation, remediation guidance, and compliance strategy. Billed in one-hour increments at $166/hour ($156/hour within a Complete Package) with a one-hour minimum.
When It Is Useful
- Your development team is applying their own fixes and needs expert review of specific implementations
- You want clarification on audit findings before your team begins remediation
- You need strategic guidance on prioritizing which issues to fix first given a limited budget or deadline
- You want a second opinion on a remediation approach before committing development resources
Consulting hours do not replace a full audit or remediation engagement — they support teams who are doing the work themselves and need specialist guidance along the way.
Not Sure What You Need?
Complete the five-minute Site Accessibility Assessment. We review your answers and your site, then send a written proposal identifying exactly what applies to your situation — no obligation until you approve it.