Case Studies
Accessibility engineering and full-stack systems delivered in public-sector and mission-driven environments. Each study follows the same structure: problem, stack, challenges, measurable outcomes, and architectural reasoning.
LipSync Connect
Next.js Device Accessibility Platform — Neil Squire Society
A web application enabling users with physical disabilities to control devices via lip and facial movements. Built accessibility-first from the ground up for a non-profit serving Canadians with motor impairments.
The Problem
Neil Squire users required a device-control interface that worked reliably across assistive hardware setups, screen readers, and low-bandwidth environments — with zero tolerance for accessibility regressions.
Technical Stack
Key Challenges
- Ensuring full keyboard navigability across all interaction states
- Building screen reader-compatible real-time feedback for device status
- Maintaining WCAG 2.1 AA compliance across dynamic UI components
- Designing for low-vision, motor-impaired, and switch-access users simultaneously
Measurable Outcomes
Architectural Reasoning
Component architecture designed for progressive enhancement — core functionality works without JavaScript, enhanced interactions layer on top. All ARIA roles and live regions implemented per WAI-ARIA authoring practices.
WCAG Implementation Initiative
Accessibility Compliance Programme — Neil Squire Society
A systematic accessibility audit and remediation initiative across Neil Squire's public-facing web platforms, resulting in measurable compliance gains and improved outcomes for users of assistive technologies.
The Problem
Existing platforms had accumulated accessibility debt across colour contrast, keyboard traps, missing ARIA labels, and non-semantic HTML — creating barriers for the very population Neil Squire serves.
Technical Stack
Key Challenges
- Auditing and categorizing hundreds of accessibility violations across multiple codebases
- Prioritizing remediation by user impact vs. implementation cost
- Training development team on WCAG authoring practices and testing workflows
- Establishing ongoing compliance monitoring and regression prevention
Measurable Outcomes
Architectural Reasoning
Remediation was delivered in priority tiers: critical barriers first (keyboard traps, missing labels), then structural improvements (landmark regions, heading hierarchy), then enhanced interactions (live regions, focus management). Each tier was tested with real assistive technology before sign-off.
Full-Stack Data System
Secure Research Platform — CanAssist, University of Victoria
A full-stack web system for CanAssist's applied research and assistive technology teams, supporting cross-functional workflows, structured data management, and privacy-compliant document handling in a university environment.
The Problem
CanAssist's research teams relied on fragmented tools — spreadsheets, shared drives, and email — creating data integrity issues, access control gaps, and audit trail deficiencies incompatible with academic and government reporting standards.
Technical Stack
Key Challenges
- Designing role-based access control that mapped cleanly to CanAssist's org hierarchy
- Ensuring all data handling aligned with FIPPA privacy standards
- Building audit logging for cross-team document access and modification
- Structuring APIs for long-term maintainability across rotating academic staff
Measurable Outcomes
Architectural Reasoning
System architecture prioritized data integrity and auditability over feature velocity. Every write operation is logged with actor, timestamp, and change delta. Role boundaries are enforced at both the API middleware layer and the database query layer — no client-side permission checks trusted alone.