accessibility at scale - pridemobility website

Oct 2025 - present

Designing an inclusive, WCAG-compliant digital experience for users with diverse abilities.

Pride Mobility’s platforms serve elderly users, individuals with mobility limitations, caregivers, and healthcare providers. Accessibility was integrated as a core usability requirement - not a compliance checkbox. For Pride Mobility, accessibility directly aligned with the needs of its real users.

Why Accessibility Was Critical

Pride Mobility’s audience includes:

  • Elderly users
  • Individuals with visual impairments
  • Users with motor limitations
  • Screen reader users
  • Keyboard-only users

This required:

  • High contrast readability
  • Large interactive targets
  • Clear error messaging
  • Logical navigation structure
  • Reduced cognitive complexity

Accessibility was embedded early into the design system to prevent retrofitting later.

Accessibility Standards Followed

WCAG 2.1 Level AA

The website was designed to comply with WCAG 2.1 Level AA guidelines following the POUR principles:

  • Perceivable: Content presented in ways users can perceive.
  • Operable: All interface elements accessible via keyboard and assistive devices.
  • Understandable: Clear and predictable interactions.
  • Robust: Compatible with assistive technologies.

WCAG AA Guidelines Implemented

Color & Contrast (1.4.3, 1.4.11)
  • 4.5:1 contrast ratio
  • Non-text contrast compliance
  • High-contrast focus indicators
  • Validated using Stark Plugin
Typography & Readability
  • Minimum readable font size
  • Scalable typography
  • Proper heading hierarchy
  • Improved line-height
Keyboard Accessibility (2.1.1)
  • Full keyboard navigation
  • Visible focus states
  • No keyboard traps
  • Logical tab order
Forms & Error Handling (3.3.x)
  • Inline validation
  • Error linked to fields
  • Color not sole indicator
  • Accessible error descriptions
Interactive Components
  • Accessible modals
  • Correct button usage
  • ARIA labels
  • Touch target sizing
Screen Reader Compatibility
  • Semantic HTML
  • Proper landmarks
  • Structured headings
  • Descriptive alt text

Selected AAA Enhancements

  • Contrast ratios exceeding AA minimum where possible
  • Enhanced error prevention in critical workflows
  • Reduced motion considerations
  • Clearer microcopy for cognitive accessibility

Where user risk was high, standards exceeded minimum compliance.

Tools & Validation Process

Stark Plugin (Figma)

  • Contrast validation
  • Color blindness simulation
  • Typography testing
  • UI state accessibility checks

Development Collaboration

  • Accessibility documentation during handoff
  • Lighthouse accessibility audits
  • Keyboard navigation testing
  • Iterative QA validation

Accessibility Integrated into the Design System

  • Contrast-safe color tokens
  • Accessible focus styling built into components
  • Standardized error state patterns
  • Typography tokens enforcing readable scaling

Accessibility was embedded at the system level to prevent regressions during future feature development.

Impact

  • Improved contrast compliance site-wide
  • Reduced accessibility-related QA issues
  • Improved usability for elderly users
  • Structured documentation for scalability

Conclusion

Accessibility at Pride Mobility was embedded into the Design System, component architecture, development workflow, and validation processes.

Accessibility became part of the product infrastructure — not a compliance checkbox.