Developers rarely talk about the importance of having the right accessibility strategy or tool in place to help with our development. Actually, we barely seem to talk about having an accessibility strategy or tool at all.With the issue of accessibility at an all-time high, it’s time we, as a development community, talk about the importance of web accessibility— something more comprehensive than just using a screen reader as a tool to assist us, but ensuring our team of developers is on the same page.
FOLLOW THE RULES
Whether it’s working together via Slack, Drive, or Basecamp, being able to communicate quickly and concisely back and forth is a big deal. It helps keep things moving and provides a virtual gathering space for ideas, discussions, and documents. But accessibility issues aren’t as cut and dry as sharing a document for most people. For many, it is a complex web of rules and guidelines that many times seem insurmountable and overwhelming. How can we navigate all these subtleties easily as a team?
We need to be on the same page, speaking the same language. Having a shared vocabulary helps facilitate communication between team members (and clients) and allows us to solve problems more efficiently. Dev teams should be keeping up with accessibility rules and guidelines, to help establish a shared accessibility vocabulary. Ensuring everyone is on the same page with types of accessibility issues and guidelines will help keep things clear and consistent.
Given the amount of accessibility guidelines and rules, having an automated system to flag errors would be helpful. It is much more efficient to have a third party do it for you and it also frees up your team to tackle the problem instead of having to determine, find, and fix issues.
Curated by (Lifekludger)
Read full article at Source: The Importance of Accessibility in the Dev Process