I wish this article would get past the "disabled people don't use computers" straw man (at least, I hope none of OP's technical friends really espouse that) and

I wish this article would get past the "disabled people don't use computers" straw man (at least, I hope none of OP's technical friends really espouse that) and address the reasons that designers marginalize accessibility in real decisions. For one, most of us are ignorant as to just how many users fall outside the "able" use case, and in what ways. Among product managers, if you can't quantify that unusual use case, it's going to be termed the "10% case" or the "1% case". And that is the kiss of death. For another thing, few of us have any idea how people outside the majority want to use software. It's just as ludicrous to assume that a legally blind person will use a cameraphone the same way as you do as to assume that she won't use a cameraphone at all. Perhaps she's far more likely to use it for document scanning, and far less likely to demand the option to apply a wacky sepia tone effect to her photos. Getting the answers to these questions into designer's heads is going to have more impact than any number of "come on, you guys" appeals.