Re: [EXT] CFC - WCAG 2.2 Page break navigation normative text

-1
I agree with Wilco as well, the point that this is a poor fit for WCAG 2.2 makes sense to me. I agree that this success criterion applies heavily to EPUB without sufficiently addressing the broader potential applications of page break locators.
I do think that a Table of Contents could be a mechanism for navigating to each locator and would pass the SC.

From: Alastair Campbell <acampbell@nomensa.com>
Date: Wednesday, June 22, 2022 at 11:41 AM
To: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: [EXT] 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<http://www.nomensa.com>