Craft8 April 2026 · 6 min
Accessible by default, not as an afterthought
Accessibility is cheaper when it's built in from the first component. A practical checklist I keep close.
Retrofitting accessibility is painful. Building it in from the first input and menu is almost free.
Real focus states, sufficient contrast, semantic markup, and keyboard paths cover most of the ground.
Respecting reduced-motion preferences is a small touch that says a lot about who you build for.