But this is replacing something with good a11y guidelines, with poorer support. That’s worth warning about, and nothing at all like trying to make downhill skiing for paraplegics.
Imagine using this for a new B2B app and then losing sales because prospective customers have ADA requirements or blind employees who use other web apps just fine. It’s extra engineering work sure, but it’s hardly a crazy ask, and it’s the right thing to do for large to medium size companies who can afford it IMO.
Working on an application now with deep a11y requirements. The main function of the application can't be done without sight (validating scanned documents). It's just a little frustrating.
I completely understand that... it's simply that some of the hard requirements only make sense for those without sight, but you cannot effectively use the app without at least some sight. (there's decent zoom and contrast support)
Imagine using this for a new B2B app and then losing sales because prospective customers have ADA requirements or blind employees who use other web apps just fine. It’s extra engineering work sure, but it’s hardly a crazy ask, and it’s the right thing to do for large to medium size companies who can afford it IMO.