Daniel Salerno
High contrast Pause or play animations
Case Study · Design Systems & Compliance

Accessible by design, not retrofit.

I built WCAG AA into every component and pattern from the start, so inclusive design is the baseline. Think ramps and elevators, not checkboxes: landmarks, keyboard navigation, heading structure, alt text and tab order, handled as a system.

Company
J.P. Morgan Chase
Role
Senior Product Designer, Workplace Solutions
Years
2026
WCAG 2.1 AA Design Systems Inclusive Design Frontend Screen Readers J.P. Morgan
Why This Matters

Accessibility is infrastructure. It always has been.

In 1945, Kalamazoo, Michigan, cut some of the first curb ramps into its sidewalks for veterans coming home from the war. Decades later, disability activists in Berkeley pushed for them on every corner. Now strollers, suitcases and delivery carts all use them. Curb cuts became infrastructure.

I think about that often. I have ADHD, a federally recognized disability, so I live in the gap where the digital version of that ramp hasn't been built yet. When an interface hides information behind "hover to discover," I can't get to it. Neither can screen reader users, or anyone using a keyboard alone.

2020 made the gap impossible to ignore. When everything went digital overnight, people without accommodations were locked out of work, school and community. Since June 2025, the European Accessibility Act requires many digital products sold in the EU, from online shops to banking apps, to meet standards that map to WCAG 2.1 AA. And designing for disability first pays off: Microsoft built the Xbox Adaptive Controller with gamers with limited mobility, and it went on to win major design awards.

Challenge

Accessibility was an afterthought.

Teams built in isolation, and accessibility got bolted on at the end, if at all. It was a ramp added to a building never designed for one, and components broke in real use.

Here is what broken looked like. A screen reader user heard the whole page read aloud with no landmarks and no map. A keyboard user got stuck in a dropdown with no visible focus. A colorblind user saw one color for both interactive and disabled buttons, told apart only by a hover state that didn't work for them.

There was no pattern language and no documentation. Every team rebuilt components from scratch, repeated the same mistakes, and failed the same audits.

The numbers backed it up:

40%
of components inaccessible at launch
0
documented keyboard or landmark patterns
3+
contrast failures per page at audit
Solution

Accessibility built into the token layer.

So I made WCAG AA a build-time constraint. Every color pairing is checked against contrast ratios. Every component ships with documented keyboard behavior, focus indicators and ARIA roles, and every pattern is tested with assistive technology before release.

The design system supplies the rules and the tools: contrast-safe color tokens, components with semantic structure built in, and patterns teams can reuse as-is.

Fixing accessibility after launch costs many times more than building it right the first time. Putting it in the token layer means that debt never builds up.

Accessibility checklist
WCAG AA Compliance
Contrast: 4.5:1
Normal text meets AA standard
Keyboard navigation
All interactive elements reachable
Visible focus states
3:1 contrast minimum on focus rings
Semantic HTML and ARIA
Assistive tech can interpret content
Automated and manual testing
axe, WAVE, screen reader validation
Documentation
Built-in Every component ships with accessibility notes
Keyboard Shortcuts and navigation patterns documented
Tested Against NVDA, JAWS, and VoiceOver
Validated Contrast and ARIA checked on every build
How It Works

Four layers of markup. All visible to assistive technology.

Before development starts, every page gets four kinds of accessibility markup. Landmarks set the structure, headings build an outline, alt text describes visuals, and tab order sets how keyboard users move.

$1
Design phase
×100
$100
Post-launch remediation
1% of the cost

Illustrative ratio, based on the widely cited rule of thumb that defects cost far more to fix after release than during design. Exact multipliers vary by team and study. The return is financial as well as ethical.

Landmarks

Landmarks like <header>, <main>, <nav> and <footer> work like street signs for screen reader users. Without them, a page is one long block they have to hear in order. With them, they jump straight to <main>. The result: scanning a page takes seconds instead of minutes.

HEADER MAIN ASIDE FOOTER

Heading Structure

Headings are the table of contents. Screen reader users jump between h1, h2 and h3 to skim, the way you scan subheads before reading. Skip a level and they lose their place. The result: a page that's scannable instead of linear.

H1 H2 H3 H2 H3

Image Alt Text

Good alt text carries the meaning a sighted user gets instantly. "Photo of a person jumping" misses it. "A person with arms raised, mid-jump, celebrating in sunlight" gets it. Charts get their data, not just "pie chart." Decorative images get alt="" so they're skipped. The result: people with vision loss get the same information you do.

1 alt="" "Person reviewing medical records on a laptop in a hospital corridor" 2 alt="" "J.P. Morgan Workplace Solutions logo" 3 role="presentation" Decorative - skip

Tab Order

Keyboard users move with Tab, so focus should follow the path the eye does: top to bottom, left to right, in logical groups. A broken tab order is a sidewalk that jogs left and doubles back. The result: keyboard users move through the site without memorizing where things are.

Username Password Sign in 1 2 3 4 5 6 7 8 Skip to main content
Process

Audit, enforce, document, and verify.

Five phases to build accessibility into the system: find the gaps, enforce standards in code review, and test with real assistive technology.

01
Audit Existing
axe · WAVE · screen reader sweep · contrast check
02
Define Standards
WCAG AA criteria · landmark patterns · heading rules
03
Build Components
Keyboard support · ARIA roles · focus management · tokens
04
Test with A.T.
NVDA · JAWS · VoiceOver · mobile TalkBack
05
Document Patterns
Storybook a11y docs · annotations · team playbook
Impact

Nobody has to retrofit or guess anymore.

100% component coverage

Every shipped component meets WCAG AA. No exceptions, and no accessibility debt left on the board.

70+ violations resolved

I resolved 70+ accessibility violations and wrote the team's guidelines for landmarks, headings, tab order and alt text, applied across all four breakpoints on every delivery. Teams now copy pre-annotated patterns instead of rebuilding accessibility every sprint.

Tested with real screen readers

Validated with NVDA, JAWS and VoiceOver, beyond automated checks.