All work
AccessibilityWCAG 2.1

Accessibility built into the components

Instead of fixing accessibility page by page, we fix it in the component, once, so every page that uses it improves at the same time.

Client

  • Enterprise client
  • Name withheld

Our role

  • Accessibility owner
  • Component development

Stack

  • HTL
  • ARIA patterns
  • JavaScript
  • LESS
1toggle that stops every animation
Onceeach audit finding is fixed
Everypage using a component improves
WCAG 2.1built in by default

The challenge

Third-party audits kept flagging keyboard traps, invalid ARIA, motion and labelling issues across shared components and authored content.

The approach

  • A site-wide reduced-motion control: one keyboard-operable toggle turns off every CSS and JavaScript animation, pauses background video and stops count-ups
  • Audit findings fixed at the component level: roles, tab targets, focus order, carousel indicators, headings and alt text
  • Separating code fixes from content fixes, and flagging where a code change would break other pages
  • New components ship with labelling, keyboard support, screen-reader table headers and print styles

Results

  • Accessibility is a property of the library, not a cleanup project
  • Findings close once and stay closed
Next projectLive cart value in Adobe Target, without touching the store

Is your platform telling you something?

An AEM health check is the fastest way to find out what’s fragile before it breaks.

Book a health check