Web Accessibility Compliance

We start by defining the target level of compliance (AODA, WCAG 2.1, Section 508) and the strategies to meet those requirements. Our UX/UI design team applies the POUR principles (Perceivable, Operable, Understandable, Robust) to ensure interfaces are intuitive and barrier-free, and all of our developers are trained in the latest accessibility standards and use licensed tools to identify and remediate accessibility faults as they code.

Every solution is then iteratively tested for accessibility, usability, and security prior to launch with training, monitoring, and strategic guidance provided post-launch to help your team maintain accessibility over the long term.

Our work with the Government of Ontario in Canada on the Fourth AODA Legislative Review is one example: in just four weeks, we delivered a fully bilingual, WCAG AAA-compliant website that facilitated public feedback, supported policy discussions, and met the needs of persons with disabilities province-wide.

It would be underselling to consider accessibility deliverables in isolation, since it runs like a red thread throughout all that we deliver but notable outputs of our engagements include:

• Demonstrably accessible UX/UI designs.
• Semantic HTML, ARIA roles, keyboard navigability, and screen reader compatibility.
• Automated and manually produced accessibility testing reports.
• Accessibility audits and remediation reports.

Raising the standard for accessibility starts with a simple conversation.