[pcl]

> “Really it shouldn't be up to the developer it should be up to the disabled person to buy tools. Just like someone may need to buy a wheelchair to move around, they should have to buy a specialty browser that handles their limited visibility needs or brail tool interface.”

No, that’s the wrong analogy. The ADA is there to ensure that people with wheelchairs can find a barrier-free entrance to a building, and a curb cut at an intersection.

It should be on us, the developers, to ensure our apps work with the tools of the trade to enable people with limitations. So, our apps should be usable by screen readers. The screen reader is the analogue to the wheelchair here.

This is one of the great things about HTML. Even ignorant / lazy / time-constrained developers are likely to output something that sorta works, just since they’re using divs and imgs and whatnot.

And the bar is so low! Adding accessibility labels takes not much effort at all. And, as an added bonus, accessible apps are easier to test, since testing frameworks like Playwright can hook into accessibility info directly to validate assertions.

[coolliquidcode]

> find a barrier-free entrance to a building, and a curb cut at an intersection I disagree with this too. It's a social nicety but shouldn't be a requirement.

> It should be on us, the developers, to ensure our apps work with the tools of the trade to enable people with limitations Why? I argue it should be on the disabled person.

> The bar is so low. Not really. There are groups of lowers running around looking for people to shake down for ADA misses. To really protect yourself it takes a lot of time.