Re: 48-Hour Call for Consensus (CfC): FPWD of Revised CAPTCHA Note

+1

On Mon, Jun 25, 2018, 8:08 PM Scott Hollier <scott@hollier.info> wrote:

> +1 from me. Great work everyone and looking forward to the next steps.
>
> Scott.
>
>
> 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.
>
> -----Original Message-----
> From: White, Jason J <jjwhite@ets.org>
> Sent: Tuesday, 26 June 2018 12:44 AM
> To: Janina Sajka <janina@rednote.net>; Accessible Platform Architectures
> Administration <public-apa-admin@w3.org>
> Subject: RE: 48-Hour Call for Consensus (CfC): FPWD of Revised CAPTCHA Note
>
> +1. All of my comments can reasonably be addressed for the next draft.
>
> > -----Original Message-----
> > From: Janina Sajka <janina@rednote.net>
> > Sent: Monday, June 25, 2018 12:32 PM
> > To: Accessible Platform Architectures Administration <public-apa-
> > admin@w3.org>
> > Subject: 48-Hour Call for Consensus (CfC): FPWD of Revised CAPTCHA
> > Note
> >
> > Colleagues:
> >
> > This is a Call for Consensus (CfC) to the Accessible Platform
> > Architectures (APA) Working Group on the publication of a First Public
> > Working Draft (FPWD) of an updated and revised "Inaccessibility of
> CAPTCHA" document:
> >
> > "https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawg
> > it.c om%2Fw3c%2Fapa%2F1f5febb77be9c09906899174ae21e5ff7302e443%2Fcaptc
> > ha%2Findex.html&data=02%7C01%7Cjjwhite%40ets.org%7Cc53f54a50ae7450f
> > d6a008d5dab938c2%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C6
> > 36655411421129970&sdata=GIMiPuNQaiHbD5KsEQiPXXGJBdSFyXGaJEGOOk2Fj
> > 6Y%3D&reserved=0
> >
> > Please note the quick turnaround on this CfC. Comments are due by
> > close of business Boston time Wednesday. If you need more time, please
> advise.
> >
> > A revision and update of our 2004 W3C Note has long been on our agenda.
> > Thanks to assistance from our Research Questions Task Force (RQTF), we
> > finally have a document we believe can shortly update our published
> > guidance on this topic. We are seeking wide review in the FPWD process.
> > We are also expecting at least one more draft publication seeking wide
> > review call before finalizing our updated document as a W3C Note.
> >
> > Please review the document at the above URI. Please note that several
> > editorial tweaks are expected before publication as a FPWD, but no
> > substantive changes are contemplated.
> >
> > *       ACTION TO TAKE
> >
> > This CfC is now open for objection, comment, as well as statements of
> > support via email. Silence will be interpreted as support, though
> > messages of support are certainly welcome.
> >
> > If you object to this proposed action, or have comments concerning
> > this proposal, please respond by replying on list to this message no
> > later than 5:00 PM close of business Boston Time, Tuesday 27 June.
> >
> > Janina
> >
> > ----------------------------------------------------------------------
> > --------
> >
> > Janina Sajka
> >
> > Linux Foundation Fellow
> > Executive Chair, Accessibility Workgroup:
> > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fa1
> > 1y.org&data=02%7C01%7Cjjwhite%40ets.org%7Cc53f54a50ae7450fd6a008d5d
> > ab938c2%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C6366554114
> > 21129970&sdata=KcbZ3r43pAAoHs%2FG22HhzioSG%2BkcSH9quGTRhTvWmCM
> > %3D&reserved=0
> >
> > The World Wide Web Consortium (W3C), Web Accessibility Initiative
> > (WAI) Chair, Accessible Platform Architectures
> > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fw
> > ww.w3.org%2Fwai%2Fapa&data=02%7C01%7Cjjwhite%40ets.org%7Cc53f54a5
> > 0ae7450fd6a008d5dab938c2%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%
> > 7C0%7C636655411421129970&sdata=%2FMPU8Pf3mCEOzvZQ2o2bSWi3MOIC6
> > au8CGOPkYDUgqA%3D&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 Tuesday, 26 June 2018 02:25:52 UTC