An audit is only worth what it can be reproduced against. Most hosting quietly makes staging differ from production in exactly the ways that matter.
The work is repeatable measurement, and that requires an environment that does not move under you.
Same PHP version, same plugin set, same caching behaviour. A staging site with caching disabled behaves differently for exactly the interactions that matter to assistive technology.
No overlay widget, no accessibility toolbar, no host-added banner. Those tools are contested, and either way it should be your decision rather than something appearing in the markup.
Layout shift and interaction delay are the vitals that hurt screen reader and keyboard users most, and they are only meaningful measured from real visitors on real connections.
Audits produce artefacts — reports, recordings, VPAT drafts — and those need somewhere durable, not a folder on the laptop of whoever ran the test.
Remediation touches templates and markup, which is exactly the class of change most likely to regress something else. It goes to a clone first.
The argument that ends most accessibility work is somebody being unable to reproduce a finding on their machine. A faithful environment settles that quickly.
Layout shift moves focus out from under a keyboard user. Interaction delay makes a screen reader announce something that has already changed. These are accessibility problems that present as performance numbers.
These differ from a standard WordPress site on the same plan, and each follows from the work being measurement that has to hold up.
| Setting | What we do | Why |
|---|---|---|
| Staging environment | Matched to production including caching behaviour | A staging copy with caching disabled behaves differently for precisely the interactions assistive technology depends on, so findings there do not transfer. |
| Injected scripts | None added by the platform, ever | Overlay and toolbar widgets are contested at best, and whether to use one has to be the site owner's decision rather than something that appears in the markup. |
| Core Web Vitals | Reported from real visitor traffic rather than synthetic runs | Layout shift and interaction delay affect keyboard and screen reader users most, and a lab run on a fast connection does not show either. |
| Audit artefacts | Stored durably alongside the site | Reports, recordings and VPAT drafts are the evidence, and evidence living on one person's laptop stops being evidence when they leave. |
| Remediation changes | Rehearsed on a clone before release | Accessibility fixes touch templates and markup, which is the change class most likely to regress something unrelated. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Free migration, staging that genuinely matches, and nothing injected into your pages.