Services
Accessibility work, described precisely
Every service below states what it covers and what it doesn't. Findings and statuses always attach to a defined scope, methodology, and date — never to a website "in general, forever."
Website Accessibility Audit
A structured assessment of your website or digital property against identified WCAG 2.2 Level AA criteria, combining:
- Automated testing — axe-core-based tooling running WCAG 2.1 Level AA rules (plus the 2.2 target-size check) to catch machine-detectable issues quickly across the scope.
- Manual testing — expert review of structure, semantics, labels, contrast, focus management, and content that automation cannot judge.
- Keyboard testing — every in-scope flow operated without a mouse, checking for traps, skipped stops, and invisible focus.
- Screen-reader testing — evaluation with assistive technologies such as NVDA, JAWS, and VoiceOver; each report documents the environments actually tested.
- User-flow testing — the journeys that matter (search, forms, checkout, account) tested end to end.
- Component and template review — shared components audited once, mapped to everywhere they appear.
- Issue prioritization — findings ranked by user impact and remediation effort, with code-level recommendations and screenshots.
Limitations, stated up front. An audit covers the defined scope as of the testing dates. It does not cover pages, states, or content outside the scope; changes made after testing; or every combination of browser, device, and assistive technology. Automated testing alone does not establish WCAG conformance.
Remediation Commitment Program
For organizations formally beginning a remediation program that needs to be documented while it happens — not just after. Getting started is simple, and most of it happens in a single onboarding conversation:
- A signed agreement (we send it; you e-sign)
- A short intake questionnaire about your website
- An agreed list of what's covered — your pages and platform
- A point of contact on your side
- A remediation plan with milestones (we draft it with you)
- Staying in the program, with periodic status check-ins
Onboarding is deliberately lightweight, and the record is often filed the same day onboarding is completed. The record is filed in the Accessibility Registry as "Remediation on record" and updated to "Verified" once our retest of the defined scope passes; verified records run for a 12-month term. A record cannot reach "Verified" on payment alone, and it is kept current only while the program continues. If a program is abandoned, or the record would otherwise become misleading, we correct or withdraw it, and the registry continues to show its history.
Accessibility Remediation
- Code-level remediation when access is provided — we fix markup, styles, scripts, and components directly. Supports Shopify, Wix, WordPress, Squarespace, Webflow, BigCommerce, and custom builds.
- Developer guidance when your team retains implementation control — precise, reviewable instructions per issue.
- Design-system guidance — fixing the source component so the fix propagates.
- Content remediation — headings, link text, alternative text, document structure, and plain-language corrections.
- Third-party component analysis — identifying barriers in embedded widgets and what can and cannot be controlled.
- Quality assurance and retesting — fixes verified with keyboard and screen readers before they're marked resolved.
Defined-Scope Retesting
After remediation, the agreed scope is retested using the stated methodology — keyboard and screen-reader testing included. The result is a dated retest report; when the retest passes, we update the record in the Accessibility Registry to "Verified."
Conclusions are limited to the exact scope and date tested. A retest says: these pages, templates, components, and flows, tested in these environments, against these criteria, on these dates. It does not extend to untested areas or to changes made afterward.
Public Record and Private Report
Public record: the record in the Accessibility Registry — assessed domain, dates, defined scope, methodology, criteria, issue status summaries, milestones, retesting status, known limitations, report identifier, and a hash or identifier associated with the confidential report. Searchable at Verify a Record.
Private report: the full technical report — detailed findings, sanitized evidence, screenshots, and retest results. Provided to the client and, subject to the engagement terms, to authorized counsel, experts, insurers, regulators, mediators, or courts. Never published, and never inserted into the public record.
This structure lets an organization document remediation activity without publishing its proprietary codebase. The public record is not evidence of compliance with any law; it states what work was performed, on what scope, and when.
Ongoing Monitoring
Websites change; accessibility drifts. Monitoring engagements provide periodic automated scans plus scheduled manual checkups at an agreed frequency (commonly monthly or quarterly, set in the engagement), regression reports, and reassessment recommendations after material changes — new templates, redesigns, platform migrations, or significant feature launches.
Monitoring is a service, not a separate record state: its periodic retesting keeps a Verified record current. It does not mean no barriers exist, and it does not make future changes automatically accessible.
Accessibility Statement Services
We develop transparent accessibility statements that say what your organization actually does: the standard you target, the testing performed, known limitations, and a working feedback mechanism for users to report barriers — plus an internal process to respond. A statement that overpromises is worse than none; we write yours to be accurate.
The badge
The registry badge
Clients with a record may display the Accessibility Registry badge. The badge is a short script furnished by the registry, which the client places in the site's footer; it displays the record's current state, links to the record itself, and changes automatically when the record is verified, renewed, or lapses. Apart from presenting that status, it leaves the website's pages, code, and accessibility untouched, and it remediates nothing.
Badge usage terms
- Display only on the website named in the record.
- Do not alter the badge, replace it with a static image, or change where it links.
- The badge describes the record, not the website.
- It must be removed if the record is withdrawn.
The one-line embed and full rules are on the registry's badge page.
Pricing
One program, one price. It covers the audit, remediation of the defined scope, the retest, and the record filed in the Accessibility Registry.
$6,500
Remediation Program — paid once, by card. No proposal cycle: pay, complete a short intake, and onboarding starts the same business day.
- Accessibility audit tested against WCAG 2.2 Level AA, with conformance documented against WCAG 2.1 Level AA
- Code-level remediation of the defined scope
- Retest, and a Verified record on the registry when it passes
- Registry badge for your site
Checkout is by Stripe. You'll accept the Terms of Service at checkout and land on a short intake form afterward.
Larger or more complex sites — many templates, custom applications, multiple domains — are quoted after review. Request a scoped proposal if that's you, or if you'd rather talk first.
Program fees compensate the work performed and the record maintained — they are not contingent on, and are not refundable based on, the outcome or resolution of any legal matter. A record is entered in the registry at the outset of the program; it becomes "Verified" only after a passing retest of the defined scope. Payment alone never results in a Verified record.