Our team identified a critical gap in our product suite: our lack of accessibility compliance was creating barriers for users with disabilities and limiting our market potential. Specifically, we recognized that our survey tool, Questions, wasn't meeting WCAG 2.1 AA standards, which meant we were excluding users with accessibility needs and potentially missing out on customers who required compliant tools.
We took collective ownership of this challenge by partnering with accessibility consultants to conduct a comprehensive audit of our most-used product. Rather than applying surface-level fixes, our team championed a complete rebuild of our core components using an accessibility-first approach. This wasn't just about compliance—we saw an opportunity to establish organization-wide accessibility processes that would prevent these issues in the future.
Our collaborative work resulted in successfully achieving AA compliance, but we didn't stop there. We validated the real-world usability of our improvements by conducting testing with users from Blind Low Vision NZ, ensuring our solution actually worked for the people we were trying to serve. This validation step was crucial to our team because technical compliance doesn't always translate to genuine usability.
Through this project, we not only solved our immediate accessibility challenges but also positioned our organization to be more inclusive and competitive in markets that require accessibility compliance.
This version maintains the strategic thinking and user-centered approach while emphasizing the team's collective effort and shared ownership of the challenge.
Recognizing that our internal team needed specialized expertise, we initiated a partnership with accessibility consultants to conduct a thorough WCAG 2.1 compliance audit. Our team participated actively in user testing sessions and expert evaluations to understand the real impact of our accessibility gaps.
Through our collaborative research, we uncovered several critical insights that shaped our approach:
The specific pain points we documented included poor keyboard navigation, missing ARIA labels, inadequate color contrast, and completely inaccessible form controls—issues that were creating real barriers for users with disabilities.
Rather than trying to tackle everything at once, our team made the strategic decision to focus on Questions, our survey tool, as it was our most-used product.
Our thinking was that by demonstrating successful accessibility improvements here, we could establish proven processes and build organizational confidence for broader application across our entire product suite.
Our team immersed ourselves in established accessibility resources, drawing heavily from the UK Government Design System and W3C Accessibility Pattern Library. This collaborative research informed our approach and ensured we were building on proven best practices rather than inventing solutions from scratch.
Our team evaluated existing design system components against accessibility standards and collectively made the strategic decision to rebuild from scratch rather than retrofit. This approach ensured we could create scalable accessibility improvements across the entire product suite.
Working together, we created new design system components with an accessibility-first approach. Our design and development team focused on building proper semantic structure, intuitive keyboard navigation patterns, and comprehensive screen reader compatibility.
We leveraged established patterns from government and W3C accessibility libraries as a foundation, ensuring we maintained visual consistency while prioritizing functional accessibility for all users.
Our process shifted from traditional siloed work to close collaboration between designers and front-end engineers.
Together, we focused on critical implementation details:
This collaborative approach ensured that accessibility considerations were embedded throughout our design and development process, rather than being an afterthought.
Our team worked closely with accessibility consultants to conduct a comprehensive professional WCAG 2.1 audit. We scoped this evaluation to cover our full product against AA compliance standards, and together we identified critical accessibility barriers and prioritized our remediation efforts based on impact and feasibility.
Throughout development, our team maintained an iterative testing approach, conducting continuous screen reader and keyboard navigation testing to catch issues early and ensure our improvements were working as intended.
We organized user testing sessions with members of Blind Low Vision NZ, working directly with users who had visual impairments and extensive screen reader experience. Our team wanted to ensure that our technical compliance translated into real-world usability.
The feedback from these sessions was encouraging: we found that almost all question types achieved high usability, and the remaining issues had clear, actionable fixes that our team could implement. Most importantly, we validated that our accessibility improvements were creating genuinely usable experiences for the people we were designing for.
As a team, we achieved several key outcomes:
Together, our team delivered a comprehensive accessibility transformation:
The collaborative effort produced significant outcomes across multiple dimensions:
This project demonstrated that when we prioritize accessibility from the ground up, we create better experiences for everyone while building a more inclusive and competitive product.