W3C home > Mailing lists > Public > public-wai-evaltf@w3.org > April 2012

Re: Step 4a: Check for the Broadest Variety of Use Cases

From: Michael S Elledge <elledge@msu.edu>
Date: Thu, 05 Apr 2012 10:00:29 -0400
Message-ID: <4F7DA57D.8070400@msu.edu>
To: public-wai-evaltf@w3.org
Hi All--

I read "use case" as meaning "scenario," so that the intention would be 
to consider the different circumstances when interacting with a site. 
So, one scenario would be a person who is blind using a screen reader. 
Another would be a person with low vision using a screen enlarger. A 
third would be a person who has dexterity problems who is sighted but 
using a mouth stick. And so forth.

Mike

On 4/5/2012 7:45 AM, detlev.fischer@testkreis.de wrote:
> Hi Martijn,
>
> In my understanding, a 'use case' refers mainly to particular user aims, translated into a sequence of user actions towards a particular  goal. These would be covered by the 'complete processes' included in  the evaluation, such as filling out and submitting a form (with error handling), or using site search and navigating to a hit. Often, such use cases will go beyond page boundaries (or bring up new states of the page dynamically). An assessment of the site under test would need to consider what can /  should be done with it and select important processes / use cases accordingly.
>
> But maybe you apply the term 'use case' in a different way, meaning different modalities of use (such as mouse use, keybord use, screen reader use)? In many ways, the individual SC checks to be carried out will already cover such modalities: for example, checking SC 2.1.1 means verifying that everything can be done with the keyboard.
>
> What level of WCAG conformance is aimed at seems to be on another level.
>
> Regards,
> Detlev
>> On 5 Apr 2012, at 10:15, Martijn Houtepen wrote:
>>
>>> Hi Eval TF,
>>>
>>> As we are currently filling in step 4 and 5, we would like your
>>> input on Step 4.a: "Check for the Broadest Variety of Use Cases" (http://www.w3.org/TR/WCAG-EM/#step4a
>>> )
>>>
>>> My question is very simple: How does one check for the broadest
>>> variety of use cases? Can we exclude specific use cases in an
>>> evaluation? Should we include extra criteria in some use cases?
>>>
>>> The editor note: "This section will instruct evaluators to apply all
>>> WCAG 2.0 Success Criteria for each web page in the selected sample,
>>> and in doing so to consider the broadest possible set of users,
>>> software tools, and use cases as scoped out in Step 1.d: Define the
>>> Context of Website Use."
>>>
>>> This seems to imply that we simply state: apply all WCAG 2.0 success
>>> criteria to the sample, except for situations in which the use is
>>> limited to or specifically for a certain group.
>>>
>>> So on the (public) website of some institute for the blind we apply
>>> level AAA criteria for visually impaired users; and on the intranet
>>> website of a company we limit the accessibility support to one
>>> browser or AT.
>>>
>>> What do you think?
>>>
>>> All the best,
>>>
>>> Martijn Houtepen
>>>
>>> Stichting Accessibility - Expertisecentrum ICT-toegankelijkheid
>>> Oudenoord 325
>>> 3513 EP Utrecht
>>> 030 - 239 8270
>>> www.accessibility.nl
>>> @AccessibilityNL
>>>
>> -- 
>> Detlev Fischer
>> testkreis - das Accessibility-Team von feld.wald.wiese
>> c/o feld.wald.wiese
>> Borselstraße 3-7 (im Hof)
>> 22765 Hamburg
>>
>> Tel   +49 (0)40 439 10 68-3
>> Mobil +49 (0)1577 170 73 84
>> Fax   +49 (0)40 439 10 68-5
>>
>> http://www.testkreis.de
>> Beratung, Tests und Schulungen für barrierefreie Websites
>>
>>
>>
>
>

-- 
Michael S. Elledge
Associate Director
Usability/Accessibility Research and Consulting
Michigan State University
Kellogg Center
219 S. Harrison Rd Room 93
East Lansing, MI  48824
517-353-8977
Received on Thursday, 5 April 2012 14:01:04 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:52:13 GMT