- developers generally don't need it, can't easily test it, and aren't even that aware of it
- "accessibility" can mean a lot of things. Are we talking about blind persons, daltonism, low visibility, limited motor skills, or something else I don't even know about? Each one has their challenge, and it's difficult to address all of them on purpose
- accessibility is often regarded as "niche" by stakeholders (unless one of them requires it or you really have a big scale), and thus not important. Unlike backward compatibility, it's not easy to have accurate numbers on how many of your users require it too.
That is not to say accessibility is not important.
Generally, the first steps to get it right is NOT to design anything specific for them, but instead to adhere to standards, semantic HTML (or whatever your platform use if you do a native app), have enough constrast, big enough fonts, and take user-settings into account (generally it's as easy as not overriding anything like zooming and scrolling).
The good thing about accessibility is if your app/website is accessible, it also benefits all your other users, in some ways.
that's because there aren't as many blind people as seeing people.
Meanwhile there are huge numbers of people with poor eyesight or other disabilities. You'd think a business would be keen to get those customers.
What I think stinks is that companies seldom thinks of accessibility. In many cases, there are more people in need of special accessibility tools than support for lower web browsers, yet all focus is on the latter when it comes to web development.
A good thing can be to follow the standard: https://www.w3.org/standards/webdesign/accessibility