Post

I think the Modern Web Guidance skills are actually promising. I mean, we couldn’t make developers listen to a11y concerns when producing their reactive hand coded slop soup. Now we have at least an avenue to make their tools listen.

Vale

@vale.rocks

I think it'll have the effect of people thinking their tool is handling accessibility for them and thus not paying it any attention. Perhaps less care than before, even. The output I've seen thus far from testing has been rather worrying, though I understand the 'skills' aren't final yet.

21/5/26, 2:53 pm0 reposts5 likes

They already did. Either you place it into the tools by stealth, or (like we did) sneak it into the design systems. When mentioning a11y in a meeting, the react devs face melts, the product owner cries because someone told her it’s soooooo expensive, and the scrum master sends you away.

Vale

@vale.rocks

I think we'll have to agree to disagree here. I don't see this improving accessibility any more than any other AI 'solution' has improved accessibility to date. I can only see it being taken as a lazy, ineffective shortcut in lieu of actual care.

Samo Korošec

@samokorosec.bsky.social

23 May

I just read this and thought neither of you is wrong. 🫣 (Personally I think, after years of watching products being developed, the only effective way to make websites accessible would be high fines for not doing so. Would make people figure shit out immediately.)

23 May

We are trying this in Europa. But the two hindering problems are: A) A certain part of the dev community has made the myth so prevalent, that a11y is expensive and hard, that POs opt for taking the risk B) the a11y community actually doesn’t get it‘s sh… together. The law actually went into effect…