W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2012

Re: Feasibiity as a factor for Level Selection

From: Jeanne Spellman <jeanne@w3.org>
Date: Fri, 27 Jan 2012 13:45:28 -0500
Message-ID: <4F22F0C8.8020306@w3.org>
To: Jim Allan <jimallan@tsbvi.edu>
CC: wed@csulb.edu, WAI-UA list <w3c-wai-ua@w3.org>
Agreed, this is a useful analysis and I have already grabbed part of it 
to put into the proposal for the level definitions.

My question is: deterministic vs. inferential is one part of ease, but 
it certainly isn't all of it.  What are the factors that define ease? 
We already have existing implementations indicate ease, but what else?

What else makes a feature hard to implement?

jeanne

On 1/27/2012 1:10 PM, Jim Allan wrote:
> Wayne,
> thanks for doing the thinking and writing on this. A good place to
> start. I agree with Chaals it strikes a good balance for ease vs
> impact. That's where we as a group can decide to push the level up or
> down.
>
> Jim
>
> On Thu, Jan 26, 2012 at 7:40 PM, Wayne Dick<wayneedick@gmail.com>  wrote:
>> Hi All,
>>
>> I wrote this to help us narrow feasibility to a reasonable range, so
>> we could use it in choosing Level A through AAA.  We don't want to let
>> developer's off reasonable tasks, but we can't require excessive
>> development.
>>
>> http://www.csulb.edu/~wed/Feasibility.html
>>
>> Wayne
>>
>
>
>
Received on Friday, 27 January 2012 18:45:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 January 2012 18:45:32 GMT