Hacker News new | ask | show | jobs
by SoftTalker 529 days ago
By that logic, why care about accomodating anyone with a disability? Your site works for 95% of people, why care about those who need to use screen readers?

And before you say "that's their choice," you're the one who is breaking the functionality. Nothing about using a VPN or linux or Firefox creates any problem for TCP/IP or https.
1 comments
scarface_74 529 days ago
One because it’s the law and two because the disabled can’t just make a choice and install Chrome.

However, while the site creator does have to meet the disabled halfway, the disabled person is responsible for having whatever type of equipment they need to make it work - ie screenreaders

link
spookie 528 days ago
If your website is full of divs generated by JS that are full of aria tags that make no sense, those tools don't have a chance. Most websites act this way as well. Even Facebook used to lock people out of their messages if you couldn't use a mouse, at least in the last time I checked (infinite feed + no way to skip feed via tab -> can't reach right panel).

Just do your job right. Not saying you should test some unique Firefox config but at least the default version is to be tested.

Hell, I've seen people here indicating that they just tell desktop Mac users to "install Chrome". Such carelessness is bad for business. Web development sure could raise its bar.

link
scarface_74 528 days ago
If you’re selling a SaaS app, you care more about the customer than you do about the user. The customer is the IT department.

For the longest, Amazon Connect’s - AWS hosted call center software - call flow builder only worked with Chrome.

Even for B2C users, using Chrome is not a deal breaker. If they are okay with using shitty Electron apps, they will be okay with using Chrome for Mac.

link