Accessibility 201: Tales from the Front End
Ready to take the next step on accessibility? Come hear cautionary tales of well-intentioned yet inaccessible products! Learn from the struggles of those who’ve gone before, change your mindset, and improve your code.
Over the course of 12+ years of running web accessibility clinics at UC Berkeley, the Web Access team has seen a lot. On the good side: a lot of innovative interfaces. On the not-so-good side: a lot of inaccessible implementations of relatively standard functionality. And, a lot of the same coding issues, over and over again.
In this session, we’ll dive in to those common problems and some other sticking points that get in the way of developing truly accessible interfaces.
Some things you’ll take away from this session:
- A deeper understanding of accessibility, beyond “can a screenreader use it”
- The first rule of ARIA (Accessible Rich Internet Applications)
- Specific pitfalls to avoid when working with markup
- Checklists, checklists, and more checklists
Who should attend: Anyone who works with markup, accessibility, or user experience.
- Themers
- Front-end developers
- Decoupled Drupal developers
- UX folk
- Testers
Some prior knowledge of accessibility and/or HTML will be helpful for understanding the technical recommendations, but anyone will be able to benefit from the overall discussion.
This session was presented in a slightly longer format at BADCamp 2018.