logoalt Hacker News

reaperducertoday at 2:36 PM3 repliesview on HN

if we get our first blind user I will gladly make some admends to make it more usable for them.

Not good enough. You have to be accessible before it is needed in order to avoid legal liability.

And how do you expect to get a blind user if they already cannot use your product?

None of the doctors I build web sites for are currently blind. I know this because I talk to them regularly. But I still build the web sites for the future, when HR might hire a doctor or nurse or other person who is blind, or partially sighted, or has trouble with their muscles, or has difficulty distinguishing colors.

Doing the right thing isn't that hard. Not doing it is just lazy.


Replies

flosslytoday at 2:46 PM

You call it lazy. I call it "focus" or avoiding pre-mature optimization.

I find the "legal liability" claim hilarious... I do better than 95% of the web: as I said I HAVE some screen reader directives (just did not test it), and labels to make the app more accessible.

show 2 replies
ncphillipstoday at 3:43 PM

We use tailwind and are capable of building accessible websites without any issue. People could make all the same mistakes with CSS for accessibility. It’s the not knowing how to make accessible content that leads to inaccessible content, not the tool you use to implement the styling.

0x3ftoday at 3:08 PM

Sounds like you're kind of just talking your book though. Person who makes accessible sites suggests you need an accessible site. Blind people aren't the only ones who might need modifications. You could have an infinitely long list of adjustments for all kinds of disabilities, and tell me I'm lazy for not doing each of them. Why are blind people special?

show 1 reply