Comments on: Google Chrome Falls Short on Accessibility

By: I tried Google Chrome: It’s light. fast and Rocks: By Olga Lednichenko « Olga Lednichenko -My new Slate

Tue, 09 Sep 2008 12:46:45 +0000

[...] Google Chrome Falls Short on Accessibility [...]

By: Kel Smith

Kel Smith — Sat, 06 Sep 2008 22:32:34 +0000

Thanks, Rob. I would add as 4) that many organizations don’t make accessibility a priority in their business plan. As a result, project engagement leads don’t factor this into the equation when writing functional requirements documentation. Too often, spec is written to accommodate a combined skillset competency rather than users’ needs.

Many thanks for contributing to the conversation.

By: Rob

Rob — Sat, 06 Sep 2008 15:38:54 +0000

Much as I hate to say this, as a software developer, things like this are often seen as an addon for two driving reasons

1) Development is focused around the needs of the *developer*, and experiences the developer has. My brother is (severely) handicapped, and to some extent that affects the way I think about software design. Not all people work like that.

2) The *majority* of people (speaking wholistically, not about subsections of the population) are not handicapped, therefore the design goes for the majority

3) Not enough people who do have these issues realise that they need to raise them with the original developer/manufacturer to get their voice heard.