Accessibility issues don’t usually arrive all at once with alarms going off. They sneak in.
A component ships without keyboard support. Someone pastes in styled content from somewhere mysterious. A color tweak drops contrast just enough to be a problem. A module update shifts markup in ways no one notices until much later. Each one feels small. Together, they pile up into accessibility debt.
And like any kind of debt, it gets expensive.
In this session, we’ll dig into how accessibility debt shows up in Drupal projects and why it’s so easy to miss. We’ll look at the usual suspects across theming, content workflows, design systems, and day-to-day maintenance, along with ways to catch issues earlier without slowing everything down.
You’ll leave with practical ways to keep accessibility from quietly slipping over time, and a few habits that make things better for users, contributors, and future maintainers alike.