The latest articles on DEV Community by HumayuNn (@humayun7yz). https://dev.to/humayun7yz 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%2F4143907%2F8e6815fe-c32a-40ee-9efd-a44592d8f055.jpg https://dev.to/humayun7yz en HumayuNn Sat, 26 Sep 2026 07:02:22 +0000 https://dev.to/humayun7yz/quick-question-for-devs-who-work-on-web-accessibility-35m3 https://dev.to/humayun7yz/quick-question-for-devs-who-work-on-web-accessibility-35m3 <p>Do you (or your team) ever ship code with accessibility issues — missing alt text, non-semantic buttons, bad contrast, etc. — just because nobody caught it in the moment, not because you don't care?</p> <p>I'm exploring building a small tool that automatically flags accessibility issues as you code (in VS Code/Cursor) — not a full audit tool, just something that catches the obvious stuff before it ships, explains why it matters, and suggests a fix.</p> <p>Before I build more of it — is this something you'd actually want, or does your team already have this solved some other way? Genuinely trying to figure out if this is worth building further, not selling anything.</p> a11y frontend vscode webdev