Re: CFC - WCAG 2.2 Page break navigation normative text

That is too bad because I was going to +1 to Davids comments

On Fri, Jul 15, 2022, 2:31 PM Alastair Campbell <acampbell@nomensa.com>
wrote:

> AG Working Group members,
>
>
>
> As we have received substantial negative feedback during this CfC, this
> CfC fails and is not agreed on as a consensus opinion of the working group.
>
>
>
> This decision will be recorded at https://www.w3.org/WAI/GL/wiki/Decisions
> .
>
>
>
> There has been a request to retain the main technique (H99
> <https://w3c.github.io/wcag/techniques/html/H99>), generalised to
> Multiple ways at the advisory level. This will come back to the group in
> future.
>
>
>
> Kind regards,
>
>
>
> -Alastair
>
>
>
>
>
> *From: *Alastair Campbell
> *Date: *Wednesday, 22 June 2022 at 16:39
> *To: *WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
> *Subject: *CFC - WCAG 2.2 Page break navigation normative text
>
> Call For Consensus — ends Monday June 27th at midday Boston time.
>
>
>
> The Working Group has previously discussed the WCAG 2.2 SC Page break
> navigation and the Normative text needs to be approved by CFC.
>
>
>
> It can be previewed in the editor’s draft:
>
> https://w3c.github.io/wcag/guidelines/22/#page-break-navigation
>
>
>
> The SC was last discussed in a meeting May 17th:
>
> https://www.w3.org/2022/05/17-ag-minutes#item05
>
>
>
> The change history is here:
>
>
> https://github.com/w3c/wcag/commits/main/guidelines/sc/22/page-break-navigation.html
>
>
> https://github.com/w3c/wcag/commits/e2e4cda3667e37a8a12ceaf0dd81f7c5595195e8/guidelines/sc/22/fixed-reference-points.html?browsing_rename_history=true&new_path=guidelines/sc/22/page-break-navigation.html&original_branch=main
>
>
>
> The survey is available here:
>
> https://www.w3.org/2002/09/wbs/35422/wcag22-page-break-nav/
>
>
>
> The github issues are listed here:
>
> https://github.com/w3c/wcag/issues?q=is%3Aissue+is%3Aopen+label%3A%222.4.13+Page+break+locators%22+
>
>
> (There is 1 open, related to an understanding content update.)
>
>
>
> 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.
>
>
>
> Kind regards,
>
> -Alastair
>
> --
>
>
>
> @alastc / www.nomensa.com
>
>
>
>
>
>
>