Frequently asked questions
Questions about accessibility audits and assurance.
Practical answers about scope, testing, evidence and the limits of an audit.
Choosing a service
Questions about scope, timing and the right engagement for your team.
What do you need before testing begins?
We agree the authorised targets, priority journeys, environments, test accounts, constraints, evidence requirements and activities that are out of scope.
Can you work with our release cycle?
Yes, when continuous assurance is the right engagement. Cadence, environments, journey coverage and review checkpoints are agreed before work starts.
How long does an engagement take?
Timing depends on the number of templates, journeys, environments and review cycles in scope. We confirm a delivery plan after the authorised targets and access requirements are understood.
Can you test authenticated or pre-release services?
Yes, when access, test accounts, environments and data-handling constraints are agreed in advance. Testing remains limited to the authorised scope and activities.
Testing
How automated checks, manual procedures and journey testing work together.
Is automated testing enough?
No. Automated checks help with repeatable discovery. Manual procedures, journey testing and human review are required to interpret impact and cover behaviour automation cannot determine reliably.
Does an audit certify WCAG conformance?
No. An audit records evidence within an agreed scope and at a point in time. It is not legal advice, certification or a guarantee that every barrier has been found.
Which browsers, devices and assistive technologies are covered?
Desktop and mobile coverage is agreed for each engagement. Browser and assistive-technology combinations are selected for the service, its users and the decisions the evidence must support.
How are possible false positives handled?
Automated observations are reviewed before they become confirmed findings. Where evidence is incomplete or context-dependent, the item remains marked for review rather than being presented as a confirmed failure.
Results and remediation
What your team receives and how to interpret the recorded evidence.
What will our delivery team receive?
The agreed handoff can include an HTML report, structured spreadsheet, evidence-linked findings, remediation direction, a stakeholder readout and retest status. Report accessibility is reviewed against the agreed delivery requirements.
How is the accessibility score used?
It is a directional signal for the tested scope, not a compliance percentage. Decisions should use the reviewed findings, coverage and documented limitations alongside the score.
Can developers discuss findings before remediation?
Yes. The handoff can include a review session to clarify impact, reproduction steps and remediation direction before work begins.
What happens after a fix is submitted?
Agreed fixes are retested against the original conditions and evidence. The result records whether the issue is verified, still present, changed or blocked from retest.
Plan the next step