LLM biased against accessible code (Claude Code issue #56079) :: Aaron Gustafson

This site is undergoing an open redesign, so if it looks strange, that’s why.<br>Close

Published

18 Jun 2026

by<br>Aaron Gustafson

Reading Time<br>1 min

Filed Under

accessibility<br>AI/ML<br>progressive enhancement

Reactions

0 Webmentions

Like this?

Share on Twitter (new tab)

Share on Hacker News

Post on Facebook

Share on LinkedIn

Share on Pinterest

EstiShay filed a bug report that’s concerning. They found that Claude Code treats accessibility fixes as optional, even when the project’s requirements file explicitly specifies “WCAG 2.2 AA minimum.” When asked, the model explains:

Claude treats accessibility fixes as optional trade-offs rather than requirements, even when the project’s own rules say otherwise. That’s distinct from just not knowing the right ARIA pattern — it’s a values problem in how the model weighs competing priorities.

So… not a lack of knowledge (the model performs well when reviewing code); it’s a conscious choice, a prioritization failure. Accessibility becomes a “nice to have” in pursuit of coding speed, just like we’ve deprioritized it in human-made software for decades.

The models learned from us and are repeating all of our mistakes. At scale.

Webmentions

Likes

Shares

(You are on this page or in this section)

{% for mention in webmentions %}

{% if mention.author %}

{{ mention.author.name }}

{% endif %}

{{ mention.content | safe }}

{{ mention.published_human }}<br>Permalink:<br>{{ mention.url }}

{% endfor %}

{% for mention in webmentions %}

{% if mention.author.photo %}

{% endif %}

{% endfor %}