We can produce the evidence, not just the claim.
Every site we build passes an automated WCAG 2.2 AA check before it goes live, and the result is yours to hand to a funder, a board or a grant assessor.
What we commit to
- WCAG 2.2 Level AA as the target for every build, not an upgrade option
- An automated accessibility gate on every build and every publish
- Contrast derived from brand tokens by construction, so illegible text is structurally impossible
- Keyboard navigability and visible focus states
- Alt text required on every image before it can be published
- Semantic landmark and heading structure — which also serves search and AI extraction
Checked on every build, not once at launch
- 01
Automated check on every build
Run as part of the build pipeline. A failure blocks the publish rather than producing a warning nobody reads.
- 02
Manual review of what automation misses
Automated tools catch a portion of issues. Keyboard traps, focus order and meaningful alt text need a person.
- 03
Evidence produced
A report you can attach to a funding application or a grant return.
- 04
Re-checked on every change
Because a site that was accessible at launch and not six months later is not accessible.
What automated testing cannot tell you
Automated accessibility tools reliably catch missing alt text, insufficient contrast, missing form labels and broken heading structure. They cannot tell you whether the alt text is meaningful, whether the tab order makes sense, or whether a screen reader user can actually complete the task.
Any vendor claiming full conformance on the strength of a passing automated scan is overstating it. We run the scan, we fix what it finds, and we review the rest by hand — and we tell you which is which.
Funders and grant bodies increasingly ask about accessibility, and some require a statement. Most website vendors assert conformance in a proposal and cannot produce anything to support it. Being able to hand over a report is a small thing that turns out to matter.
Questions funders and boards ask
Can you provide conformance documentation?
Yes. We produce the automated report and a statement of what was reviewed manually.
What standard do you work to?
WCAG 2.2 Level AA.
Does this apply to content our staff add later?
Yes — that is why alt text is required at publish time rather than requested politely.
What about the 2Labs website itself?
We hold this site to the same standard. See our accessibility statement.
Is automated testing enough?
No, and we do not claim it is. Automated tools catch a portion of issues; keyboard traps, focus order and meaningful alt text need a person.