Understanding Success Criterion 2.4.13: Page Break Navigation

Success Criterion 2.4.13 Page Break Navigation (Level A): For web content with page break locators, a mechanism is available to navigate to each locator.

Status

This understanding document is part of the draft WCAG 2.2 content. It may change or be removed before the final WCAG 2.2 is published.

Intent

The purpose of this success criterion is to allow people using assistive technology to find references to content based on the page break locators found in the default view or printed version of a publication.

Page numbering has long been a fundamental way to identify and communicate the location of written content. Page numbers are used constantly in references, footnotes, endnotes, and bibliographies. Particularly, they are critical in academic and learning environments.

Digital publishing has provided valuable access to content for people who are blind, have low vision, dyslexia or other cognitive disabilities. In order to consume the information the content may be adapted to use a different layout, or presented to them using assistive technology. If there is no clear way to find a specific page from the print version that was referenced by a professor in class, because the electronic version is zoomed-in and that paragraph is on page 145 of the user's version of the content, the user misses out on valuable and sometimes critical information to understanding the reference.

In publishing, there can be many different editions of a work, e.g. a second edition or a paperback edition. There is a requirement (separate from accessibility) for metadata in digital publications like EPUB to identify the edition of the title of which this digital version represents. The page break locaters would be aligned with the specified edition.

Note

Statically paginated formats (e.g., PDF) where the user agents include a mechanism to navigate by page typically meet this success criteria by default. The user agents for the EPUB format also typically provide the navigation mechanism if a page list is included. Web browsers do not have a standard page navigation mechanism, so for HTML content with page break locators it is the author responsibility to add that mechanism.

Benefits

Examples

Related Resources

Resources are for information purposes only, no endorsement implied.

Techniques

Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. However, it is not necessary to use these particular techniques. For information on using other techniques, see Understanding Techniques for WCAG Success Criteria, particularly the "Other Techniques" section.

Sufficient Techniques

  1. H99: Provide page list navigation

Key Terms

page break locators

programmatic markers that are arranged in a meaningful sequence to determine the location of a page in relation to others in the set.

Examples would be:

  • A digital version of an ebook that has a print version, it includes the page break locators to align with the print edition.
  • A digital book is published with no print equivalent and page break locators are inserted which supports direct navigation across platforms and form factors.