Shipping Accessible Interfaces by Default
Accessibility is a baseline, not a feature. Here's how we bake it into every build.
Accessibility shouldn’t be a retrofit. When it’s part of your defaults, it costs almost nothing and benefits everyone.
Start with semantics
Most accessibility comes free with correct HTML. Buttons that are <button>, headings
in order, labels on inputs — this foundation does the heavy lifting.
Keyboard first
If it works with a keyboard, it usually works with assistive technology. We test every interactive component with the keyboard alone.
Respect user preferences
We honour prefers-reduced-motion, ensure sufficient contrast, and never trap focus
except intentionally (like in a modal menu, which we then make escapable).
It’s a practice, not a checkbox
Automated checks catch some issues, but real accessibility comes from building with it in mind from the first line of markup.