Application

There are two [[wcag2]] accessible authentication success criteria — a minimum (3.3.8) and an enhanced (3.3.9) version — as well as a related success criterion for re-authentication (2.2.5). These have a combined goal of ensuring that users with certain cognitive disabilities are provided an easy-to-use and accessible login method for protected web sites, and that information is not lost if users have to reauthenticate themselves.

Not all users are able to remember usernames and passwords, transcribe verification access codes, or solve puzzles to gain entry which is why it is important that logins do not rely solely on methods that require these kinds of cognitive capabilities. It is also vital to ensure that users do not lose any information they have input if they are required to reauthenticate as this could prevent some users from being able to complete the task (i.e., they may continue to reach the time out just trying to re-enter the lost information).

It is not common that these success criteria will apply to EPUB publications, however. When a login is required, the more typical scenario is that a vendor will require users to log in to their reading system to access their publications. In this case, if the login does not meet the requirements of the minimum success criterion, then it is the reading system that is not accessible, not the individual publications it provides access to. Similarly, if the reading system loses the current state of a quiz or task at the time it forces reauthentication, there is nothing the publication can do about this.

Even in the case of EPUB publications served through a learning management system (LMS), it is more typical for the user to log in to the LMS. The LMS may use that information to track their activity, but again it is rarely the publications within the LMS that are secured.

One major reason that EPUB publications typically do not build in login requirements is because scripting support is not guaranteed. The reading system is more reliably going to have a connection to, or be able to connect to, the user's network. It is also more capable of being able to store information for later transmission to a publisher's server when a connection is not immediately available, as persistent storage is also not commonly available within EPUB publications. The lack of persistent state also means that a login in one EPUB content document likely will not persist into any of the others. That means a user might, for example, have to log in at the end of every chapter to complete embedded quizzes.

Locating

Despite the potential drawbacks of adding authentication to EPUB publications, nothing prevents a publisher from using logins. They are much rarer than on the web because a publication belongs to one user and so it does not have to be blocked internally from public access and there is no question if the user is human or not. Authentication typically only matters in the case where the publisher has to collect information; for example, from quizzes and other interactive content.

For these reasons, it is unlikely that logins will be found outside of educational material, which can help narrow down when to look for them. Since a login will typically require the user to have an account with the publisher, they are less likely to be found in general reading material.

But, while it may be highly uncommon to find logins, their possibility cannot be ignored when performing an accessibility review.

Unfortunately, there is no quick way to determine if a publication has a login attached to any of its content short of manually checking. The only useful aid that an EPUB publication provides is the scripting designation that has to be expressed in the package document manifest.

Knowing which files are scripted may help reduce the amount of work involved in finding logins, but that is only if scripting is used sparingly in the publication. If most or all of the EPUB content documents are scripted, it might be easier to read the JavaScript files. Even without a strong knowledge of scripting, the names of the various functions might provide clues to their purpose. For example, a function with "login" in its name would be a major flag to look more deeply into what the scripting is doing.

Ultimately, direct testing of all scripted content for accessibility is always advised (i.e., not trying to gauge the accessibility by looking only at the markup), so as long as an assessment is thorough in this regard any logins should be found in due course.

If a login is found, checking for a reauthentication requirement may still take some work. It should never be assumed that lack of mention of a timed session means that users will not be prompted to reauthenticate after a certain amount of time, or a certain amount of time without activity being registered. Verifying if there is a timeout, and checking what happens after reauthenticating, may require inspecting code to understand when a timeout is triggered. If the evaluator is not the publisher of the content, it may be faster to check with publisher whether session timeouts can occur and how best to test them.

Application

The [[wcag2]] consistent navigation success criterion (3.2.3) has a similar goal to the consistent help success criterion but in this case the objective is to make it easier for users on the web to find and use repeated navigational aids such as tables of contents, search boxes, and skip to content links. Having these aids in the same location, and the links within them ordered in the same way (when the links repeat), simplifies navigating a site.

But many of these kinds of navigation aids are not included in EPUB publications, at least in a way that they fall on the publisher to make accessible (i.e., being available across multiple content documents). It is the user's reading system that is going to make access to the table of contents, or landmarks, or page list, or a search box consistently available in its user interface. Likewise, information about what (virtual) page the user is on is handled by the reading system. Even the EPUB equivalent of a skip to content link — a landmark to the first page of body matter — is information for the reading system to use to advance the user; it is not content the user directly encounters in the publication.

If the reading system were to change the order of access to these features in the middle of reading a publication, that would be a failure of the reading system not the publisher. Similarly, if it were to change the order of the links within a navigation element — for example, change the order of the landmark links — that would also be a failure of the reading system.

Mini tables of contents

The most common case where the consistent navigation success criterion applies to EPUB publication is when chapters include mini tables of contents at their start. These are most typically found in educational works to provide quick access to all the subsections of a major topic.

In this case, the position of each of these mini tables of contents needs to be consistent relative to any other content at the beginning of the chapter or section. If the first mini table of contents occurs after the first chapter heading, for example, then the same pattern has to be followed in each subsequent chapter.

It is also worth noting that the pattern of placement has to be consistent, not that the same elements always have to appear. For example, if some chapters have a title followed by an epigraph, followed by an image to illustrate the concept being covered before the mini table of contents is provided, then it is acceptable if some chapters omit the epigraph and/or image so long as the order of the elements before the navigation is always consistent. It would only be a failure if the mini table of contents is sometimes placed before the heading, or between the epigraph and image.

The order of links within the mini tables of contents is not likely going to be relevant to check for this success criterion. Because each chapter's content is unique, the links are never going to be repeated from one chapter to the next so there is not a consistent order that has to be maintained.

Page numbering

Although page numbers provide a form of static navigation aid — indicating to the user where they are in a publication — their consistent placement in reflowable EPUB publications is out of scope for this success criterion. Page break markers in these documents will occur arbitrarily at locations that typically correspond to a statically paginated equivalent, like a print copy of the book.

The consistent identification of page break markers in reflowable publications is more typically a concern of the reading system, as it will provide the user the page number somewhere in its user interface.

Application

The [[wcag2]] reflow success criterion (1.4.10) seeks to ensure that content remains readable for users with low vision as they enlarge it. It requires that there be no loss of information or readability for vertically scrolling content at a width equivalent to 320 CSS pixels [[wcag2]].

The first thing to note about this success criterion is that the "scrolling" aspect of the definition applies to all EPUB publications whether they are read in a reading system that lays out the content in a scrolling manner or whether the reading system dynamically paginates the content. Dynamic pagination is just a feature of EPUB that takes a vertically scrolled document and splits it up for reading in a book-like manner.

The second thing to note is that the width and height sizes do not refer to the actual screen resolution of the device. The emphasis of the success criterion is on equivalence up to these sizes, which is why it notes that a viewport with a width of 1280 CSS pixels is equivalent to a width of 320 CSS pixels when it is zoomed to 400%. The example is just a common screen resolution and exhibits easy math to the 320 CSS pixel maximum.

What happens when zooming a 1280 CSS pixel viewport beyond 320 CSS pixels is out of scope, as is zooming any other starting resolution after it exceeds 320 CSS pixels in width. The success criterion is not saying that all viewports greater in width than 320 CSS pixels are out of scope.

The good thing about reflowable EPUB publications when it comes to meeting this success criterion is that they were designed to work exactly in the manner it anticipates. A reflowable EPUB publication is expected to work on many different device screens and with many different user preferences applied. The content has to reflow to fit within the paginated environment that reading systems provide as users rarely can scroll the content — if the content does not fit in the viewport, it is typically inaccessible to all users. Publishers are typically already aware of these reflow issues and how to ensure their content does not break.

It does not mean that all reflowable EPUB publications get an automatic pass on this success criterion, but only that the circumstances where the content will not reflow are not common.

Container widths

The most likely source of failure for the reflow success criterion is going to arise with container elements, such as with the [[html]] [^aside^], [^div^], [^nav^] and similar elements used to group content. When these elements are assigned fixed widths, their ability to adapt to changes in zoom diminish.

The content of an [[html]] [^aside^] element used as a sidebar, for example, will reflow by default to so that its content fits the available screen space. But if a width, or a minimum width, greater than 320 CSS pixels is assigned, then as the content is zoomed the dimensions of the viewport may become smaller than the width of the aside.

When a user zooms their publication, what typically will happen with EPUB reading systems is that the sidebar will extend outside the boundary of the page/viewport, causing its text to be cut off and become inaccessible.

But even if the sidebar is made scrollable using CSS overflow properties [[css-overflow]], the result still fails this success criterion because the content now requires scrolling on the x axis to reach the hidden overflow text.

Any hoped-for value in assigning fixed widths to container elements in reflowable content is generally going to be offset by the problems it will cause with the reflow success criterion. If a size must be specified (e.g., to ensure that boxes of content always fill the width of the viewport), the more accessible way is to use a unit that adapts to changes in the viewport. Setting a percentage (%) or viewport width (vw) no greater than 100 percent of the viewport size will avoid scroll bars appearing as the content is zoomed.

Font size

When testing this success criterion, be aware that app-based reading systems typically do not allow zooming of reflowable content. They are more likely to support font size increases up to 400% of the default, but increasing the font size is not the same as zooming the content.

The reflow success criterion does not, in fact, specify requirements on the font size as the content is enlarged. The requirement for text to enlarge up to 200% is instead addressed by the [[wcag2]] resize text success criterion.

Large text strings

Large words, hyperlinks, code examples, and other strings of contiguous text with no break points can also pose problems for reflow as the viewport reaches 320 CSS pixels, but the text is not required to stay the same font size as the content is enlarged. The font size could, for example, be reduced using a media query so that it stays at 200% the original size as the viewport nears 320 CSS pixels.

Other strategies to prevent large text strings causing scrolling include using the [[html]] [^wbr^] element to specify word break locations, using the CSS overflow-wrap and word-break properties, or using the Unicode soft hyphen character.

Exempt content

Not all content is required to reflow as it is enlarged. The success criterion makes an exception for content that would lose its meaning if it were reflowed. For reflowable publications, the most common content that requires two-dimensional layout are diagrams, charts, maps and similar images.

Data tables are also exempt due to their grid nature, but the individual cells within them are not. This means that it would not be unreasonable for the user to have to scroll to reach all the columns, but the content with a column must not require scrolling in two dimensions to read.

Content that can be scrolled in two dimensions needs to always be checked that it has been authored so that it can indeed be scrolled this way. Reading systems will often try to compress tables to fit the available space, for example, but when that cannot be done the overflow outside the page boundary will not be accessible. A common practice to avoid this is to wrap the two-dimensional content in a container that allows scrolling (e.g., a table can be placed inside a div that provides it more space for rendering and includes scrollbars to move around the columns and rows). But when using this practice, content that does not depend on two dimensions for comprehension cannot be captured in the scroll. If a table has a caption, for example, only the table can scroll on the x axis to meet the success criterion; the text of the caption cannot require scrolling.

Fixed layouts

Although the reflow success criterion does not pose a lot of problems for reflowable EPUB publications, it is one of the most problematic to meet for fixed-layout EPUB publications as reading systems do not reflow the content of a fixed-layout page as it is zoomed.

This guide does not address the problems with making fixed-layout publication accessible. For more information on this topic, refer to [[[epub-fxl-a11y]]] [[epub-fxl-a11y]].

Page breaks

Inserting page break markers [[epub-a11y]] into an EPUB publication provides users with context about where they are in the text. Assistive technologies [[epub-a11y]] can use this information to announce the current page number the user is on, for example, if the user wants to cite something on the page.

The inclusion of page break markers can also allow users to move quickly forwards and backwards by page without having to access the page list each time.

The inclusion of these markers also simplifies the creation of a page list, as they provide easily referenced destinations for the links.

Page list

The page list [[epub-a11y]] is the primary means of navigating to page break locations as it provides a list of links to each of the static page break locations in the EPUB publication.

Reading systems typically use this list to generate a "go to page" interface in which users can plug in the page number that they wish to move to, but sometimes offer users the ability to access the full list and select the page number to go to.

Without a page list, page navigation becomes extremely difficult as it would rely on navigating the individual page break markers (if they are even present).

Page source

Users need to know the source of the pagination [[epub-a11y]] in an EPUB publication to determine whether it will be useful for their needs. Print publications, for example, produced in both hard and soft cover editions will have different pagination. Different editions of the same book often also have different pagination.

Including a recognizable identifier for the statically paginated source, such as its ISBN or ISSN, ensures that users can determine which version the pagination corresponds to.

Completeness

Although it is possible for users who require a publication in audio form to use text-to-speech playback, the experience is considerably poorer than when pre-recorded narration is provided. Text-to-speech engines have limited built-in vocabularies, causing them to mangle and mispronounce most uncommon words they encounter. As a result users have to have words repeated and spelled out to make sense of the content, slowing down their reading and reducing comprehension.

For this reason, it is important to provide narration for the full text of a publication in addition to the full text. Users can then decide which reading modality they prefer — text, audio, or a mix of the two.

Escapability

When reading visually, users can quickly move through, and escape from, highly structured content such as sidebars, lists, and figures. Visual readers can skim lists and quickly return to the primary narrative once they locate the desired information, for example. The same is true for reading figures and sidebars, as they are visually offset from the primary narrative so easily jumped into and out of.

The same ease of escaping from content is only possible if EPUB publications include structural semantics in the synchronized text/audio format. Users might not be able to escape from lists, sidebars, figures, and other highly structured content, without the structural semantics of those elements being available.

When the synchronized text-audio playback instructions include this information, reading systems can simplify playback for auditory readers to enable a comparable reading experience.

Navigation document

Reading systems typically provide their own interfaces to the navigation aids in the EPUB navigation document. For example, they open the table of contents as a specialized interface on top of the content the user is reading.

To access these interfaces, users typically rely on text-to-speech playback, when available, to hear the entries.

Providing synchronized text-audio playback for the EPUB navigation document provides reading systems the ability to use auditory labels for the links, improving the experience for auditory readers.

Reading order

Every EPUB publication has a default reading order that allows users to progress through the content. The default reading order consists of two parts: the order of references in the spine provides a high-level progression through the EPUB content documents that make up the publication, while the markup within each EPUB content document provides the default progression through the content elements (i.e., as represented in the document object model [[?dom]]).

For many languages, the default reading order also matches the logical reading order — the way that users will naturally follow the narrative. It ensures that readers can follow the primary narrative and that they encounter secondary content where the author intended it to be read. The default reading order also establishes some less obvious relations, like the progress within a table from cell to cell and row to row.

If the sequence of the synchronized text-audio playback does not match this progression, it can cause confusion for readers, whether they are only listening to the audio or trying to also follow visually.

Ordering the playback to match the default reading order is the safest way to ensure that users can follow the text. In some cases, however, strict adherence to this practice can result in a suboptimal reading experience (e.g., playback of a table by column instead of row might make more natural sense in some cases). These publications have a logical reading order that cannot match the default order of the elements of the host format.

The goal of this objective is not to forbid alternate presentations, but to ensure that deviations are only made to better represent the logical reading order of the content.

Skippability

Being able to read the primary narrative of a work without interruption is central to reading comprehension. EPUB publications are typically structured to visually represent secondary information such as page break markers and footnotes outside the main narrative flow (e.g., by using different background colors or placement so readers can filter this information visually out while reading).

Readers who prefer auditory playback, however, cannot skip this information with the same ease in a linear audio-based reading experience. And, without structural semantics, synchronized text-audio playback cannot offer skipping content either.

When the synchronized text-audio playback instructions include structural semantics, however, reading systems can create reading experiences that allow users to decide which secondary content to skip by default.

Introduction

There are fifty-six success criteria that fall at level A or AA in WCAG 2.2 [[wcag2]]. They are organized by whether they improve the perceivability, operability, understanding, or robustness of the content.

This organization matters because success criteria across multiple categories can apply to different content types. The non-text content success criterion, for example, can apply to images, audio, video, and interactive content. It requires that static images and dynamic images drawn on an [[html]] [^canvas^] element have alternative text and/or descriptions. And for audio and video, it requires labels to describe the nature of the content.

At the same time, there are various success criteria that only apply to a single type of content. The time-based media success criteria, for example, only apply to audio and video.

When carrying out an accessibility evaluation, it is important to know the possible applications of each success criterion. This avoids both mistakenly missing critical checks and wasting time on success criteria that cannot apply the content.

It is not possible for a document like this to determine exactly which success criteria can apply to an EPUB publication because so much depends on the nature of the content. But it is possible to help steer evaluators away from success criteria that do not apply.

Many publications do not contain images, audio, video, or scripted content. The filtering table identifies success criteria that can be skipped when they are not present in EPUB publications.

It is possible to determine what types of content are present, or not present, in an EPUB publication by using validation tools and inspecting the package document. With this information, the filtering table can be used to skip any success criteria that do not apply.

Identifying content types

Before attempting to filter the success criteria it is critical to be sure what content an EPUB publication contains. The traditional way to verify this is through the package document manifest [[epub-3]]. Each manifest item has to list its media type in a media-type attribute, so all that is required is a knowledge of which media types define which type of content.

The media types themselves typically aid in understanding the nature of the listed resources, as the start of each usually classifies the type. Image formats, for example, begin with "image/", while audio formats begin with "audio/". EPUB also maintains a list of core media types which also limits the number of formats that are actually used in publications.

Unfortunately, the package document manifest is an imperfect way of assessing the content of an EPUB 3 publication. It only works well for EPUB 2 publications because EPUB 2 lacks the more advanced content options of EPUB 3.

Determining whether there are images in an EPUB publication is a prime example of how the manifest can fail. Scripts can be used to draw images on the [[html]] [^canvas^] element or to create interactive charts or games. These kinds of images will not be listed in the manifest because they are created using native html functionality.

Similarly, data URLs allow raw image data to be embedded directly in html, once again bypassing a manifest entry. A search for URLs that begin with "data:" might not even be sufficient as a script could dynamically insert an image this way.

Scripting is also problematic because it limits the ability of validators to check whether resources are missing from the manifest. If an [[html]] [^audio^] or [^video^] element is dynamically written into an html file, for example, a validator might only report the corresponding audio or video file in the EPUB package as an unused resource in a usage message. Usage messages are not usually emitted by default making the issue easy to miss. Moreover, if the script writes a reference to a remotely hosted resource, the validator will not report anything at all.

Evaluators will always have to be aware of these limitations and be on the lookout for content that is not listed in the manifest.

In an odd twist, although scripting makes the package document manifest less reliable for detecting non-text content, the package document is the best way to detect if scripting is used. When scripting is used in an EPUB content document, no matter what form it takes, it has to be declared in a properties attribute [[epub-3]].

Scripts are not always stored in standalone JavaScript files, so it can be quite difficult to determine if scripting is present without the help of a validator. Scripts embedded using [[html]] [^script^] tags and scripting inlined in the markup using event handler attributes like {{HTMLElement/onclick}} and {{HTMLElement/onkeypress}} are a couple of ways that scripting can be present at the content level. Trying to locate these possibilities manually is prone to mistakes. But so long as the EPUB publication is validated prior to carrying out an accessibility evaluation, detecting scripting will be straightfoward.

Filtering table

The following table provides a list of success criteria that can be skipped if an EPUB publication does not contain the specified type of content.

If an EPUB publication does not contain any of the above content types, and does not use CSS animations, the following Level A and AA success criteria will also not apply:

• non-text content (1.1.1)
• non-text contrast (1.4.11)
• pause, stop, hide (2.2.2)
• three flashes or below threshold (2.3.1)