Re: Use case / scenario

Hi Howard,

> You're welcome. Looks good to me. 


Thank you! 

> One typo I see: "may" instead of "Mei" in line: What may thinks when she uses QuickRef and the Techniques and Understanding documents it links out to:


Woops, fixed! 

> I agree with Shawn on the expertise level.

Have updated! 

Best,
Hidde

—

Web Accessibility Specialist ・ https://w3.org/people/hidde <https://w3.org/people/hidde> ・ Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)

> On 14 Apr 2020, at 18:33, Howard Kramer <howard.kramer@colorado.edu> wrote:
> 
> Hi Hidde,
> 
> You're welcome. Looks good to me. 
> 
> One typo I see: "may" instead of "Mei" in line: What may thinks when she uses QuickRef and the Techniques and Understanding documents it links out to:
> 
> I agree with Shawn on the expertise level.
> 
> thanks,
> Howard
> From: Hidde de Vries <hidde@w3.org>
> Sent: Tuesday, April 14, 2020 8:52 AM
> To: Howard Kramer <howard.kramer@colorado.edu>
> Cc: wai-eo-editors <wai-eo-editors@w3.org>
> Subject: Re: Use case / scenario
>  
> Hi Howard,
> 
> Thanks again for sending this! 
> 
> I've tweaked it a bit, so that it fits a little more with the others. The updated version now has just a first name, and lists the problems outside the introduction as “the person's reaction”. 
> 
> This new scenario now exists as 'Mei': https://github.com/w3c/wai-wcag-supporting-documents-redesign/wiki/Current-user-flows#mei <https://github.com/w3c/wai-wcag-supporting-documents-redesign/wiki/Current-user-flows#mei>, and I've added “corporate trainer / university instructor” under use cases.
> 
> Please let me know if there's anything you'd like to change to it still. 
> 
> Best,
> Hidde
> 
> —
> 
> Web Accessibility Specialist ・ https://w3.org/people/hidde <https://w3.org/people/hidde> ・ Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)
> 
>> On 14 Apr 2020, at 13:35, Hidde de Vries <hidde@w3.org <mailto:hidde@w3.org>> wrote:
>> 
>> Hi Howard,
>> 
>> Many thanks for this, that's great! I will let you know when I've updated the document.
>> 
>> Best,
>> Hidde
>> —
>> 
>> Web Accessibility Specialist ・ https://w3.org/people/hidde <https://w3.org/people/hidde> ・ Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)
>> 
>>> On 11 Apr 2020, at 21:43, Howard Kramer <howard.kramer@colorado.edu <mailto:howard.kramer@colorado.edu>> wrote:
>>> 
>>> Hi Hidde,
>>> 
>>> As per my input on the last call I wrote up this scenario for the issue(s) I was discussing. Let me know if you have any questions.
>>> 
>>> Thanks,
>>> Howard
>>> 
>>> John Doe - corporate trainer, university instructor
>>> 
>>> Wants to explain how to use WCAG to evaluate pages. Has developers/students use different heuristics including easy checks, to audit for accessibility. He has them identify the principle (https://www.w3.org/WAI/fundamentals/accessibility-principles/ <https://www.w3.org/WAI/fundamentals/accessibility-principles/>) and the guideline and sub-guideline (https://www.w3.org/WAI/WCAG21/quickref/ <https://www.w3.org/WAI/WCAG21/quickref/>) for each issue they identify. However, quickref often refers to success criteria but does not explain what it is or even link to information about it. This is confusing to John Doe and his students who would like to know exactly how SC fits into WCAG and checking for accessibility.