Hacker News new | ask | show | jobs
by josephg 2001 days ago
Based on what other commenters have said, it sounds like the button is implemented in a custom react component. In that case ideally it should be as simple as changing the component to output a button instead of a div, with some css to remove the default button styling. Which would be the equivalent of translating a decent chunk of a website to French with one tiny change.
1 comments

I'd be amazed if the only thing that makes the website inaccessible is the use of a single div instead of a button - that'd be an enormous oversight. As in, there's either a reason for it that does not make this an easy fix, or it's so trivial that it's not a mistake you make if you're the kind of developer that follows basic accessibility practices throughout the rest of the app.
Its usually not an all or nothing thing. Most websites aren't "inaccessible" entirely. They have some parts which work fine in screen readers and some parts which barely work at all, and which leave blind people muddling through. And they can muddle through a lot - blind people don't have much choice a lot of the time.

So incremental improvements like this can still be very helpful. You don't need to fix everything all at once.