There’s no arguing that building accessible websites is a force for good. Everyone, regardless of ability or disability, ought to have the right to participate on the web. But ensuring that our websites and apps work for everyone can be time consuming and isn’t always easy to get right. Luckily, like most things in programming, investing a little bit of extra time on your accessibility workflow and setting up a series of automated tools will end up saving you tons of time and energy in the long run. In this talk I will lay out a set of processes that can reduce your time spent identifying, debugging and testing accessibility support in your applications. I will discuss the ways that I automate certain aspects of my development workflows to catch accessibility errors, define and set up e2e tests for accessibility and go through the entire lifecycle of accessibility feature development using a real world example.

Comments

Comments are closed.

Thank you