WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Do people actually want Automatic Accessibility withinWebTechnologies?

for

From: Bryan Garaventa
Date: Apr 20, 2012 10:26AM


That would mean both screen reader and keyboard only users, including voice
only activation (using keyboard nav commands), which is where the highest
percentage of accessibility issues reside, and these can be solved
programmatically.

Devs still need to do the rest like color contrast and sizing for low vision
and color blind users, which can be accomplished through CSS.

The reason why I ask, is that I've brought this concept up to approximately
6000 Accessibility Professionals around the world, and received positive
feedback from about 10, not counting WebAim.

That appears to be 0.17% in favor, and 99.83% against?

----- Original Message -----
From: "Léonie Watson" < <EMAIL REMOVED> >
To: "'WebAIM Discussion List'" < <EMAIL REMOVED> >
Sent: Thursday, April 19, 2012 11:57 PM
Subject: Re: [WebAIM] Do people actually want Automatic Accessibility
withinWebTechnologies?


Bryan Garaventa wrote:
"When I say Automatic Accessibility, I'm referring to a combination of
Universal Design (equally accessible for all) and Inclusive Design
(integrated accessibility within mainstream applications)."

I have reservations about the possibility of universal design.
Without wanting to derail this conversation too far though, the answer for
me is yes. I'd certainly like to see more products/tools/whatever designed
to be accessible from the outset. The catch is accessible to whom?


Léonie.
-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Bryan Garaventa
Sent: 20 April 2012 04:32
To: WebAIM Discussion List
Subject: [WebAIM] Do people actually want Automatic Accessibility within
WebTechnologies?

I'm curious about this.

When I say Automatic Accessibility, I'm referring to a combination of
Universal Design (equally accessible for all) and Inclusive Design
(integrated accessibility within mainstream applications). I adopted the
term Automatic Accessibility because it's more descriptive and easier for
people to understand who aren't already familiar with the terms Universal
and Inclusive design.

So when I refer to Automatic Accessibility for web technologies, I'm talking
about the incorporation of automatically accessible processes at the bedrock
level of enterprise development. This way, new technologies can be built
that include accessible features automatically, and everyone wins.

Is there something wrong with this idea?
messages to <EMAIL REMOVED>