Re: Publish WCAG 2.1 FPWD

Agree with Alastair... I hope there is an elegant and easy way for the
community to post comments... perhaps a new issue for each new SC, or put
notes on closed PRs that although it is closed, it is open to get comments
... the SC managers can have responsibility for doing that.

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 Tue, Feb 21, 2017 at 6:57 PM, Alastair Campbell <acampbell@nomensa.com>
wrote:

> +1 to publish.
>
> I'd just note that, by the time it gets to announcement, it would really
> help if the links through to Issues / PRs could go to somewhere more useful.
>
> At the moment they (mostly?) go to closed issues/PRs. For the SCs I
> manage, can I open a new issue to take public comments?
>
> -Alastair
>
> ________________________________________
> From: Andrew Kirkpatrick <
> Sent: 21 February 2017 18:26
> To: WCAG
> Subject: CFC: Publish WCAG 2.1 FPWD
>
> Call For Consensus — ends Thursday February 23th at 1:30pm Boston time.
>
> The Working Group discussed the latest editor’s draft of WCAG 2.1 (
> https://rawgit.com/w3c/wcag21/FPWD_review/guidelines/index.html) and
> basedon a survey (https://www.w3.org/2002/09/wbs/35422/WCAG21FWPD/results)
> and a Working Group call (http://www.w3.org/2017/02/21-ag-minutes.html)
> where the majority of comments were resolved and no blocking issues
> remained.
>
>