Whether it's an #a11y "shotgun house" social problem (add it at the ass end, poorly), the "who cares I'm not disabled (yet)" fallacy, a policy concern or other accessibility woe: What issues irk you the most and why? Any method, approach or idea you tried ever even kinda help?
2
1
6
My current favorite trend is people using Lighthouse for a11y testing. Lighthouse only works on load, so anything behind an interaction, like forms in an accordion, are only tested in their initial state. 1/2
1
Dev groups claim success till I point out they should test again after a button click that modifies the DOM and AT. It's such a problem I built roking-a11y-automation...and finally got around to publishing the npm package.
1
Replying to @hrobertking
Oh dd you hit a nerve with the "dev groups claim success" comment, which begs the question just who is successful in such a case? To which I have several answers none of which address folks who don't use "devs" daily. Or ever ;) Or never use human testing for real real.

Mar 13, 2021 · 8:17 AM UTC

1
Replying to @mholzschlag
Testing using a living person?! There isn't a story for that in this sprint or any other, and we definitely don't have time for it. Our engineer will run a Lighthouse test to make sure we don't have any critical WCAG errors. We can fix all the "moderate" errors after release.
1
1
Way to turn a phrase, Robert! I almost lol'd for real because your wit is sharp but nicked my lip on the razor's edge of a story known too long, too bloody true so a typed ha ha ha and perfect sardonic nostril twitch is best I can do for old problems with newer titles and v.∞ 🙄
1