Updated the section on the pagination objectives - #3041
Open
mattgarrish wants to merge 2 commits into
Open
Conversation
mattgarrish
requested review from
GeorgeKerscher,
avneeshsingh,
clapierre,
gautierchomel and
gregoriopellegrino
July 6, 2026 16:58
Member
Author
|
The diff's not going to help much with these changes, but if you want to review the original text it can be accessed through the editor's draft here: https://w3c.github.io/epub-specs/epub34/a11y-understand/#page-nav |
iherman
added
the
Spec-A11yExplainer
sueneu
reviewed
Jul 7, 2026
Comment on lines
+785
to
+787
| page break locations in an <a data-cite="epub-3#dfn-epub-publication">EPUB publication</a>. Its | ||
| purpose is to provide users with an easy means of accessing the same location across different | ||
| device screen sizes and user text preferences.</p> |
Contributor
There was a problem hiding this comment.
Suggested change
| page break locations in an <a data-cite="epub-3#dfn-epub-publication">EPUB publication</a>. Its | |
| purpose is to provide users with an easy means of accessing the same location across different | |
| device screen sizes and user text preferences.</p> | |
| page break locations in an <a data-cite="epub-3#dfn-epub-publication">EPUB publication</a>. Specifying these static locations allows multiple users to navigate to the same location within a publication, even when each user is reading on a different device. A static location remains identical across all reading systems, independent of screen size or user text preferences. </p> |
sueneu
reviewed
Jul 7, 2026
Comment on lines
+806
to
+808
| <p>When a page list is provided, a <a data-cite="epub-3#dfn-epub-reading-system">reading system</a> | ||
| can generate a "go to page" interface in which users can plug in the page number that they wish | ||
| to move to and know that they will end up in the same place as readers of the static source. |
Contributor
There was a problem hiding this comment.
Suggested change
| <p>When a page list is provided, a <a data-cite="epub-3#dfn-epub-reading-system">reading system</a> | |
| can generate a "go to page" interface in which users can plug in the page number that they wish | |
| to move to and know that they will end up in the same place as readers of the static source. | |
| <p>When a page list is provided, a <a data-cite="epub-3#dfn-epub-reading-system">reading system</a> | |
| can generate a navigation interface that allows users to input a specified page number and navigate directly to the corresponding content. |
sueneu
reviewed
Jul 7, 2026
Comment on lines
+913
to
+924
| <p>When seeking accessible publications for mixed print-digital reading environments, the first | ||
| thing an individual wants to be sure of is that the digital edition is the same as the print | ||
| edition. Different editions of a publication can differ not only in the content they contain but | ||
| in how they are paginated. Print publications, for example, will have different pagination | ||
| between their hard and soft cover editions. Different editions of the same book often also have | ||
| different pagination as new content gets added or existing content gets revised or removed.</p> | ||
|
|
||
| <p>An <a data-cite="epub-3#dfn-epub-publication">EPUB publication</a> with a page list and page | ||
| break markers loses its accessibility when it is not possible for users to determine what static | ||
| edition the pagination corresponds to. The <a data-cite="epub-a11y#sec-page-src">source of the | ||
| pagination</a> [[epub-a11y]] has to be specified in the metadata to allow users to determine | ||
| whether if they have the right digital edition.</p> |
Contributor
There was a problem hiding this comment.
Suggested change
| <p>When seeking accessible publications for mixed print-digital reading environments, the first | |
| thing an individual wants to be sure of is that the digital edition is the same as the print | |
| edition. Different editions of a publication can differ not only in the content they contain but | |
| in how they are paginated. Print publications, for example, will have different pagination | |
| between their hard and soft cover editions. Different editions of the same book often also have | |
| different pagination as new content gets added or existing content gets revised or removed.</p> | |
| <p>An <a data-cite="epub-3#dfn-epub-publication">EPUB publication</a> with a page list and page | |
| break markers loses its accessibility when it is not possible for users to determine what static | |
| edition the pagination corresponds to. The <a data-cite="epub-a11y#sec-page-src">source of the | |
| pagination</a> [[epub-a11y]] has to be specified in the metadata to allow users to determine | |
| whether if they have the right digital edition.</p> | |
| <p>The <a data-cite="epub-a11y#sec-page-src">source of the pagination</a> [[epub-a11y]] has to be specified in the metadata to allow users to determine if they have the right digital edition.</p> | |
| <p>An <a data-cite="epub-3#dfn-epub-publication">EPUB publication</a> containing a page list and page break markers cannot be considered fully accessible if users are unable to identify the corresponding source edition. Pagination and content layout frequently vary across different editions of the same publication; for example, the pagination of a hardcover edition often differs from that of the softcover edition.</p> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The original text of these sections came from the EPUB Accessibility 1.2 specification but it was kept minimal to avoid overloading each objective with explanatory text. This pull request expands each of the sections to more fully cover the requirements. (I'm going to look at the media overlay sections next.)
This link goes to the start of the revised sections:
https://raw.githack.com/w3c/epub-specs/understanding/epub-obj/epub34/a11y-understand/index.html#page-nav
Preview | Diff