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?
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.
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.
Top comments (0)