Part III: Design Patterns Library

Accessibility as Baseline

Designing for all abilities in healthcare
View as Markdown

Accessibility in healthcare is not optional. Health apps serve users across the full spectrum of ability — including many who are older, have visual or hearing impairments, or experience cognitive challenges due to their health conditions.

WCAG 2.2 Compliance in Health Contexts

The Web Content Accessibility Guidelines provide the technical standard:

LevelRequirementHealth-Specific Consideration
AEssential complianceKeyboard navigation for all health data entry
AATarget for most health appsColor contrast, captions for health video content
AAABest practiceSign language interpretation for critical health information

Designing for Aging Populations

Health apps disproportionately serve older users:

  • Larger text: Minimum 16px body text, offer text size controls
  • High contrast: Ensure readability in varied lighting conditions
  • Simple navigation: Avoid complex hierarchies and jargon
  • Touch targets: Minimum 48x48px for all interactive elements
  • Voice input: Support dictation for data entry
  • Patience: Allow extra time for task completion, no time-out pressure

Visual Accessibility

Health data visualizations must work without color reliance:

  • Colorblind-safe palettes: Don’t use red/green alone to convey meaning
  • Pattern differentiation: Use patterns and textures in addition to color
  • Screen reader compatibility: All health data must have text alternatives
  • Zoom support: Content must remain usable at 200% zoom

Cognitive Accessibility

Health information is complex. Make it accessible:

  • Clear language: Health literacy considerations (see Patient-Centered Design)
  • Consistent layout: Predictable navigation across all sections
  • Error prevention: Prevent mistakes rather than just highlighting them
  • Help and support: Contextual help available at points of confusion
  • Focus management: Guide users through complex multi-step health workflows