Burnout happens in teams that skip accessibility

In an industry obsessed with speed, scale, and constant reinvention, we rarely stop to ask whether the way we build software is healthy, for our users or for ourselves.
Yet hidden in one of the most overlooked engineering disciplines lies a blueprint for calmer systems and more resilient developers.

We often treat accessibility as a grueling “last‑mile” chore, but what if it’s actually one of the best tools we have to survive this profession?
This talk explores a Developer’s Paradox: the idea that by slowing down to build for users with visible and hidden impairments, we inadvertently create technology that’s more predictable, maintainable, and humane and in doing so, we reduce our own risk of burnout.

By trading chaotic, over‑engineered complexity for intentional, calm technology, we don’t just make better interfaces.
We reduce cognitive load, simplify our architecture, and build codebases that work with us, not against us.
Accessibility principles push us toward clarity, consistency, and resilience — qualities that benefit every engineer, every codebase, and every team.

This keynote is an invitation to reframe accessibility not as a constraint, but as a path to more sustainable engineering. When we build for the edges, we strengthen the center, including ourselves.