W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2004

Re: R: Usability and Accessibility

From: Doyle-Work <dburnett@sesa.org>
Date: Wed, 12 May 2004 10:21:29 -0800
To: W3C Web Content <w3c-wai-gl@w3.org>
Message-ID: <BCC7AB29.2A31%dburnett@sesa.org>

Hi Roberto -

I think we are saying the same thing or close to the same.

On 5/11/04 11:19 PM, "Roberto Castaldo" <r.castaldo@iol.it> wrote:

> Hi Doyle, hi group
> 
> 
> Doyle:
> However, there can be usability issues that make it more difficult for
> certain individuals, especially individuals with disabilities. Sometimes,
> these same issues make it more challenging for individuals without
> disabilities. Hence, if it is an equal burden on everyone, even if it takes
> a person with a disability longer, there is not likely an accessibility
> issue.

Addressing your comment above, I had written:

"When a usability issue potentially becomes an accessibility barrier is when
the person with a disability (or anyone for that matter) has to take more
time and energy beyond what would have been their norm to complete a given
Task".  

I was trying to say, when a person with a disability or anyone goes well
beyond their typical norm to navigate and use a web resource, it is likely
an accessibility issue.  Let's say, it takes me (generally speaking) ten
minutes to fill out a form (a well formulated and easy to navigate form).
If I go to a different web resource where the same information is being
required and it takes me 20 minutes, I now have an increase in time and
energy.  If a person without a disability has no time differences between
the two web resources as described above, in terms of filling out the forms,
there is an accessibility issue.  This is somewhat difficult to put this
into words.  Hope this makes sense.
> 
> When a usability issue potentially becomes an accessibility barrier is when
> the person with a disability (or anyone for that matter) has to take more
> time and energy beyond what would have been their norm to complete a given
> task.  
> 
> For example, if a person without a disability were able to navigate a
> particular web resource, interact with content and complete the intended
> goal in a given period of time, it might be expected that a person with a
> disability could do the same task but it may take longer.  When the typical
> take longer time period or energy level is unduly increased for the person
> with a disability (beyond what would have been their typical) the issue now
> becomes one of accessibility.
> 
> 
> Roberto C:
> I can agree with tha basic concept within this first draft, but I'm having
> some doubt; the real difficult thing is to quantify the maximun amount
> (absolute or %) of time or effort that is required for each site (or kind
> of) to remain into usability domain; how can we set a range of time periods?
> How can we transform the word "typical" into a really testable concept? And,
> above all, does this effort to measure in numbers the difference between
> usability and accessibility really make sense?

We could set a percentage factor but where those numbers would lie, I have
no idea.  Do you have any ideas on numbers?

Doyle
> 
> My best regards,
> 
> Roberto Castaldo
> -----------------------------------
> www.Webaccessibile.Org coordinator
> IWA/HWG Member
> rcastaldo@webaccessibile.org
> r.castaldo@iol.it
> Mobile 348 3700161
> Icq 178709294
> -----------------------------------
> 
> 
Received on Wednesday, 12 May 2004 14:22:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:30 GMT