Thorium Reader Conformance Reports

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.

Non-text Content

Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.

Audio-only and Video-only (Prerecorded)

Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

Captions (Prerecorded)

Captions are provided for all live audio content in synchronized media.

Captions (Live)

Audio description is provided for all prerecorded video content in synchronized media.

Audio Description (Prerecorded)

Sign language interpretation is provided for all prerecorded audio content in synchronized media.

Sign Language (Prerecorded)

Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media.

Extended Audio Description (Prerecorded)

An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media.

Media Alternative (Prerecorded)

An alternative for time-based media that presents equivalent information for live audio-only content is provided.

Audio-only (Live)

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Info and Relationships

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

Meaningful Sequence

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.

Sensory Characteristics

Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.

Orientation

The purpose of each input field collecting information about the user can be programmatically determined when the input field serves a purpose identified in the Input Purposes for user interface components section.

Identify Input Purpose

In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined.

Identify Purpose

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Use of Color

If any audio on a web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.

Audio Control

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for large text (3:1), incidental, or logotypes.

Contrast (Minimum)

Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

Resize text

If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for customizable or essential cases.

Images of Text

The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for large text (4.5:1), incidental, or logotypes.

Contrast (Enhanced)

For prerecorded audio-only content that contains primarily speech in the foreground, is not an audio CAPTCHA or audio logo, and is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: no background, turn off, or 20 dB.

Low or No Background Audio

For the visual presentation of blocks of text, a mechanism is available to achieve the following: foreground and background colors can be selected, width is no more than 80 characters or glyphs, text is not justified, line spacing is at least space-and-a-half within paragraphs, paragraph spacing is at least 1.5 times larger than line spacing, and text can be resized without assistive technology up to 200 percent.

Visual Presentation

Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.

Images of Text (No Exception)

Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for vertical scrolling content at 320 CSS pixels width or horizontal scrolling content at 256 CSS pixels height.

Reflow

The visual presentation of user interface components and graphical objects has a contrast ratio of at least 3:1 against adjacent color(s).

Non-text Contrast

In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting line height to at least 1.5 times the font size, spacing following paragraphs to at least 2 times the font size, letter spacing to at least 0.12 times the font size, and word spacing to at least 0.16 times the font size.

Text Spacing

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: dismissible, hoverable, persistent.

Content on Hover or Focus

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

Keyboard

If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

No Keyboard Trap

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

Keyboard (No Exception)

If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true: turn off, remap, or active only on focus.

Character Key Shortcuts

For each time limit that is set by the content, at least one of the following is true: turn off, adjust, extend, real-time exception, essential exception, or 20 hour exception.

Timing Adjustable

For moving, blinking, scrolling, or auto-updating information, a mechanism for the user to pause, stop, or hide it is available unless the movement is part of an activity where it is essential.

Pause, Stop, Hide

Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.

No Timing

Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.

Interruptions

When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.

Re-authenticating

Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.

Timeouts

Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

Three Flashes or Below Threshold

Web pages do not contain anything that flashes more than three times in any one second period.

Three Flashes

Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or information being conveyed.

Animation from Interactions

A mechanism is available to bypass blocks of content that are repeated on multiple web pages.

Bypass Blocks

Web pages have titles that describe topic or purpose.

Page Titled

If a web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

Focus Order

The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

Link Purpose (In Context)

More than one way is available to locate a web page within a set of web pages except where the web page is the result of, or a step in, a process.

Multiple Ways

Headings and labels describe topic or purpose.

Headings and Labels

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

Focus Visible

Information about the user's location within a set of web pages is available.

Location

A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.

Link Purpose (Link Only)

Section headings are used to organize the content.

Section Headings

When a user interface component receives keyboard focus, the component is not entirely hidden behind author-created content.

Focus Not Obscured (Minimum)

When a user interface component receives keyboard focus, no part of the component is hidden behind author-created content.

Focus Not Obscured (Enhanced)

When the keyboard focus indicator is visible, an area of the focus indicator meets the following: is at least as large as the area of a 2 CSS pixel thick perimeter of the unfocused component or sub-component, and has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states.

Focus Appearance

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

Pointer Gestures

For functionality that can be operated using a single pointer, at least one of the following is true: no down-event, abort or undo, up reversal, or essential.

Pointer Cancellation

For user interface components with labels that include text or images of text, the name contains the text that is presented visually.

Label in Name

Motion Actuation

The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when equivalent, inline, user agent control, or essential.

Target Size (Enhanced)

Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings.

Concurrent Input Mechanisms

All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.

Dragging Movements

The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except when spacing, equivalent, inline, user agent control, or essential.

Target Size (Minimum)

The default human language of each web page can be programmatically determined.

Language of Page

The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

Language of Parts

A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.

Unusual Words

A mechanism for identifying the expanded form or meaning of abbreviations is available.

Abbreviations

When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.

Reading Level

A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.

Pronunciation

When any user interface component receives focus, it does not initiate a change of context.

On Focus

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

On Input

Navigational mechanisms that are repeated on multiple web pages within a set of web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

Consistent Navigation

Components that have the same functionality within a set of web pages are identified consistently.

Consistent Identification

Changes of context are initiated only by user request or a mechanism is available to turn off such changes.

Change on Request

If a web page contains any help mechanisms, and those mechanisms are repeated on multiple web pages within a set of web pages, they occur in the same order relative to other page content, unless a change is initiated by the user.

Consistent Help

If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.

Error Identification

Labels or instructions are provided when content requires user input.

Labels or Instructions

If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.

Error Suggestion

For web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: reversible, checked, or confirmed.

Error Prevention (Legal, Financial, Data)

Context-sensitive help is available.

Help

For web pages that require the user to submit information, at least one of the following is true: reversible, checked, or confirmed.

Error Prevention (All)

Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated, or available for the user to select.

Redundant Entry

A cognitive function test is not required for any step in an authentication process unless that step provides at least one of the following: alternative, mechanism, object recognition, or personal content.

Accessible Authentication

A cognitive function test is not required for any step in an authentication process unless that step provides at least one of the following: alternative or mechanism.

Accessible Authentication (No Exception)

Parsing

For all user interface components, the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

Name, Role, Value

In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

Status Messages

The user can access information from explicitly-defined relationships in content, including image names, control names, table captions, and table cell labels.

Show Related Elements

The user can determine the path of element nodes from the root element to the currently focused or selected element.

Show Element Hierarchy

The user can choose to render any type of recognized alternative content that is present for a content element.

Render Alternative Content

The user can request a placeholder that incorporates recognized text alternative content instead of recognized non-text content, until explicit user request to render the non-text content.

Replace Non-Text Content

Provide highlighting for selection, keyboard focus, enabled elements, visited links Guideline

The user can have selection, search results, active keyboard focus, unvisited links, and visited links uniquely highlighted, overriding any values specified by the author.

Distinguishable Highlighting

The user can set foreground color and background color characteristics of selection highlighting, overriding any values specified by the author.

Highlighting Options

The user can globally set text scale, color, font family, line spacing, and text style (underline, italic, bold).

Basic Text Formatting (Globally)

The user can globally set text scale, color, font family, line spacing, and text style (underline, italic, bold).

Basic Text Formatting (Globally)

The user can globally set text scale, color, font family, line spacing, and text style (underline, italic, bold).

Basic Text Formatting (Globally)

The user can set text characteristics for specific element types including at least headings, input fields, and links (size, color, font, line spacing, style, margins, borders).

Basic Text Formatting (by Element)

The user can print rendered content with user's text configuration settings applied, and can choose to have content printed as rendered on screen or reflowed.

Configured and Reflowed Text Printing

The user can print rendered content with user's text configuration settings applied, and can choose to have content printed as rendered on screen or reflowed.

Configured and Reflowed Text Printing

The user can print rendered content with user's text configuration settings applied, and can choose to have content printed as rendered on screen or reflowed.

Configured and Reflowed Text Printing

Enable Configuration of User Stylesheets Success Criteria

Enable Configuration of User Stylesheets Success Criteria

Enable Configuration of User Stylesheets Success Criteria

Enable Configuration of User Stylesheets PRINCIPLE 2. Ensure that the user interface is operable Note

The user can have the viewport with the input focus be highlighted.

Highlight Viewport

If new top-level viewports are configured to open without explicit user request, the user can specify whether or not they take active keyboard focus.

Allow Top-Level Viewport Focus Control

When a viewport's selection or input focus changes, the viewport's content moves to ensure the new location is at least partially visible.

Move Viewport to Selection and Focus

The point of regard remains visible within the viewport when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed.

Maintain Point of Regard

When highlighting viewports, the user can customize attributes of the viewport highlighting mechanism such as color and width of borders.

Customize Viewport Highlighting

For user agents that implement a history mechanism, the user can return to any state in viewport history including restored point of regard, input focus, and form field entries.

Provide Viewport History

For user agents that implement a history mechanism, the user can return to any state in viewport history including restored point of regard, input focus, and form field entries.

Provide Viewport History

The user can override the play on load of recognized time-based media content.

Time-Based Media Load-Only

All functionality can be operated via keyboard without specific timings for individual keystrokes, except where the function requires input that depends on the path of movement.

Provide Full Keyboard Functionality

If keyboard focus can be moved to a component, focus can be moved away using only a keyboard interface, or users are advised of the exit method.

Avoid Keyboard Traps

The user agent follows keyboard conventions for the operating environment.

Follow Text Keyboard Conventions

The user can move keyboard focus backwards and forwards through all recognized enabled elements in the rendered content.

Sequential Navigation Between Elements

The user can move keyboard focus backwards and forwards through all recognized enabled elements in the rendered content.

Sequential Navigation Between Elements

The user can move keyboard focus directly to any enabled element in the rendered content.

Allow Direct Navigation to Enabled Elements

The user can save and retrieve multiple sets of user agent preference settings.

Allow Multiple Sets of Preference Settings

If the user agent provides mechanisms for changing settings, it allows the user to reverse changes or requires confirmation.

Settings Changes can be Reversed or Confirmed

There is a dedicated section of documentation presenting all features necessary to meet UAAG 2.0 requirements.

Centralized View

The user can prevent focus changes that are not a result of explicit user request.

Avoid Unpredictable Focus

The user agent makes available via platform accessibility services: name, role, state, value, selection, focus, bounding dimensions, font, colors, and keyboard commands.

Expose Accessible Properties

The user agent makes available via platform accessibility services: name, role, state, value, selection, focus, bounding dimensions, font, colors, and keyboard commands.

Expose Accessible Properties

The user agent makes available via platform accessibility services: name, role, state, value, selection, focus, bounding dimensions, font, colors, and keyboard commands.

Expose Accessible Properties

The user agent makes available via platform accessibility services: name, role, state, value, selection, focus, bounding dimensions, font, colors, and keyboard commands.

Expose Accessible Properties

If the user agent contains native interfaces, those native interfaces follow platform accessibility guidelines.

Implement Accessibility Features of the Platform

If the user agent contains native interfaces, those native interfaces follow platform accessibility guidelines.

Implement Accessibility Features of the Platform

If the user agent contains native interfaces, those native interfaces follow platform accessibility guidelines.

Implement Accessibility Features of the Platform

If the user agent contains native interfaces, those native interfaces follow platform accessibility guidelines.

Implement Accessibility Features of the Platform

If the user agent contains native interfaces, those native interfaces follow platform accessibility guidelines.

Implement Accessibility Features of the Platform

EPUB publications MUST include accessModeSufficient metadata indicating one or more access modes sufficient to consume content without significant loss of information.

Discoverability: accessModeSufficient

EPUB publications MUST include accessibilityFeature metadata listing features and adaptations that contribute to accessibility (e.g., alternative text, extended descriptions, captions).

Discoverability: accessibilityFeature

EPUB publications MUST include accessibilityHazard metadata identifying any potential hazards such as flashing, motion simulation, or sound.

Discoverability: accessibilityHazard

EPUB publications SHOULD include accessMode metadata specifying sensory perceptual systems required to process content (textual, visual, auditory, tactile).

Discoverability: accessMode

EPUB publications SHOULD include accessibilitySummary metadata providing human-readable summary of accessibility complementing other metadata.

Discoverability: accessibilitySummary

EPUB publications MUST meet the requirements of WCAG 2.0 Level A at minimum, though WCAG 2.2 Level AA is strongly recommended.

WCAG Conformance: Minimum Level

When EPUB includes page navigation, the source of static page break locations must be identified with recognizable identifier such as ISBN or ISSN.

Page Navigation: Pagination Source

EPUB publications with page navigation MUST include a page list providing navigation to static page break locations.

Page Navigation: Page List

EPUB publications with page navigation SHOULD include page break markers identifying all pages reproduced from the source.

Page Navigation: Page Breaks

EPUB with synchronized text-audio playback MUST include audio playback for all visible textual content and textual alternatives for visual media.

Synchronized Text-Audio: Completeness

Synchronized text-audio playback instructions SHOULD reflect spine order of documents and element order within documents, or result in logical playback.

Synchronized Text-Audio: Reading Order

Synchronized text-audio playback instructions SHOULD identify all skippable structures enabling users to skip secondary content.

Synchronized Text-Audio: Skippability

Synchronized text-audio playback instructions SHOULD identify all escapable structures enabling users to exit from structured content.

Synchronized Text-Audio: Escapability

EPUB with synchronized text-audio playback SHOULD include synchronized playback for the EPUB navigation document.

Synchronized Text-Audio: Navigation Document

EPUB publications MUST specify conformance using dcterms:conformsTo property in format: 'EPUB Accessibility 1.2 - WCAG [VERSION] Level [LEVEL]'.

Conformance Reporting: Publication Conformance

Package document metadata MUST include a11y:certifiedBy property specifying name of party that evaluated the EPUB publication.

Conformance Reporting: Evaluator Name

If evaluation date is known, include dcterms:date property conforming to ISO 8601 format associated with evaluator information.

Conformance Reporting: Evaluation Date

If evaluator has credentials, include a11y:certifierCredential properties associated with evaluator information.

Conformance Reporting: Evaluator Credentials

If evaluator provides public assessment report, provide link using a11y:certifierReport property associated with evaluator information.

Conformance Reporting: Evaluator Report

EPUB publications MAY include accessibility contact email using a11y:contactEmail property for users to report issues.

Accessibility Feedback

User must have straightforward way to navigate forward and backward through content (text or audio-based).

Navigation: Forward and Backward

User must be able to navigate publication using Table of Contents with focus matching current reading position, supporting hierarchical/nested structures.

Navigation: Table of Contents

User must have way to navigate content by page numbers; may include pseudo-pages for publications without page markup.

Navigation: By Pages

User must have way to go to specific location in audio-based content via time, percentage, or other approach.

Navigation: Audio Location

User must be able to return to last reading location when reopening publication; automatic saving required.

Navigation: Return to Last Location

User must be able to determine current position in content; minimum information is percentage progress.

Navigation: Determine Current Location

User must be able to go back to previous location in content.

Navigation: Return to Previous Location

User must be able to use screen reader in user interface; all components must provide semantic labels and roles per WCAG 2.1 and ARIA.

Screen Reader: User Interface

Screen reader users must be able to navigate through content by headings, block items, lines, words and characters.

Screen Reader: Navigation

Screen reader users must be able to read continuously from current position, pause, and resume from paused location.

Screen Reader: Continuous Reading

User must be able to leverage screen reader's ability to interpret semantic markup; headings, lists, tables, images must be exposed.

Screen Reader: Semantic Markup

User must be able to use screen reader in scrolling mode.

Screen Reader: Scrolling Mode

Screen reader users must be able to navigate confidently between internal hyperlinks and read from new navigation position.

Screen Reader: Internal Hyperlinks

Screen reader users must be able to activate actionable content such as links, buttons, expandable elements.

Screen Reader: Actionable Content

Screen reader users must be able to detect footnote references, reach footnote content, read it, and return to original position.

Screen Reader: Footnotes/Endnotes

User could use additional navigation features provided by reading app such as navigation by heading, landmarks, tables, figures, math.

Screen Reader: Additional Navigation

User must be able to listen to text-based content using text-to-speech; seamless transition between embedded audio, TTS, and screen reader.

Read Aloud: Text-to-Speech

User must control starting position of read aloud; starting from screen reader position, indicated position, or reading position.

Read Aloud: Starting Position

User must be able to select text (word, phrase, sentence, paragraph) and have it read aloud.

Read Aloud: Selected Content

User must listen to read aloud without manually advancing; continuous until end or user interruption.

Read Aloud: Continuous Reading

Read aloud must follow logical reading order of content rather than visual layout.

Read Aloud: Logical Reading Order

Read aloud must use appropriate pauses after headings, paragraphs, list items rather than continuous reading.

Read Aloud: Appropriate Pauses

User must see text being read aloud with automatic display updates; text highlighted may move to different part while read aloud continues.

Read Aloud: View Text

User must be able to visually emphasize text being read aloud and turn feature off.

Read Aloud: Visual Emphasis

User must be able to change color or style of visual emphasis; could adjust number of words highlighted.

Read Aloud: Emphasis Customization

User must hear read aloud in correct language when reading content with language tags; could override language switching.

Read Aloud: Language

User must control playback speed of read aloud; speed adjustments maintain natural pitch and pronunciation.

Read Aloud: Playback Speed

User must be able to control voice of read aloud.

Read Aloud: Voice Control

User must be able to listen to image alt text included in read aloud.

Read Aloud: Image Alt Text

User must be able to listen to math content when using read aloud.

Read Aloud: Math Content

User must be able to lock mobile device and use read aloud.

Read Aloud: Locked Device

User must control read-aloud playback using device media controls (play, pause, skip, stop).

Read Aloud: Media Controls

User must use read aloud with tables; must read left to right, top to bottom.

Read Aloud: Tables

User must use read aloud with expandable/collapsible content; expanded content read, collapsed not read.

Read Aloud: Expandable Content

User must escape from certain structures when using read aloud and continue from following item.

Read Aloud: Escape Structures

User must configure app to not announce skippable elements.

Read Aloud: Skip Content

User could choose from range of read aloud modes such as word, sentence, paragraph, page, chapter.

Read Aloud: Reading Modes

User could adjust pause length between content blocks during read aloud.

Read Aloud: Pause Length

User could choose to have semantic expressiveness for read aloud.

Read Aloud: Semantic Expressiveness

User must access and play pre-recorded audio; seamless transition between embedded audio, TTS read aloud, and screen reader.

Embedded Audio: Playback

User must control starting position of embedded audio via time, percentage, or other approach.

Embedded Audio: Starting Position

User must listen to embedded audio without manually advancing; continuous playback with optional sleep timer.

Embedded Audio: Continuous Playback

User must listen to embedded audio in correct logical reading order matching publication structure.

Embedded Audio: Logical Reading Order

User must view corresponding text while listening to embedded audio if synchronized text available.

Embedded Audio: Synchronized Text

User must enable or disable visual emphasis of synchronized text during embedded audio playback.

Embedded Audio: Visual Emphasis Toggle

User must customize color and style of visual emphasis; could adjust number of words highlighted.

Embedded Audio: Emphasis Customization

User must adjust playback speed without distortion; speed adjustments maintain natural pitch and pronunciation.

Embedded Audio: Playback Speed

User must listen to alt texts included in embedded audio and skip if supported.

Embedded Audio: Alt Text

User must listen to math content included in embedded audio if present.

Embedded Audio: Math Content

User must lock mobile device and continue listening to embedded audio.

Embedded Audio: Locked Device

User must control embedded audio playback using device-level media controls.

Embedded Audio: Device Controls

User must listen to embedded audio that conveys structure and content of tables.

Embedded Audio: Table Structure

User must listen to embedded audio reflecting current state of expandable content; only expanded content plays.

Embedded Audio: Expandable Content

User can escape from defined structures during embedded audio playback and resume from following item.

Embedded Audio: Escape Structures

User must configure embedded audio playback to skip content marked as skippable.

Embedded Audio: Skip Content

User could play embedded audio for selected portion of text if content is synchronized.

Embedded Audio: Selected Portion

User could choose different playback modes for embedded audio including non-continuous playback.

Embedded Audio: Playback Modes

User could adjust pause length between content blocks during embedded audio playback.

Embedded Audio: Pause Length

User must change typeface of all text, choosing from sans serif and serif fonts.

Visual: Typeface

User must be able to control line spacing of text.

Visual: Line Spacing

User must be able to control letter spacing.

Visual: Letter Spacing

User must turn off justification and center alignment of blocks of text.

Visual: Text Justification

User must be able to change font size.

Visual: Font Size

User must change margins and adjust line length for blocks of text.

Visual: Margins and Line Length

User must view reflowable content in scrolling view.

Visual: Scrolling View

User must use app with high contrast and magnification features of operating system platform.

Visual: Platform Features

User must adjust size and color of math expressions by adjusting text's font size and color.

Visual: Math Expressions

User must personalize background and foreground colors.

Visual: Background and Foreground Colors

User must change display brightness.

Visual: Brightness

User must visually hide certain content such as page breaks and footnotes.

Visual: Hide Content

User should remove visual text styling (underline, italic, bold).

Visual: Text Styling

User should visually emphasize text being read using highlight, ruler lines, or other means.

Visual: Reading Emphasis

User should enlarge math expressions for closer inspection.

Visual: Math Enlargement

User could change capitalization of text to sentence style.

Visual: Capitalization

User could view content in paginated view.

Visual: Pagination

User could display mathematical expressions without color formatting using consistent text color.

Visual: Math Color

Additional visual adjustment features provided by reading app.

Visual: Additional Features

User must create bookmarks at arbitrary positions within content.

Bookmarking: Create

User must delete bookmarks individually; could delete all bookmarks at once.

Bookmarking: Delete

User must view overview of all bookmarks sorted by appearance order and navigate from there.

Bookmarking: Overview

User must identify each bookmark via meaningful system-generated title; should be editable or taggable.

Bookmarking: Identify

User bookmarks must be saved automatically including during offline use.

Bookmarking: Auto-Save

User must create, review, edit and delete highlights.

Highlighting: Create

User must distinguish highlights.

Highlighting: Distinguish

User should hide highlights.

Highlighting: Hide

User must change color or category of highlights.

Highlighting: Change

User should navigate from highlight to highlight.

Highlighting: Navigate

User highlights must be saved automatically including during offline use.

Highlighting: Auto-Save

User should export highlighted sections.

Highlighting: Export

User must create, review, edit and delete notes during reading.

Notes: Create

User must view notes in context such as margin or overlay maintaining reading position.

Notes: View in Context

User notes must be saved automatically including during offline use.

Notes: Auto-Save

Screen reader users should navigate from one note to another.

Notes: Navigate

User should apply basic formatting to note content (bold, italic, underline).

Notes: Formatting

User should hide or show notes.

Notes: Visibility

User should have notes read aloud individually or in sequence.

Notes: Read Aloud

User should export notes in structured format.

Notes: Export

User could create notes in formats beyond text such as handwriting, math notation, or video.

Notes: Format Variety

User must enter, edit and review answers into input fields embedded within publication.

Answers: Input

User must save answers automatically; ideally online with offline support and syncing.

Answers: Save

User must see previously saved answers when reopening book.

Answers: View Previous

Screen reader users must navigate between input fields.

Answers: Navigate Fields

User should format answers in text fields using basic rich text editor.

Answers: Text Formatting

User should share answers with others by export or within system.

Answers: Share

User could add custom input fields where none exist.

Answers: Custom Fields

User could synchronize answers across multiple devices.

Answers: Synchronize

User could have answers automatically checked.

Answers: Auto-Check

User must have simple accessible way to log in to reading system.

Library: Login

User must search, browse and acquire titles in service provider's collection.

Library: Search and Browse

User must add titles from diverse sources (sideload content).

Library: Add Titles

User must subscribe to and unsubscribe from serial publications.

Library: Serial Subscriptions

User must be able to remove titles from bookshelf.

Library: Remove Titles

User must be able to download titles and read offline.

Library: Download

User must be able manage titles from multiple sources.

Library: Manage Sources

User must manage diverse collection with search, sort, filter, categorization.

Library: Manage Collection

Bookshelf must automatically reflect changes made in synchronized services, syncing across devices.

Library: Synchronized Bookshelf

User should be able to preview publication when available.

Library: Publication Preview

User should be able to open EPUB files directly from file manager.

Library: Open EPUB from File Manager

User must have user-friendly documentation for reading system.

Misc: Documentation

User must receive clear and user-friendly error messages.

Misc: Error Messages

User must access and read protected content using assistive technologies.

Misc: Protected Content

User should get citations or references in accepted formats.

Misc: Citations

A simplified or 'Zen' mode should be available, hiding most interface controls and presenting only essential reading functions. This reduces cognitive load and visual distractions, benefiting users with attention-related or cognitive disabilities.

Less distraction mode / Zen mode / Simplified interface

The application shall allow users to configure reading-related features both globally (via application settings) and locally (per document). Global settings (e.g. font size, contrast, voice speed) ensure consistency, while some features (e.g. layout or reading mode) may need to be overridden per document.

Configurable reading preferences

Some digital publications include hyperlinks to external web resources. Users should be able to follow these links and open them in an external web browser outside the reading system, supporting access to supplementary materials.

Follow external links

Users should be able to view multiple versions of a text side by side, such as an original and a translation, or a text with annotations, supporting comparative reading and study.

Parallel text viewing and navigation for linked content

The app should display the word count for each article or chapter in the table of contents, helping users estimate the length and effort required for each section.

Display word counts in tables of contents

Text style properties such as font, line spacing, indentation, justification, and emphasis (bold, italic, underline) should be made available to assistive technologies, allowing screen readers and braille displays to convey visual structure and emphasis in non-visual ways.

Disclose text style properties to assistive technologies

Users should be able to enable or disable hyphenation. This customization supports a more accessible and comfortable reading experience, especially for users with dyslexia or low vision, by reducing visual clutter and improving text flow.

Turn hyphenation on/off

Text in fixed-layout documents should be able to reflow, allowing for better readability on small screens or when using magnification.

Reflow of text for fixed layout as well

The app could provide region-based navigation which zooms in and steps the reader through a defined reading order. The reader could navigate between regions at their own pace.

Regional navigation features

The app should allow integration of AI-powered features, such as summarization, question answering, or contextual assistance based on the content of the publication.

Support for LLM inference or other processing

Users should be able to print or export selected parts of a publication, such as templates or activity pages. This supports hands-on learning and accessibility for users who benefit from physical or tactile formats.

Print or export specific content

The app must allow users to export content in a digital format suitable for creating alternative accessible formats, such as braille or large print.

Export content for alternative format production

The app should, where feasible, support the rendering of tactile graphics via compatible hardware such as refreshable Braille displays or pin-matrix devices, enabling users with visual impairments to access graphical content.

Support for tactile graphics

The user should be able to enter personal or contextual information—such as the number of servings in a recipe or a name for personalized narration—which then dynamically updates the content. This makes digital publications more engaging and helps reduce cognitive load.

Dynamic content based on user input

The app should provide personalized book recommendations based on the user's reading history, interests, or profile, making it easier to discover relevant content.

Book recommendations based on personal preferences

Users should be able to share book recommendations with others, for example via social media or within the reading platform, to encourage community and engagement.

Book recommendation sharing

The app should indicate which books a user has previously borrowed or read, helping them avoid duplicates and revisit favorites.

Borrowing history indicator

The app should allow users to save and organize excerpts or quotes from digital publications, functioning as a digital scrapbook for easy reference and study.

Digital clippings archive