JUAN GALAVIS Principal Product & Service Designer · Healthcare · Accessibility · AI-first teams
← All work

Accessible interfaces · Healthcare · Design systems

An Android design system, accessible by default.

An accessibility audit found the app failing WCAG 2.1 AA. We remediated it screen by screen, then turned the fixes into a system.

Splash screen
Log in screen
Home screen with balance and tiles
Medical claim details
Financial dashboard
Role
Lead Product Designer, via Optimity Advisors
Client
Largest federal health insurance payer, 5M+ members
Worked with
Business analysts, product owners, developers
System
Android, alongside the web and iOS systems
0.0M+ members on the app
0+ Android screens audited
AA WCAG 2.1 target, every component
0 component families
1 systems: web, iOS and Android

Overview

An audit showed the member app wasn't compliant with accessibility guidelines. The client set a bar for every digital experience: WCAG 2.1 AA.

The same audit surfaced branding issues and inconsistent patterns, so we fixed both at once with a design system: premade, reusable components so teams stop rebuilding things like date pickers from scratch and drifting apart. We built accessible systems for the desktop member portal and the iOS app. This case is about the third one, Android, and the problems that only showed up there.

The production Android home screen before remediation
The problem

An Android app pretending to be iOS.

Colors, type styles and animations were used inconsistently, which made the app harder to learn. Key WCAG 2.1 AA requirements, like color-contrast minimums and code annotations, weren't met. And the Android app followed iOS design patterns, which created inconsistencies on the platform and slowed performance.

Not WCAG AA compliantContrast minimums and code annotations failed the audit.
iOS patterns on AndroidInconsistent with the platform, and slower.
All custom componentsNothing native, everything rebuilt and drifting.
Inconsistent interactionsErratic color, type and animation made the app harder to learn.
The call

One system or two?

We weighed one integrated system against two separate ones. Two meant more design work up front. But it let each platform use the maximum number of native UI components, which meant less development work and a faster, more platform-specific app.

01 · Research

Learn Android before redesigning it.

We analyzed and categorized 50+ screens of the existing Android app to find every element that needed to change. In parallel we went deep on Google's Material Design 3 to see which native components the system could lean on, and studied what best-in-class Android apps were doing in Q2 2023, comparing the same products on iOS and Android.

Apple Files and Google Drive side by sideHow each platform handles the same job natively.
iOS and Android versions of eight top apps comparedThe same eight top apps on iOS and Android, compared pattern by pattern.
02 · Remediation prototype

Fix it screen by screen, side by side.

Using the Accessibility Management Platform (AMP) report, plus personas and journey maps from earlier work with the client, we built low-fidelity wireframes to settle fonts, text sizes, brand color and contrast. Once approved, we prioritized key screens with the mobile product manager and built them in high fidelity.

Every remediated screen was presented next to the production screen it replaced. That made the improvements obvious to stakeholders and kept approvals moving on a tight timeline.

Log in screen, after: remediated design Log in screen, before: in production
Before: in production · After: remediated
Drag the handle to compare
A login you can actually read

Production used pale, underlined fields and a washed-out button that read as disabled. The remediated screen uses outlined text fields, a visible password toggle, a solid primary button and one combined recovery link.

Contrast, measuredProductionRemediated
Primary button label 1.4:1FAILS AA 6.0:1PASSES AA
Screen heading 2.7:1FAILS AA 8.2:1PASSES AA

Ratios sampled from the comparison screenshots, so treat them as approximate. AA asks for 4.5:1 on normal text.

03 · Design system

Work backwards, from screens to parts.

We compiled every approved component and showed how each prototype screen was built from reusable parts, which made adoption easier. The system follows Material Design 3's organization, so stakeholders started from a structure they already knew. Each component has usage guidance and CSS code snippets, and the system is built to grow as features are added.

Components are named by level: a- atoms, m- molecules, o- organisms. WCAG criteria are part of each spec, not a separate checklist.

Design system documentation page for the filled button
Live, rebuilt from the speca-button_filled
primary-blue-dark on white text: about 6:1. Height 48px clears the touch-target minimum.
23 component families, organized like Material Design 3
Core brand elements
App bars
Badges
Buttons
Cards
Checkbox
Datepicker
Dialog
Dividers
Lists and tables
Menu
Navigation
Progress indicators
Search
Sheets
Switch
Tabs
Text fields
Dashboard components
Disclosure controls
Banners
Misc
Key page templates

The remediated app

Every screen built from the same components: consistent color, legible type, native Android patterns, and TalkBack-ready structure.

Identity verification options
Location permission prompt
My Plan menu
Most recent medical claims
Wellness and incentives
Member ID card with share sheet
Challenges

Many stakeholders, conflicting goals.

When conflicts came up, WCAG 2.1 AA and Material Design 3 were the North Star. We also had to make the case for inclusive design to business leaders, and teach technical and non-technical people how, and why, to use the system.

Lessons learned

Accessibility isn't only a design job.

UI fixes matter, but a big share of accessibility lives in backend adjustments and settings. It takes designers, developers and everyone else in the delivery chain.

Future iterations

This is step one, not done.

Accessibility is iterative. Regular audits against the latest WCAG standards, plus feedback loops across teams, keep the app accessible as it grows.

Creative Duel after boards held up in front of the room
Next · 02 / 05 · Scalable systemsInnovation Conference Experience Strategy
Read the next case study