The worst thing about building an "accessible" app is that you might just have 4 users out of the million who need it.

Either they don't know it exists or it needs to be modified for every user!

If you do your research and your expectations are that only ; people will use your app, then you don't make it accessible. It doesn't make sense to do so. If your website is a government agency that issues the national identification cards or something... then you do - and you make it dead simple. When things are designed well and people research and follow goal driven strategies, this isn't a real problem.

@sheriffderek when you start building applications for the visually impaired or developmentally challenged, you face these problems.

I think there's a social responsibility on us to make things as accessible as possible. We can't predict how systems will evolve and what the user base will be to decide not to do it. And it's the sort of thing that is easier to do from the start (by including it in your design process) than to introduce it a few releases down the line. In some places, it's also a legal requirement.

@blessin Clearly, but if the application is only for 4 blind people - something else is wrong.