W3C home > Mailing lists > Public > public-rqtf@w3.org > June 2019

RE: Conclusions of draft CAPTCHA Note

From: White, Jason J <jjwhite@ets.org>
Date: Thu, 13 Jun 2019 15:02:52 +0000
To: Janina Sajka <janina@rednote.net>
CC: "public-rqtf@w3.org" <public-rqtf@w3.org>
Message-ID: <BN7PR07MB48493248B750BC25BE053B9AABEF0@BN7PR07MB4849.namprd07.prod.outlook.com>
Yes, I think you can introduce a subheading without enclosing it in a section element - at least, it's worth trying on a branch.

-----Original Message-----
From: Janina Sajka <janina@rednote.net>
Sent: Thursday, June 13, 2019 10:35 AM
To: White, Jason J <jjwhite@ets.org>
Cc: public-rqtf@w3.org
Subject: Re: Conclusions of draft CAPTCHA Note

Hi Jason, All:

White, Jason J writes:
> Revisiting the list of conclusions again, I wonder whether it should be stated explicitly that the cognitive and sensory demands imposed on the user by an interactive CAPTCHA challenge should be minimized so far as is possible while meeting the security objective. This could be a separate point, or an additional sentence in the fourth point.

I'm liking this suggestion. Let me mull it and add something late today.

Note that COGA wants an advisory when user data is being collected. I'm disinclined to say much like that in conclusory points. Too many lawyers!

>
> A simple heading such as "Summary" would be sufficient - we already state that we are summarizing the conclusions in this list.
>

Yeah, but we have a narrative paragraph both and below the unordered list. Can we drop an additional H level without marking an additional <section> ... </section> ?? Is that something respec will respect?

Janina


> -----Original Message-----
> From: Janina Sajka <janina@rednote.net>
> Sent: Wednesday, June 12, 2019 8:21 PM
> To: White, Jason J <jjwhite@ets.org>
> Cc: public-rqtf@w3.org
> Subject: Re: Conclusions of draft CAPTCHA Note
>
> Thanks for the review, Jason.
>
> What subheading might reinforce our conclusions? Would you perhaps put a nested head over the unordered list? Should we perhaps make these an ordered list--which might mean reording them?
>
> PS: I've made additional changes per discussion on the Editor's Draft today.
>
> *The beginning of the reCAPTCHA section has been altered slightly *to
> acknowledge there was a reCAPTCHA Version 1, which Google no *longer
> supports.
>
> *Our concluding paragraph in the reCAPTCHA section now also *points to
> the Google reCAPTCHA FAQ, because the FAQ clearly *states Version 2 is
> not going away.
>
> Next, I added a few sentences to the Turing Tokens discussion to briefly sketch a user oriented VPN service per discussions on our call.
>
>
> I have one more tweak I plan to accomplish tomorrow. There is still a DTMF reference in the Webex section that needs to say something more generally understandable. I've put this off until my next Webex call were I can go into the background on a side session and ask Webex to call my cell phone. I need to capture the exact language they're using.
> I should be able to achieve this Thursday morning.
>
> Janina
>
> White, Jason J writes:
> > Having regard to the conversation that occurred at the meeting today, I reviewed the conclusions of the CAPTCHA Note, as currently drafted.
> >
> > I think the conclusions already set forth all of the central observations that received overwhelming endorsement at the meeting today. In particular, the list of 5 major points(see the unordered list in the "conclusions" section) could be regarded as the basis of potential guidance to implementers.
> >
> > My only suggestion is that we may wish to give these points greater emphasis, perhaps proceeding so far as to characterize them as essential findings to be borne in mind by web application developers. A subheading would suffice for this purpose, though other strategies would serve equally well.
> >
> >
> > ________________________________
> >
> > 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.
> >
> > ________________________________
>
> --
>
> Janina Sajka
>
> Linux Foundation Fellow
> Executive Chair, Accessibility
> Workgroup:https://nam01.safelinks.protection.outlook.com/?url=http%3A%
> 2F%2Fa11y.org&amp;data=02%7C01%7Cjjwhite%40ets.org%7C2758cf56b26a41f43
> 78208d6ef94f6e3%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636959820
> 908822705&amp;sdata=O3SEXAm%2FjZqQTT30FN1yXXvPiRWCtE1eOU1XVnYCK1U%3D&a
> mp;reserved=0
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative
> (WAI) Chair, Accessible Platform
> Architectureshttps://nam01.safelinks.protection.outlook.com/?url=http%
> 3A%2F%2Fwww.w3.org%2Fwai%2Fapa&amp;data=02%7C01%7Cjjwhite%40ets.org%7C
> 2758cf56b26a41f4378208d6ef94f6e3%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C
> 0%7C0%7C636959820908822705&amp;sdata=YQGZbdaal6qeJqdlWmOFonGjy9ohrfRnI
> 2Ox7jr9U0Q%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.
>
> ________________________________

--

Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fa11y.org&amp;data=02%7C01%7Cjjwhite%40ets.org%7C24d2b9449728413e07ac08d6f00c49f6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636960332902791196&amp;sdata=wNbLCTU9NO%2FngJgvuWGwdIK73ZaTan3aRc1sb2qurJw%3D&amp;reserved=0

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectureshttps://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2Fwai%2Fapa&amp;data=02%7C01%7Cjjwhite%40ets.org%7C24d2b9449728413e07ac08d6f00c49f6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636960332902791196&amp;sdata=fGwx7YaegZb4ojjAC4OhjSsxj9tw2rkpsNFN72h7yy4%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, 13 June 2019 15:03:21 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 17 January 2023 20:26:46 UTC