The latest articles on DEV Community by Zay Dea (@zay_dea_af755ce20154bca7a). https://dev.to/zay_dea_af755ce20154bca7a https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4055565%2F80e5629d-da26-462e-a424-f9e3abbf4463.png https://dev.to/zay_dea_af755ce20154bca7a en Zay Dea Thu, 30 Jul 2026 18:37:32 +0000 https://dev.to/zay_dea_af755ce20154bca7a/why-four-companies-rebuilt-the-same-accessibility-fix-for-their-clis-and-what-i-built-instead-k09 https://dev.to/zay_dea_af755ce20154bca7a/why-four-companies-rebuilt-the-same-accessibility-fix-for-their-clis-and-what-i-built-instead-k09 <p>I built this after noticing that Anthropic, Google and GitHub have each rebuilt the same fix for their CLIs to replace animated spinners and boxed tables with plain text if a screen reader is detected. Since there was no reusable version of this fix, I built one. It auto detects if it is running in a screen reader context and swaps the output automatically, as well as providing a linter to find these anti patterns in any codebase.</p> <p>Github: <a href="https://github.com/zaydea805/term-a11y" rel="noopener noreferrer">https://github.com/zaydea805/term-a11y</a></p> cli javascript opensource a11y