Re: CFC - Publish Understanding and Techniques documents with WCAG 2.1

+1 to David and Jon.

I agree to the proposal for coordinated publication of our documents, but
stand with the editorial change from David & Jon as a condition of moving
forward. Is there a process or publication issue that would frustrate that
quick edit?

JF

On Thu, May 31, 2018 at 8:30 AM, Jonathan Avila <jon.avila@levelaccess.com>
wrote:

> I agree with David – if the group passes the CFC then I would recommend
> removing language rather than adding an editor’s note.  If the CFC doesn’t
> pass then I am fine in regards to the understanding documents.
>
>
>
> Jon
>
>
>
>
>
> *From:* David MacDonald [mailto:david100@sympatico.ca]
> *Sent:* Thursday, May 31, 2018 12:10 AM
> *To:* Andrew Kirkpatrick
> *Cc:* Jonathan Avila; WCAG
> *Subject:* Re: CFC - Publish Understanding and Techniques documents with
> WCAG 2.1
>
>
>
> > How about if we include an editor’s note in the non-text contrast
> understanding document saying that there was a late-breaking change and
> that the understanding content would be updated in the next few days?
>
>
>
> I'd rather just strike the 2 paragraphs about hit area... that's going to
> cause a lot of confusion,
>
>
>
> The editor's note could raise alarms...
>
>
>
> We can get the finer points in the next couple of weeks.
>
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613.235.4902
>
> LinkedIn
> <http://www.linkedin.com/in/davidmacdonald100>
>
> twitter.com/davidmacd
>
> GitHub <https://github.com/DavidMacDonald>
>
> www.Can-Adapt.com <http://www.can-adapt.com/>
>
>
>
> *  Adapting the web to all users*
>
> *            Including those with disabilities*
>
>
>
> If you are not the intended recipient, please review our privacy policy
> <http://www.davidmacd.com/disclaimer.html>
>
>
>
> On Wed, May 30, 2018 at 11:10 PM, Andrew Kirkpatrick <akirkpat@adobe.com>
> wrote:
>
> How about if we include an editor’s note in the non-text contrast
> understanding document saying that there was a late-breaking change and
> that the understanding content would be updated in the next few days?
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
>
> *From: *Jonathan Avila <jon.avila@levelaccess.com>
> *Date: *Wednesday, May 30, 2018 at 20:29
> *To: *WCAG <w3c-wai-gl@w3.org>
> *Subject: *RE: CFC - Publish Understanding and Techniques documents with
> WCAG 2.1
> *Resent-From: *WCAG <w3c-wai-gl@w3.org>
> *Resent-Date: *Wednesday, May 30, 2018 at 20:26
>
>
>
> In my opinion – if the CFC on non-text contrast passes, we would need to
> update the understanding for non-text contrast before publishing these.
> Without that update publication of the understanding document would only
> cause confusion.  Without that information I can’t say plus one.
>
>
>
> Jonathan
>
>
>
> *From:* Andrew Kirkpatrick <akirkpat@adobe.com>
> *Sent:* Wednesday, May 30, 2018 3:57 PM
> *To:* WCAG <w3c-wai-gl@w3.org>
> *Subject:* CFC - Publish Understanding and Techniques documents with WCAG
> 2.1
> *Importance:* High
>
>
>
> Call For Consensus — ends Friday June 1st at 3:30pm Boston time.
>
>
>
> The Working Group has discussed the publication of the Understanding
> documents and republication of techniques in conjunction with the release
> of WCAG 2.1 as a W3C Recommendation. The Understanding document is
> understood to need to continue to evolve, but the view of the Working Group
> is that the documents should be published at the same time as the WCAG 2.1
> Recommendation. This will be the first time that the Techniques and
> Understanding documents will be published outside of the Technical Reports
> space at the W3C, but this will also allow the Working Group to update the
> documents on an ongoing basis rather than on a multiple-month schedule.
>
>
>
> The proposed consensus position is that these documents should be
> published at the same time as the WCAG 2.1 Recommendation.
>
>
>
> Current editor’s draft for Understanding: https://w3c.github.io/wcag21/
> understanding/
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwcag21%2Funderstanding%2F&data=02%7C01%7Cakirkpat%40adobe.com%7C8798b606da5144986fc408d5c68d825f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636633233437302968&sdata=JwIrp2bEpn%2B2vMTiQTfHX4vkOwpuDWIWpq7P24MCYWc%3D&reserved=0>
>
>
>
> Call minutes: https://www.w3.org/2018/05/29-ag-minutes.html#item02
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2018%2F05%2F29-ag-minutes.html%23item02&data=02%7C01%7Cakirkpat%40adobe.com%7C8798b606da5144986fc408d5c68d825f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636633233437302968&sdata=tZjpH%2BXr2RTIvAy1Y1UZ3APbtvShSh2SJTZ0wP%2BJJQQ%3D&reserved=0>
>
>
>
> If you have concerns about this proposed consensus position that have not
> been discussed already and feel that those concerns result in you “not
> being able to live with” this decision, please let the group know before
> the CfC deadline.
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C54093524ef264326424008d51cd66c05%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446629619786436&sdata=c5UP0xiniJIppvd6Esu1XA%2FbX1ykpABkhgCCmBp%2Fht8%3D&reserved=0>
>
>
>
>
>
>
>



-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion