W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2022

RE: Page break locators

From: Jonathan Avila <jon.avila@levelaccess.com>
Date: Tue, 28 Jun 2022 18:00:41 +0000
To: "WCAG list (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
Message-ID: <BL1PR03MB6120804BA9FB4BD20521B87FF1B89@BL1PR03MB6120.namprd03.prod.outlook.com>
  *   making the role aspect more explicit:

That's what I wrote to clarify in October in issue 2084.  I don't think it's necessary but if it would help the SC to pass then it could be good.


From: Alastair Campbell <acampbell@nomensa.com>
Sent: Tuesday, June 28, 2022 1:24 PM
To: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: Page break locators

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi everyone,

In the after-meeting chat we wondered if an updated definition of page break locators<https://w3c.github.io/wcag/guidelines/22/#dfn-pagebreak-locators> might help somewhat.

For example, making the role aspect more explicit:
"programmatically determinable<https://w3c.github.io/wcag/understanding/page-break-navigation.html#dfn-programmatically-determined> destination markers with a role<https://w3c.github.io/wcag/guidelines/22/#dfn-role>  to indicate page breaks in an alternative version of the document."

Kind regards,



@alastc / www.nomensa.com<http://www.nomensa.com>
Received on Tuesday, 28 June 2022 18:00:58 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 28 June 2022 18:01:01 UTC