01
Discovery scan
We run the same axe-core engine plaintiff firms use, plus four additional layers of analysis. You get a prioritized list of every issue, mapped to the WCAG criterion and the templates it touches.
WordPress Remediation
We fix accessibility in your WordPress source code — not with a widget.
If your WordPress site has ADA accessibility issues, Sturdly engineers go into the templates, forms, theme, and content and fix them at the source. You get a re-scanned, documented, and timestamped record of every change — the kind of evidence that actually matters if a demand letter arrives.
What’s included
Every remediation includes the work, the QA, and the record.
- Accessibility scan and prioritized issue review
- Source-level template, theme, and component fixes
- Form labels, names, error states, and validation
- Color contrast, focus order, keyboard navigation
- Image alt text policy and remediation
- Heading structure, landmarks, and ARIA cleanup
- Human QA across key user flows on desktop and mobile
- Post-remediation scan and timestamped change log
What we don’t do
The shortcuts we refuse to take.
- Overlay widgets or runtime patches
- Compliance certifications or legal guarantees
- Promises that you won't be sued
An accessibility overlay is a floating JavaScript widget that claims to fix compliance at runtime. It can’t. The FTC fined accessiBe $1M in 2024 for that exact claim. Real remediation changes the site itself.
The process
Scan, scope, fix, verify. Done by the same team. Logged at every step.
02
Scope and quote
We separate WCAG-critical fixes from lower-value noise and quote the remediation against a fixed price. If the site needs more than remediation (full rebuild, custom rebuild on a new theme), we say so.
03
Source-level fixes
Engineers work directly in your WordPress source — templates, theme functions, page builder blocks, forms, content. Every change is committed and logged.
04
Human QA + re-scan
Real humans test the fixes with a screen reader and keyboard across your key flows. We re-run the scan to confirm the issues are actually gone, and you get a timestamped report of what changed.
Pricing
Fixed-price remediation, starting at $4,500.
Most small-to-mid WordPress sites land between $4,500 and $9,500 depending on template count, plugin complexity, and how broken the existing accessibility patterns are. Enterprise / custom scope is quoted separately. See the full breakdown on the pricing page, or talk to us about your specific site.
Remediation, in plain English.
- How long does WordPress remediation take?
- Most small-to-mid sites finish in 2–4 weeks of calendar time. Sites with heavy page builders, custom WooCommerce, or membership/portal logic take longer because each unique template needs its own pass.
- Will remediation guarantee I won't be sued?
- No. No one can promise that — and anyone who does is lying. Remediation reduces real-world risk by removing the specific issues plaintiff firms cite, and gives you a documented good-faith record if a demand letter does arrive.
- Why source-level fixes instead of an accessibility widget?
- Overlay widgets sit on top of your site at runtime. They can't rewrite broken HTML, restructure forms, or repair a checkout flow that traps keyboard users. The FTC reached a $1M settlement with accessiBe in 2024 over claims their widget was a compliance solution. We change the underlying site.
- Do you work on non-WordPress sites?
- Our specialty is WordPress and WooCommerce because that's where most small-business ADA exposure lives. We've done Shopify and headless React sites case-by-case — contact us with the URL and we'll tell you whether we're the right fit.
- What if my site needs a full rebuild?
- Sometimes the underlying theme is so broken that remediating it costs more than rebuilding. We say so directly. Enterprise/custom scope handles full rebuilds — talk to us about your site and we'll tell you which path makes sense.
- Can my developer use the fixes you make?
- Yes. Every change is committed to your repo (or delivered as a structured changelog if you don't use Git), so your team can review, deploy, and maintain it after we're done.
Ready to fix it at the source?
Tell us about your WordPress site. A real engineer reads every submission and replies within one business day. No sales chatbot, no calendar trap.
Prefer email? support@sturdly.com