We bring accessibility into discovery, design, build and assurance. Our teams use WCAG 2.2 AA as a reference where appropriate, combine automated and manual checks, and include disabled people in research when feasible. We do not represent this as a certification.
Questions, clearly answered
Useful answers for careful decisions.
Find out how we approach accessible delivery, integration and long-term service support.
We begin by understanding what data is genuinely needed, map its movement and apply proportionate controls such as role-aware access, secure transport, auditability and limited retention. Specific arrangements are agreed with each client.
Yes. We map source-of-truth boundaries, data quality and operational needs before selecting integration patterns. We work with documented APIs and other suitable interfaces rather than assuming one platform fits all.
Scope, governance and integration complexity shape timelines. We usually begin with a bounded discovery and a delivery plan, then work in reviewable increments with clear decision points.
Yes. We inventory and prioritise content, agree ownership, rewrite where needed and validate the migration against a content model and accessibility requirements.
We design clear, staged information and consent journeys with version awareness, participant choice and accessible routes to ask questions or change preferences. Client research governance remains in control.
We design content structures and interfaces ready for translation, including expansion, language switching and right-to-left considerations where relevant. Translation is planned with the service, not added as a last-minute layer.
Yes. We tailor working sessions and handover materials for service, content, engineering and assurance teams so the work can be maintained after delivery.
Support is agreed to fit the service, including operational guidance, incident triage, accessibility follow-up and planned improvement. See the Support centre for routes and response context.
Hosting depends on the client’s architecture, procurement and data requirements. We help assess options and document responsibilities; we do not claim a single hosting arrangement or certification.
We can support early requirements, delivery scoping and procurement documentation. Engagement route and any framework availability are confirmed case by case; no procurement status is implied.
We do not add AI by default. Any proposed use is assessed for need, data exposure, explainability, human oversight and potential harms; the client decides whether it is appropriate.