Mastodawn

Here's some thoughts and feelings about needing to vibe code to do accessibility design work. https://ericwbailey.website/published/the-case-for-an-accessibility-designer-vibe-coding-when-all-his-coworkers-are-also-vibe-coding/

The case for an accessibility designer vibe coding when all his coworkers are also vibe coding

Am I letting my own personal beliefs and biases affect the outcome I ultimately want?.

Show thread

Mark T. Tomczak 2d ago

@eric I hadn't considered AI for accessibility before... It may plug an unfortunate gap I've seen, which is that developers really, really, really don't want to support a11y in most firms and management doesn't care enough to force the issue.

But if an LLM can reduce the problem of identifying issues to one analysis pass... That's not a small thing. And I'm generally seeing LLMs are better at that than traditional heuristic approaches, because they end up trained on real-world examples of what goes wrong.

Show thread

Eric 2d ago

@mark Unfortunately, my experience has been a high degree of wildly incorrect fixes when it comes to a LLM performing autonomously. It takes a high degree of scoped human intervention and verification, much to my boss’ disappointment.

Show thread

Mark T. Tomczak

@eric The approach I've seen work best is AI as an automated reviewer in the pull request workflow. It can false positive and false negative, but in practice the false-pos rate I'm seeing is like 1-5% (and much of that corner case stuff, like "yes you're right but that is autogen code that cannot be fixed at this layer").

It needs human in the loop, but it doesn't get bored in the same way humans do.