Before/After: Accessibility-First Redesign for a Telehealth MVP

Design · 6 min read

MediMeet built a barebones telehealth MVP tested primarily with neurotypical users. Feedback from a small accessibility beta exposed critical barriers: low-contrast controls, tiny touch targets, and modal dialogs that broke keyboard navigation. The product team chose an accessibility-first path for the next sprint rather than a piecemeal fix.

Key decisions included adopting WCAG AA color tokens as defaults with theme toggles, increasing touch-target sizes and spacing, and reworking modal flows to maintain focus order. The team also added descriptive aria labels and a simplified appointment flow that reduced required fields for callers using assistive tech.

Within two months of release, sessions from assistive-technology users tripled; completion of scheduled appointments rose from 62% to 84% among that cohort. Developers reported fewer edge-case bug reports because the new component library enforced accessible patterns. The product team kept the redesign modular to avoid slowing feature delivery for other users.

MediMeet’s story shows that accessibility is not a feature sprint—it’s a product design stance. Starting with inclusive defaults reduces long-term technical debt and expands the usable audience, often with measurable gains in satisfaction and retention.