Skip to content

Quality Engineering

Accessible is testable, and most sites fail

Procurement asks for WCAG conformance evidence, and the deal waits on your answer. A scanner badge won't pass that review. We test the way conformance is judged: criterion by criterion, with assistive technology, on real task flows.

How it’s delivered
  1. 01ScopeSelect flows and pages by user impact and conformance target.
  2. 02AuditAutomated plus expert manual review; every finding evidenced.
  3. 03PrioritizeFindings ranked by user impact and fix cost, mapped to WCAG criteria.
  4. 04RetestVerify fixes and issue an updated conformance summary.

Engineering-led cybersecurity and quality engineering since 2020, delivered by senior security & quality engineers on platforms we build and run ourselves.

Inaccessible products exclude users, fail procurement requirements, and carry legal exposure under accessibility law (ADA, EN 301 549, EAA). Fixing it later costs more than building it in.

What we do

WCAG conformance audits

Assessment against WCAG 2.2 AA: automated scans where machines can judge, expert manual review for the majority of criteria they can't.

Assistive-technology testing

Task completion with screen readers (NVDA, VoiceOver), keyboard-only navigation, magnification, and voice control, exercised on real user flows end to end.

Usability validation

Task-based usability sessions: where users hesitate, backtrack, or abandon, with findings your designers can act on.

Remediation partnership

Prioritized fixes with code-level guidance, then retest and a conformance statement you can share.

Tools & standards

Automated
axe, Lighthouse, WAVE
Assistive technology
NVDA, JAWS, VoiceOver, TalkBack; keyboard-only protocols
Standards
WCAG 2.2 AA, EN 301 549, Section 508

What you receive

  • WCAG 2.2 criterion-mapped audit report with evidence per finding
  • Prioritized remediation plan with code-level guidance
  • Retest verification and conformance summary
  • Usability findings from real task flows

Evidence

How conformance is actually judged

Findings are reported against the specific WCAG 2.2 success criteria your obligation names. Our full methodology is published.

How we deliver →

Engagement

Ways to engage the same senior bench

Buy it as a scoped project, embed it in your team, or run it as a managed service. The engineers and the governance stay the same, whichever shape fits.

Scoped project

A defined piece of work with a fixed outcome (a test suite built, a release hardened, a backlog cleared), delivered by our team and handed over with documentation.

Embedded QE

Our engineers work inside your sprint teams, on your tools and cadence, owning quality alongside your developers.

Managed QE service

We own the discipline as an ongoing service (coverage, execution, and reporting), scaling the bench up or down as your release pressure moves.

Who this is for

  • Products selling into government, education, or enterprise procurement with conformance requirements
  • Teams that ran a scanner, fixed the top ten, and know that isn't conformance
  • Design-led companies that want usability evidence their teams can act on

Common questions

Is an automated scan enough for conformance?

Automated tools catch a minority of WCAG criteria. We combine them with expert manual review and assistive-technology testing (screen readers, keyboard-only) on real task flows, which is how conformance is judged.

Which standard do you test against?

WCAG 2.2 at the AA level by default, the bar most procurement, ADA, and EN 301 549 expectations map to. If your obligation is different, we scope to it and report against the specific success criteria.

Who actually does the work?

Senior engineers from our own team, and the ones who scope your engagement stay on it through delivery. Across the practice, our engineers hold industry certifications spanning ISTQB, AWS, CISSP, CEH, and eCPPT.

In the assurance loop

Accessibility findings get the discipline security findings get. They are remediated, re-checked, and the evidence stays in the release record. See how the loop connects →

Answer the conformance question with evidence

Show us the flows your users depend on and the requirement you're facing. We scope an audit that stands up to the procurement review behind it.