Re: [wbs] response to 'WCAG Video Scripts - Thorough Review 2'

Hi Todd,

Many thanks for your thorough review and thoughtful comments! Please 
find some responses inline:


On 02/06/2021 17:24, Todd Libby via WBS Mailer wrote:
>> ---------------------------------
>> (Updated) Draft script for Success Criterion 1.3.5 "Identify Input
>> Purpose"
>>
>> ----
>> (Updated) Draft script for Success Criterion 1.3.5 "Identify Input
>> Purpose" (Nearby: previous version and changes made)
>> For each of your comments, please clearly indicate:
>>   * Location: eg. "SC 1.2.2 - Scene 2"
>>     * Priority: eg. "[e]" for editorial  or "[i]" for important
>>     * Current wording:
>>     * Suggested revision:
>>     * Rationale:
>>
>>
> 
>   * [ ] I am comfortable with this script as it currently is (no changes
> suggested)
>   * [x] Please consider my comments raised in GitHub or in the comments
> field below (for editors' discretion)
>   * [ ] I abstain from commenting and accept the decisions of the Working
> Group
> Comments:
> The line "We see Jonathan using the auto-complete for username (and maybe
> also password) on a different log-in page (for another website)." concerns
> me because it could convey that Jonathan can use the same username and
> password on any other sites he navigates to.

The sub-group made edits to address this particular concern.

The sub-group opened issue #69 on this script and welcomes your input:
  - https://github.com/w3c/wai-wcag-videos/issues/69


>> ---------------------------------
>> Draft script for Success Criterion 2.1.1 "Keyboard"
>>
>> ----
>> Draft script for Success Criterion 2.1.1 "Keyboard"
>> For each of your comments, please clearly indicate:
>>   * Location: eg. "SC 1.2.2 - Scene 2"
>>     * Priority: eg. "[e]" for editorial  or "[i]" for important
>>     * Current wording:
>>     * Suggested revision:
>>     * Rationale:
>>
>>
> 
>   * [ ] I am comfortable with this script as it currently is (no changes
> suggested)
>   * [x] Please consider my comments raised in GitHub or in the comments
> field below (for editors' discretion)
>   * [ ] I abstain from commenting and accept the decisions of the Working
> Group
> Comments:
> In the first scene, "She has a headset and using speech to operate the
> computer." seems to make more sense if it were "She has a headset and
> **is** using speech to operate the computer." Also, "We the screen and the
> email application opening and the message being started as she speaks the
> commands." reads better if it is something like, "We **see** the screen and
> the email application open, the message starts as she speaks the commands."

Fixed (both), thanks.

The sub-group opened issue #64 on this script and welcomes your input:
  - https://github.com/w3c/wai-wcag-videos/issues/64


>> ---------------------------------
>> Draft script for Success Criterion 2.1.3 "Keyboard (No Exception)"
>>
>> ----
>> Draft script for Success Criterion 2.1.3 "Keyboard (No Exception)"
>> For each of your comments, please clearly indicate:
>>   * Location: eg. "SC 1.2.2 - Scene 2"
>>     * Priority: eg. "[e]" for editorial  or "[i]" for important
>>     * Current wording:
>>     * Suggested revision:
>>     * Rationale:
>>
>>
> 
>   * [ ] I am comfortable with this script as it currently is (no changes
> suggested)
>   * [x] Please consider my comments raised in GitHub or in the comments
> field below (for editors' discretion)
>   * [ ] I abstain from commenting and accept the decisions of the Working
> Group
> Comments:
> Not sure of the necessity for "Niando is a middle school student." and the
> word "also" in, "he has muscular dystrophy, which also impacts her arms."
> There is also a typo. "[We hear **Naindo** (Niando) say the commands
> “draw line”]"

Fixed typos and removed this description in the script. We will review 
the persona and their appearances at a later stage.

The sub-group opened issue #66 on this script and welcomes your input:
  - https://github.com/w3c/wai-wcag-videos/issues/66


>> ---------------------------------
>> Draft script for Success Criterion 2.1.4 "Character Key Shortcuts"
>>
>> ----
>> Draft script for Success Criterion 2.1.4 "Character Key Shortcuts"
>> For each of your comments, please clearly indicate:
>>   * Location: eg. "SC 1.2.2 - Scene 2"
>>     * Priority: eg. "[e]" for editorial  or "[i]" for important
>>     * Current wording:
>>     * Suggested revision:
>>     * Rationale:
>>
>>
> 
>   * [ ] I am comfortable with this script as it currently is (no changes
> suggested)
>   * [x] Please consider my comments raised in GitHub or in the comments
> field below (for editors' discretion)
>   * [ ] I abstain from commenting and accept the decisions of the Working
> Group
> Comments:
> Typo: "[We hear Alex speak into his **heaset** (headset) dictating a news
> article]", "For longer passages of text, such as his article, **her** (he)
> prefers to use dictation software that converts his speech to text.", I
> think use of the Shift key in #5 should be replaced with either the Alt key
> or the Control key, since those are more widely used for keyboard
> interactions with content management systems in my experience.

This script has been put on hold for now due to conflicting suggestions.


>> ---------------------------------
>> Draft script for Success Criterion 2.3.1 "Three Flashes or Below
>> Threshold"
>>
>> ----
>> Draft script for Success Criterion 2.3.1 "Three Flashes or Below
>> Threshold"
>> For each of your comments, please clearly indicate:
>>   * Location: eg. "SC 1.2.2 - Scene 2"
>>     * Priority: eg. "[e]" for editorial  or "[i]" for important
>>     * Current wording:
>>     * Suggested revision:
>>     * Rationale:
>>
>>
> 
>   * [ ] I am comfortable with this script as it currently is (no changes
> suggested)
>   * [x] Please consider my comments raised in GitHub or in the comments
> field below (for editors' discretion)
>   * [ ] I abstain from commenting and accept the decisions of the Working
> Group
> Comments:
> "Manti has photosensitive reactions to certain types of flashing lights,
> such as strobe lights on the computer screen.". "Strobe lights" doesn't
> read right to me and would suggest "flickering images such as animated
> GIFs" or something similar. "such as images of strobe lights" is something
> tht I would lso suggest as well. All these things I have experienced when
> some content like this has triggered my migraine headaches.

The sub-group opened issue #67 on this script and welcomes your input:
  - https://github.com/w3c/wai-wcag-videos/issues/67


>> ---------------------------------
>> Draft script for Success Criterion 2.3.2 "Three Flashes"
>>
>> ----
>> Draft script for Success Criterion 2.3.2 "Three Flashes"
>> For each of your comments, please clearly indicate:
>>   * Location: eg. "SC 1.2.2 - Scene 2"
>>     * Priority: eg. "[e]" for editorial  or "[i]" for important
>>     * Current wording:
>>     * Suggested revision:
>>     * Rationale:
>>
>>
> 
>   * [ ] I am comfortable with this script as it currently is (no changes
> suggested)
>   * [x] Please consider my comments raised in GitHub or in the comments
> field below (for editors' discretion)
>   * [ ] I abstain from commenting and accept the decisions of the Working
> Group
> Comments:
> "Manti has photosensitive reactions to certain types of flashing lights,
> such as strobe lights on the computer screen." Again, I'd suggest using
> some wording other than "strobe lights" when conveying this message, to
> something such as my suggestion in 2.3.1

Noted; change from 2.3.1 will be reflected here too.


Regards,
   Shadi

-- 
Shadi Abou-Zahra - http://www.w3.org/People/shadi/
Accessibility Strategy and Technology Specialist
Web Accessibility Initiative (WAI)
World Wide Web Consortium (W3C)

Received on Monday, 21 June 2021 10:08:09 UTC