Build vs. Buy: Automated Accessibility Tools

▤ Summary

My company was actively trying to address accessibility, but in the past had mainly done audits manually in test environment links and used a monitoring tool for issues that were pushed into production. This may add more time and research to your project timeline, but my recommendation is to find advocates wherever you can to act as evangelists of accessibility. If your organization’s build process and tech stacks are a special case, you’ll need this extra support to implement a new tool. Buying an automated solution instead of building one saves time and can get you fully integrated in your testing environment faster than starting from scratch. Rather, the purpose of this post is to shed light on the effort, time, and overall magnitude of what it takes to build an automated testing solution and what challenges may occur, especially if you’re at a large organization.

▦ Linked Companies

Deque Systems

$10M to $25M

GitHub, Inc.

$1M to $5M