Accessibility isn't something you add at the end; it's shaped by many decisions along the way, and many barriers are easy to avoid.
Based on situations we run into again and again in everyday frontend work, we'll go from quick wins anyone on the team can spot, to native browser features that do the work for you, to the more involved patterns behind interactive components. Because accessibility is a shared responsibility, not just a developer's job.
This is not an exhaustive guide, but a starting point (or a next step) with things you can apply in your next project and pointers to dig deeper.
Learning objectives:
- Understand that accessibility benefits everyone, and that it's a shared responsibility across design, project management and development
- Spot common, easy-to-avoid barriers such as poor contrast, small click targets, unclear error messages and missing focus styles
- Make use of native HTML elements and browser features, respect user preferences, and support different languages and writing directions
- Know that common components like accordions, tabs, dialogs and menus come with specific user expectations, and where to find established patterns for them (WAI-ARIA APG)
- Run basic accessibility checks, understand the limits of automated testing, and know where to dig deeper