People sometimes ask, “What about accessibility? Isn't that part of usability?” And they'reright, of course. Unless you're going to make a blanket decision that people with disabilities aren'tpart of your audience, you really can't say your site is usable unless it's(71)In most organizations, the people who end up being responsible for doing something aboutaccessibility are the people who actually build the thing: the designers and the developers. Whenthey try to learn about what they should do, whatever books or articles they pick up inevitably listthe same set of reasons why they need to make their sites accessible. There's a lot of truth in all ofthese(72).Unfortunately, there's also a lot that's(73)to convince 26-year-old developersand designers that they should be "doing accessibility". Two arguments in particular tend to makethem skeptical:
.Since their world consists largely of able-bodied 26-year-olds, it's very hard for them tobelieve that a large percentage: ofthe population actually needs help accessing the Web.
.They're also(74)about the idea that making things more accessible benefits
everyone.The worst thing about this skepticism is that it obscures the fact that there's really only onereason that's important: It's the right thing to do. And not just the right thing; it's profoundly theright thing to do, because thc one argument for(75)that doesn't get made nearly often enoughis how extraordinarily better it makes some people's lives .