Re: Draft changes to CAPTCHA Note - security and privacy

+1 This does help to set expectations for the remainder of the document. Thanks, Jason!

In reading through this draft, I’d like to propose an edit to the first paragraph of Section 1 (Introduction), which attempts to clarify the sentence meaning by identifying in parenthesis examples of resources that are attractive to aggregators.

Replace:

Web sites with resources that are attractive to aggregators such as sign-up web pages, travel and event ticket sites, web-based email accounts, and social media portals have taken measures to ensure that they can offer their service to individual users without exposing their data and content to web robots.

With:

Web sites with resources that are attractive to aggregators—such as sign-up web pages, travel and event ticket sites, web-based email accounts, and social media portals—have taken measures to ensure that they can offer their service to individual users without exposing their data and content to web robots.

Dave

> On 15 Aug 2018, at 08:58, Scott Hollier <scott@hollier.info> wrote:
> 
> To Jason
>  
> This is great work and in my opinion works well in clearly identifying the scope of the note while still acknowledging the fact that accessibility, privacy and security are all important access factors. It feeds in well from the introduction and also acknowledges why a little more detail is provided in the security section. In my opinion it gets the balance right based on our discussions and the feedback received. 
>  
> Scott.
>  
>  
>  
> <image001.gif>Dr Scott Hollier 
> Digital Access Specialist
> Mobile: +61 (0)430 351 909
> Web: www.hollier.info
>  
> Technology for everyone
>  
> WCAG 2.1 has arrived – is your organisation ready? Keep up-to-date by following @scotthollier on Twitter and subscribing to Scott’s digital access newsletter.
>  
> From: White, Jason J <jjwhite@ets.org> 
> Sent: Wednesday, 15 August 2018 2:12 AM
> To: Research Questions Task Force <public-rqtf@w3.org>
> Subject: Draft changes to CAPTCHA Note - security and privacy
>  
> In fulfillment of my action from last week, I’ve added material on security and privacy that explicitly confines the scope of the document.
>  
> I created a new section, and added the proposed text as a subsection that precedes the existing text on security of CAPTCHAs.
>  
> Please see section 2 of the branch at
> https://rawgit.com/w3c/apa/security-privacy-considerations/captcha/
>  
>  
> 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.
> 

--
David Sloan
--
UX Research Lead
The Paciello Group
https://www.paciellogroup.com
A VFO™ Company http://www.vfo-group.com/
--
This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.

Received on Wednesday, 15 August 2018 10:45:18 UTC