Right after I started my first job, the client I was working for had to implement web accessibility as a legal requirement, which was a pretty big deal as it concerned a large legacy codebase, many different stakeholders and most people on the team didn’t have much experience with the topic.
Since everything was new to me, I didn’t mind much about what I would learn first - but I was very excited about learning something that benefited a diverse community of people.
I was lucky enough to have a bunch of amazing mentors and I would like to share some of the things I learned along the way with you - hope they help you on your journey.
- The basics of Web Accessibility
- Why it’s important and who benefits from it
- Basic terminology regarding Web Accessibility
- Where and how to get started with implementation
More specifically, we will look at three things you can do today to make your application a little more accessible, including:
- Semantic HTML
- Color Contrast
- Keyboard Accessibility
If there is only one thing you take away from my talk, however, it would be that in the case of web accessibility, 10% is better than nothing. It’s an ongoing journey of improvement - but it’s important to start somewhere :)
Josefine is a frontend engineer based in Hamburg, Germany. She describes herself as "ready to take over the world by storm" on good days and "wondering when she will be exposed as the imposter she is" on bad ones.