RE: First two comment response branches uploaded

Thank you, Janina, for this update.

I think you are right not to cite WCAG 2 in connection with an independent volume control. The relevant success criterion (1.4.2) only applies to audio that is played automatically, and can also be satisfied by ensuring that a mechanism is available to pause or stop the audio.

-----Original Message-----
From: Janina Sajka <janina@rednote.net>
Sent: Thursday, February 21, 2019 12:00 PM
To: public-rqtf@w3.org
Subject: First two comment response branches uploaded

Colleagues:

Per our conversation on this week's call, there are now two new github branches providing initial draft responses to comments we've received on our wide-review CAPTCHA draft.

1.)The editorial-captcha branch currently contains only the
spelling correction for the word "vicious:"

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fraw.githack.com%2Fw3c%2Fapa%2Feditorial-captcha%2Fcaptcha%2Findex.html&amp;data=02%7C01%7Cjjwhite%40ets.org%7C2df40b85b7114821b96108d6981e10da%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636863652229620034&amp;sdata=Vgc%2FRRRu%2FTmhbJsFnWX0z3Yjx3tfNzsl1M%2BX4XwlZvw%3D&amp;reserved=0


2.)The wcag-captcha branch is my first pass at reinforcing the
importance of following WCAG despite the fact that WCAG contains an exemption for CAPTCHA. This branch is here:

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fraw.githack.com%2Fw3c%2Fapa%2Fwcag-captcha%2Fcaptcha%2Findex.html&amp;data=02%7C01%7Cjjwhite%40ets.org%7C2df40b85b7114821b96108d6981e10da%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636863652229630043&amp;sdata=c0%2FoVdH9vVAZN6h%2BV1H7V6zS5e5qspvT9GL0D52Txdw%3D&amp;reserved=0

My edits come at two locations in our doc.

a.)I added the concept of an "independent volume control"
where we discuss the general lack of pause, play, rewind, and
fast forward. However, I did not specifically identify any WCAG
criteria in this edit.

b.)I revised the paragraph where we note the WCAG
exemption for CAPTCHA and added a summation paragraph to
that same introductory section to reinforce the notion
that WCAG should still be observed, even though the
content of the CAPTCHA has itself been exempted. This
forced me to find a term to more precisely name what
WCAG specifically exempts which WCAG itself fails to do.

I've settled on the term "payload," but we need to
consider whether that's a good term.  Is it too obscure?
Will it prove a problem for translations of our eventual
note?

Here's the dict definition of payload:

     1. The part of a missile or torpedo that carries the explosive charge.
          2. The goods carried by a large vehicle.

Very interested in your reactions to this term.

Best,

Janina

--

Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fa11y.org&amp;data=02%7C01%7Cjjwhite%40ets.org%7C2df40b85b7114821b96108d6981e10da%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636863652229630043&amp;sdata=%2FY%2F3K8TefslUONiLaavD8vw%2F6AbO1HkBma%2BJxEHXa80%3D&amp;reserved=0

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectureshttps://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2Fwai%2Fapa&amp;data=02%7C01%7Cjjwhite%40ets.org%7C2df40b85b7114821b96108d6981e10da%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636863652229630043&amp;sdata=W2q8o9J10Bif3IQMwW9aA5c8T0sIqQ3eXN8t4VukRYs%3D&amp;reserved=0



________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________

Received on Thursday, 21 February 2019 21:09:45 UTC