Digital Experience
Assessment against WCAG 2.2 AA using assistive technology as well as automated tooling, because automated checks find roughly a third of real barriers and none of the ones that matter most.
Stated as we hear it, before any mention of what we would do about it.
Qualitative, because we do not publish numbers we cannot evidence.
Scope
Three to five weeks depending on the number of distinct templates and flows.
The boundary
Naming the boundary early removes the most common source of disappointment in an engagement.
No. Automated tools reliably find contrast and missing labels but cannot judge whether a heading structure makes sense, whether focus order follows the visual flow, or whether an error message is announced. Those require manual testing.
We can assess conformance and guide remediation. Nobody can certify compliance, because conformance is assessed against real use and changes with every content update. Any claim otherwise should be treated with suspicion.
Assessment against WCAG 2.2 AA using assistive technology as well as automated tooling, because automated checks find roughly a third of real barriers and none of the ones that matter most.
Organisations with procurement or regulatory accessibility requirements; Teams whose site has never been tested with assistive technology; and Businesses that want the statement they publish to be true
Automated scanning as a first pass, treated as coverage rather than as the answer; Manual testing: keyboard only, screen reader, zoom to 400%, reduced motion; Assessment against WCAG 2.2 AA with the failing criterion named per finding; Severity ranked by impact on a user completing a task, not by rule count; Remediation guidance specific enough to implement; and Support in drafting an accessibility statement that reflects reality
An accessibility statement is required and nobody knows what is true; A complaint or procurement question has raised the issue; and An automated scanner reports a clean pass that nobody believes
A defensible picture of conformance, with severity by user impact; Findings written so a developer can act on them without interpretation; and Evidence that supports an honest accessibility statement
Three to five weeks depending on the number of distinct templates and flows.
Connected
Describe where the work currently is and what it has to achieve commercially. We will tell you what we would scope, what we would leave alone, and whether this is the right service to be buying first.
