@aardrian Yeah it's true. We have one client, who's site is fully WCAG 2.0 AA compliant, but they keep it only because they think it looks good from a PR perspective (we've tried to get them to remove it). And another client who Adrian had actually mentioned in a previous blog post about getting sued despite having accessiBe, and today they would rather pull their site offline than have an a11y overlay run on their site.
@aardrian Right. Though I'll say the client who got sued, in response they brought on a dev who really cares about accessibility. I've never had a client come back with so many QA bugs on screenreader experience. So, I gotta say it was a win for a11y, and frankly I learned a lot too. Just unfortuante it had to happen that way haha.
Add comment