I will audit and fix your website for WCAG 2.2 and ADA accessibility compliance

I will audit your website against WCAG 2.2 and ADA standards, then fix the real code so screen readers, keyboards, and assistive tech actually work — no checklist theater.

What you get

• A full manual and automated accessibility audit of your live site, measured against WCAG 2.2 Level AA (the current legal benchmark referenced by ADA Title III and Section 508).
• A prioritized findings report: every issue mapped to its specific WCAG success criterion (e.g. 1.4.3 Contrast, 2.1.1 Keyboard, 4.1.2 Name/Role/Value), with severity, the exact element/page, and a plain-English explanation of who it blocks.
• Actual code fixes committed to your codebase or delivered as patches — not just a list telling you what's broken. I correct the HTML, ARIA, focus management, contrast, and markup myself.
• Keyboard-only navigation testing: tab order, visible focus indicators, skip links, and no keyboard traps.
• Screen reader testing with real assistive tech (NVDA on Windows, VoiceOver on macOS/iOS) so labels, roles, and announcements are verified by ear, not just by a linter.
• Color contrast analysis for text, UI components, and graphical objects, with corrected values you can drop into your design tokens.
• Form accessibility: associated labels, error identification, required-field signaling, and inline validation that assistive tech can read.
• Semantic structure cleanup: correct heading hierarchy, landmark regions, list markup, and reading order.
• A re-test pass after fixes to confirm the corrected criteria now pass, plus a short summary you can keep on file as evidence of remediation effort.
• A maintenance cheat-sheet so your team stops reintroducing the same issues.

Plans

	Basic	Standard	Premium
Audit depth	Up to 5 key pages/templates	Up to 15 pages/templates	Full site or app, all unique templates
WCAG 2.2 level	A & AA review	A & AA review	A, AA & selected AAA
Automated scan	Yes	Yes	Yes
Manual keyboard testing	Yes	Yes	Yes
Screen reader testing	Core flows	Full flows	Full flows + mobile (iOS/Android)
Code fixes included	Critical issues	Critical + serious issues	All findings remediated
Findings report	Yes	Yes	Yes + executive summary
Re-test after fixes	—	One pass	Two passes
VPAT / conformance statement draft	—	—	Yes
Revisions	1	2	Unlimited within scope

How it works

1. Share access. You send me the URL(s) and, where you want code fixes applied, access to the repo, CMS, or theme files. We agree on which pages and user flows are in scope.
2. Audit. I run automated tooling (axe-core, Lighthouse, contrast analyzers) to catch the broad strokes, then do the manual work that automation can't: keyboard-only navigation, screen reader passes, zoom/reflow at 400%, and reduced-motion checks.
3. Report. I deliver the findings document — every issue tied to a WCAG 2.2 criterion, ranked by severity and user impact, with a clear recommendation for each.
4. Fix. I implement the corrections directly: semantic HTML, correct ARIA, focus management, label associations, contrast adjustments, and skip navigation. You get a PR, patch, or updated files depending on your setup.
5. Re-test. I verify the corrected criteria now pass and update the report so you have before/after evidence.
6. Handoff. I walk you through what changed, why, and how to keep it accessible going forward.

Why choose this

Most "accessibility audits" are a raw automated scan exported to PDF. Automation reliably catches only a portion of WCAG failures — the rest (logical focus order, meaningful alt text, sensible screen reader announcements, keyboard operability of custom widgets) require a human who actually uses assistive tech. I do both, and I fix what I find instead of leaving you a homework assignment.

I work against the current WCAG 2.2 success criteria, including the newer ones like Focus Not Obscured (2.4.11), Dragging Movements (2.5.7), and Target Size (2.5.8) that older audits miss entirely. Fixes are written to be standards-correct and framework-friendly (plain HTML/CSS, React, Vue, WordPress, Shopify, and similar), so they survive your next deploy.

Who it's for / use cases

• Businesses reducing legal exposure. ADA web accessibility demand letters and lawsuits target sites that fail WCAG. A documented audit plus genuine remediation is your strongest good-faith position.
• Agencies and dev teams that need an accessibility specialist for a client project without hiring full-time.
• SaaS and e-commerce companies whose checkout, signup, or dashboard flows must work for every user — including keyboard and screen reader users who otherwise abandon.
• Public-sector and education sites needing Section 508 / WCAG-aligned conformance.
• Procurement teams that require a VPAT or conformance statement before a deal can close.
• Anyone who ran an automated scan, got a wall of errors, and needs someone to actually resolve them.

FAQ

Q: Can you guarantee my site is 100% ADA compliant or lawsuit-proof? No honest professional can. The ADA has no single fixed technical checklist, and "compliance" is judged against WCAG conformance. I bring your site into measurable WCAG 2.2 AA conformance for the agreed scope and document the work — which is exactly the evidence that matters. Anyone promising a legal guarantee is selling you something they can't deliver.

Q: Do you only report problems, or do you actually fix them? I fix them. The report is the starting point; remediation is the core of the service. The amount of code fixing included scales with the plan you choose.

Q: What's the difference between an automated scan and your audit? Automated tools flag a meaningful but limited slice of issues and produce false positives. The hardest, most user-blocking problems — focus order, screen reader announcements, keyboard traps, meaningful alt text — need manual testing with real assistive technology, which is what I do.

Q: Which platforms and frameworks can you work with? Static HTML/CSS/JS, React, Vue, Angular, WordPress, Shopify, Webflow, and most CMS themes. If your stack is unusual, message me first and I'll confirm before you order.

Q: How long does it take? It depends on page count and how much remediation is needed. A small Basic audit is quick; a full Premium remediation of a large app takes longer. I give you a realistic timeline once I've seen the site's scope.

Q: Will the fixes change how my site looks? Accessibility fixes are usually invisible to sighted users — better markup, labels, and focus states. Where a change is visible (a contrast adjustment or a focus outline), I flag it first and align it with your brand.

Q: Can you provide a VPAT or conformance statement? Yes, a drafted VPAT / conformance statement is included in the Premium plan and reflects the actual tested scope — not a rubber-stamp.

Q: What do you need from me to start? The page URLs in scope, and — if you want me to apply the fixes — access to your repository, theme, or CMS. The more access you provide, the more I can remediate directly rather than hand back as instructions.