How do you handle accessibility and compliance?
We build to WCAG 2.2 AA as standard. This includes semantic markup, full keyboard operability, visible focus indicators, sufficient contrast, labelled form controls and errors announced to assistive technology. Automated checks run in the build pipeline, supplemented by manual testing with a keyboard and screen reader.
Building accessibility in from the start is far more cost-effective than adding it later. Components built on the wrong underlying elements often need to be rebuilt rather than patched.
Accessibility is also a growing legal requirement in many jurisdictions. Organisations selling into regulated sectors or public procurement are frequently asked for a conformance statement.
Wider compliance requirements, such as data protection, sector-specific rules for health or payment data, and data residency, are treated as architectural inputs and identified during discovery.
Where a formally audited certification is required, we explain the process, the external auditor’s role and the associated cost.
Related service
UI/UX Design & Product StrategyUser research, information architecture and design systems ready for development.
Was this helpful?