You're obviously not an engineer. The more requirements you have, the more complex the design process becomes and the more it costs. This isn't to say you sho

You're obviously not an engineer. The more requirements you have, the more complex the design process becomes and the more it costs. This isn't to say you shouldn't bother, but it does add extra cost. Now as I said, this doesn't mean you shouldn't ever bother, but you have to weigh the costs and benefits. Making a product more accessible can get you more customers, which means more money. You can also make the product more appealing to more customers, even non-disabled ones: for instance, suppose you make your software product so that the color scheme can be changed, so that color-blind people can tweak it to see it better. Non-color-blind people may find out about this feature and rave about it because they can also use it to tweak it for their tastes (perhaps with a "dark" theme), rather than being stuck with whatever boring color scheme your designers chose to appeal to the masses. This could drive up your sales, even though the original motivation was disabled people.