Accessibility is a crucial part of product creation. Every team member, from engineer to technical writer, must have at least a basic understanding of what accessibility means for their role in product development. Often, writers leave it to engineers to build accessible products but don’t take into consideration how to make their documentation accessible, too. We can and must do better as writers in thinking about accessible language and content design.

Instead of focusing on empathy and why accessibility is important, this talk will focus on how we can actually make change in our work.

In this talk, we’ll discuss:

+ Accessible style guides and a11y-friendly words
+ Semantic content design in HTML / Markdown
+ Testing for accessibility in docs
+ Advocating for a11y as a priority

You’ll walk away with some easy wins to start making your products and documentation better, as well as some bigger goals to help implement change in your company. After all, accessibility is for everyone.