Conformance Report - Desktop

The application features extensive accessibility interoperability and content customization, It performs well against WCAG 2.2, UAAG 2.0, and DAISY requirements, though some advanced features and interface zoom are still limited.

About This Report

Product Name:
Thorium Reader
Version:
3
Platform:
Desktop (Windows, macOS, Linux)
Evaluation Date:
2025-02-26
Changelog
  • 2025-02-26: Initial conformance report for Thorium Reader Desktop 3
  • 2025-01-15: Evaluation testing phase
  • 2024-12-01: Accessibility audit and code review
More about this evaluation

Evaluation Methodology

The evaluation included the following testing approaches:

Tested Scenarios

Standards & References

Web Content Accessibility Guidelines (WCAG)
Version: 2.2 - Reference: https://www.w3.org/WAI/WCAG22/
User Agent Accessibility Guidelines (UAAG)
Version: 2.0 - Reference: https://www.w3.org/TR/UAAG20/
DAISY Reading Apps User Requirements (DAISY URS)
Version: 1.0 - Reference: https://daisy.org/s/readingURS/FINAL-20251031

Detailed Reports

WCAG Conformance Results

Thorium Reader Desktop provides comprehensive access to assistive technologies and offers a variety of customisation options for content display and interface behaviour. In many cases, it meets the Level AAA criteria. However, there are certain limitations: the lack of a zoom function for the interface can detract from the reading experience, and some specialised features have not yet been tested.

WCAG Conformance Details
WCAG conformance results (column headers with buttons are sortable).
1.1.1 Non-text Content

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

Non-text Content

A

passed

all visual information is also available as text
1.2.1 Audio-only and Video-only (Prerecorded)

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)

A

passed

Thorium Reader can restitue publications with pre-recorded audio or video.
1.2.2 Captions (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)

A

passed

Thorium Reader can restitue publications with pre-recorded captions.
1.2.4 Captions (Live)

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

Captions (Live)

AA

inapplicable

Live captions may be available depending on the video-service provided by the ebook creator.
1.2.5 Audio Description (Prerecorded)

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

Audio Description (Prerecorded)

AA

passed

Thorium Reader can restitue publications with pre-recorded Audio descriptions.
1.2.6 Sign Language (Prerecorded)

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

Sign Language (Prerecorded)

AAA

passed

Thorium Reader can restitue publications with pre-recorded Sign language videos. An experimental feature allows the reading of authored-synchronisation between text and video.
1.2.7 Extended Audio Description (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)

AAA

passed

Thorium Reader can restitue publications with pre-recorded extended audio descriptions.
1.2.8 Media Alternative (Prerecorded)

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

Media Alternative (Prerecorded)

AAA

passed

Thorium Reader can restitue publications with pre-recorded media alternative.
1.2.9 Audio-only (Live)

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

Audio-only (Live)

AAA

passed

Thorium Reader can restitue publications with live-audio only, depending of the streaming application chosen and implemented by the ebook-creator.
1.3.1 Info and Relationships

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

Info and Relationships

A

passed

Thorium Reader makes use of HTML markup with additional ARIA roles when necessary. It also fully restitues all XHTML and ARIA markup as authored in publications.
1.3.2 Meaningful Sequence

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

Meaningful Sequence

A

passed

1.3.3 Sensory Characteristics

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

A

passed

1.3.4 Orientation

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

AA

passed

1.3.5 Identify Input Purpose

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

AA

passed

1.3.6 Identify Purpose

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

Identify Purpose

AAA

passed

1.4.1 Use of Color

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

A

passed

1.4.2 Audio Control

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

A

passed

1.4.3 Contrast (Minimum)

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)

AA

passed

1.4.4 Resize text

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

AA

failed

The text from the interface cannot be resized.

Make the interface scalable #3293

1.4.5 Images of 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

AA

passed

1.4.6 Contrast (Enhanced)

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)

AAA

passed

1.4.7 Low or No Background Audio

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

AAA

passed

1.4.8 Visual Presentation

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

AAA

passed

1.4.9 Images of Text (No Exception)

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)

AAA

passed

1.4.10 Reflow

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

AA

failed

The text from the interface cannot be resized.

Make the interface scalable #3293

1.4.11 Non-text Contrast

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

AA

passed

1.4.12 Text Spacing

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

AA

passed

1.4.13 Content on Hover or Focus

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

AA

passed

2.1.1 Keyboard

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

A

passed

2.1.2 No Keyboard Trap

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

A

passed

2.1.3 Keyboard (No Exception)

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

Keyboard (No Exception)

AAA

passed

2.1.4 Character Key Shortcuts

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

A

passed

2.2.1 Timing Adjustable

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

A

passed

2.2.2 Pause, Stop, Hide

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

A

passed

2.2.3 No Timing

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

AAA

passed

2.2.4 Interruptions

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

Interruptions

AAA

passed

2.2.5 Re-authenticating

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

Re-authenticating

AAA

inapplicable

2.2.6 Timeouts

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

AAA

inapplicable

2.3.1 Three Flashes or Below Threshold

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

A

passed

2.3.2 Three Flashes

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

Three Flashes

AAA

passed

2.3.3 Animation from Interactions

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

Animation from Interactions

AAA

passed

2.4.1 Bypass Blocks

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

Bypass Blocks

A

passed

2.4.2 Page Titled

Web pages have titles that describe topic or purpose.

Page Titled

A

passed

2.4.3 Focus Order

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

A

passed

2.4.4 Link Purpose (In Context)

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)

A

passed

2.4.5 Multiple Ways

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

AA

passed

2.4.6 Headings and Labels

Headings and labels describe topic or purpose.

Headings and Labels

AA

passed

2.4.7 Focus Visible

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

Focus Visible

A

passed

2.4.8 Location

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

Location

AAA

passed

2.4.9 Link Purpose (Link Only)

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)

AAA

passed

2.4.10 Section Headings

Section headings are used to organize the content.

Section Headings

AAA

passed

2.4.11 Focus Not Obscured (Minimum)

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

Focus Not Obscured (Minimum)

AA

passed

2.4.12 Focus Not Obscured (Enhanced)

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

Focus Not Obscured (Enhanced)

AAA

passed

2.4.13 Focus Appearance

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

AAA

passed

2.5.1 Pointer Gestures

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

A

passed

2.5.2 Pointer Cancellation

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

A

passed

2.5.3 Label in Name

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

A

passed

2.5.4 Motion Actuation

Motion Actuation

A

passed

2.5.5 Target Size (Enhanced)

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)

AAA

passed

2.5.6 Concurrent Input Mechanisms

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

AAA

passed

2.5.7 Dragging Movements

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

AA

passed

2.5.8 Target Size (Minimum)

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)

AA

passed

3.1.1 Language of Page

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

Language of Page

A

passed

3.1.2 Language of Parts

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

AA

passed

3.1.3 Unusual Words

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

AAA

failed

There is an ongoing discussion about Dictionary Integration in Thorium Reader

Dictionary Integration #1751

3.1.4 Abbreviations

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

Abbreviations

AAA

passed

If the abbr tag is present in a puiblication, it will be rendered as a tooltip and made available to assistive technologies.
3.1.5 Reading Level

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

AAA

inapplicable

3.1.6 Pronunciation

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

Pronunciation

AAA

inapplicable

3.2.1 On Focus

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

On Focus

A

passed

3.2.2 On Input

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

A

passed

3.2.3 Consistent Navigation

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

AA

passed

3.2.4 Consistent Identification

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

Consistent Identification

AA

passed

3.2.5 Change on Request

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

Change on Request

AAA

passed

3.2.6 Consistent Help

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

A

passed

3.3.1 Error Identification

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

A

passed

3.3.2 Labels or Instructions

Labels or instructions are provided when content requires user input.

Labels or Instructions

A

passed

3.3.3 Error Suggestion

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

AA

passed

3.3.4 Error Prevention (Legal, Financial, Data)

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)

AA

inapplicable

3.3.5 Help

Context-sensitive help is available.

Help

AAA

inapplicable

3.3.6 Error Prevention (All)

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)

AAA

passed

3.3.7 Redundant Entry

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

passed

3.3.8 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, mechanism, object recognition, or personal content.

Accessible Authentication

AA

inapplicable

3.3.9 Accessible Authentication (No Exception)

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)

AAA

inapplicable

4.1.1 Parsing

Parsing

A

inapplicable

4.1.2 Name, Role, Value

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

A

passed

4.1.3 Status Messages

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

AA

passed

UAAG Conformance Results

Thorium Reader Desktop shows high conformance to UAAG 2.0, with strong support for keyboard operation, user preference controls, accessible documentation, and integration with platform accessibility services. Most criteria are passed across levels A to AAA; remaining non-conformances are concentrated in a limited set of user-adjustment features, notably configurable defaults for some alternative content behaviors and full interface-level scaling/zoom consistency.

UAAG Conformance Details
UAAG conformance results (column headers with buttons are sortable).
1.1.1 Render Alternative Content

Render Alternative Content

A

passed

1.1.2 Indicate Unrendered Alternative Content

Indicate Unrendered Alternative Content

A

failed

  • Abbr are indicated by a dotted underline.
  • alt text are not indicated. See Issue 3139: Allow users to display alt texts.
  • The video player indicates the presence of subtitles if they are available. Embed players are the responsibility of the ebook content creator.
1.1.3 Replace Non-Text Content

Replace Non-Text Content

A

passed

Caption Clean view is available for TTS reading. It should be extended to visual reading (see Issue #3141 Extend Caption / Clean View to visual reading (UAAG1.1.3 Replace Non-Text Content))
1.1.4 Facilitate Clear Display of Alternative Content for Time-based Media

Facilitate Clear Display of Alternative Content for Time-based Media

A

passed

The video player indicates the presence of subtitles if they are available. Embed players are the responsibility of the ebook content creator.
1.1.5 Provide Configurable Alternative Content Defaults

Provide Configurable Alternative Content Defaults

AA

failed

1.1.6 Use Configurable Text for Time-based Media Captions

Use Configurable Text for Time-based Media Captions

AA

passed

1.1.7 Allow Resize and Reposition of Time-based Media Alternatives

Allow Resize and Reposition of Time-based Media Alternatives

AAA

passed

1.2.1 Support Repair by Assistive Technologies

Support Repair by Assistive Technologies

AA

passed

1.3.1 Distinguishable Highlighting

Distinguishable Highlighting

A

passed

1.3.2 Highlighting Options

Highlighting Options

AA

passed

1.3.3 Highlighting Active Keyboard Focus

Highlighting Active Keyboard Focus

AA

passed

1.3.4 Distinguishing Enabled Elements

Distinguishing Enabled Elements

AA

passed

1.3.5 Distinguishing Enabled Elements

Distinguishing Enabled Elements

AA

passed

1.4.1 Basic text formatting (Globally)

Basic text formatting (Globally)

A

passed

1.4.2 Basic text formatting (by Element)

Basic text formatting (by Element)

AA

passed

1.4.3 Blocks of text (Globally)

Blocks of text (Globally)

AA

passed

1.4.4 Configured and Reflowed Text Printing

Configured and Reflowed Text Printing

AA

passed

1.4.5 Default to platform text settings

Default to platform text settings

AA

passed

1.4.6 Advanced text formatting

Advanced text formatting

AAA

passed

1.5.1 Global Volume

Global Volume

A

passed

1.6.1 Speech Rate, Volume, and Voice

Speech Rate, Volume, and Voice

AA

passed

1.6.2 Speech Pitch and Range

Speech Pitch and Range

AA

passed

1.6.3 Synthesized Speech Features

Synthesized Speech Features

AA

passed

1.6.4 Synthesized Speech Language

Synthesized Speech Language

AA

passed

1.6.5 Advanced Speech Characteristics

Advanced Speech Characteristics

AAA

passed

1.7.1 Disable Author Stylesheets

Disable Author Stylesheets

A

passed

1.7.2 Support User Stylesheet or User Style Modification Mechanism

Support User Stylesheet or User Style Modification Mechanism

A

passed

1.7.3 Apply User Stylesheets

Apply User Stylesheets

A

passed

1.7.4 Save Copies of Stylesheets

Save Copies of Stylesheets

AA

passed

1.8.1 Highlight Viewport

Highlight Viewport

A

passed

1.8.2 Move Viewport to Selection and Focus

Move Viewport to Selection and Focus

A

passed

1.8.3 Provide Viewport Scrollbars

Provide Viewport Scrollbars

A

passed

1.8.4 Indicate Viewport Position

Indicate Viewport Position

A

passed

1.8.5 Allow Zoom

Allow Zoom

A

failed

Additional Info: Reflowable contents can be adjusted in size and fixed layout contents can be zoomed. However the text from the interface cannot be resized. This is tracked in Issue Make the interface scalable
1.8.6 Maintain Point of Regard

Maintain Point of Regard

A

passed

1.8.7 Customize Viewport Highlighting

Customize Viewport Highlighting

AA

passed

1.8.8 Allow Viewport Resize

Allow Viewport Resize

AA

passed

1.8.9 Provide Viewport History

Provide Viewport History

AA

passed

1.8.10 Allow Top-Level Viewport Open on Request

Allow Top-Level Viewport Open on Request

AA

passed

1.8.11 Allow Top-Level Viewport Focus Control

Allow Top-Level Viewport Focus Control

AA

passed

1.8.12 Allow Same User Interface

Allow Same User Interface

AA

passed

1.8.13 Multi-Column Text Reflow

Multi-Column Text Reflow

AA

passed

1.8.14 Ignore Fixed Unit Dimensions

Ignore Fixed Unit Dimensions

AA

passed

1.8.15 Linearize Content

Linearize Content

AA

passed

1.8.16 Provide Web Page Bookmarks

Provide Web Page Bookmarks

AAA

passed

1.9.1 Outline View

Outline View

AA

passed

1.9.2 Source View

Source View

AAA

failed

Source view is available only with development versions, without LCP protection support.
1.10.1 Show Related Elements

Show Related Elements

AA

passed

1.10.2 Show Element Hierarchy

Show Element Hierarchy

AAA

passed

2.1.1 Provide Full Keyboard Functionality

Provide Full Keyboard Functionality

A

passed

2.1.2 Has Keyboard Focus

Has Keyboard Focus

A

passed

2.1.3 Avoid Keyboard Traps

Avoid Keyboard Traps

A

passed

2.1.4 Separate Selection from Activation

Separate Selection from Activation

A

passed

2.1.5 Follow Text Keyboard Conventions

Follow Text Keyboard Conventions

A

passed

2.1.6 Make Keyboard Access Efficient

Make Keyboard Access Efficient

A

passed

2.2.1 Sequential Navigation Between Elements

Sequential Navigation Between Elements

A

passed

2.2.2 Sequential Navigation Between Landmarks

Sequential Navigation Between Landmarks

A

passed

2.2.3 Default Navigation Order

Default Navigation Order

AA

passed

2.2.4 Options for Wrapping in Navigation

Options for Wrapping in Navigation

AA

passed

2.3.1 Allow Direct Navigation to Enabled Elements

Allow Direct Navigation to Enabled Elements

AA

passed

2.3.2 Allow Direct Activation of Enabled Elements

Allow Direct Activation of Enabled Elements

AA

passed

2.3.3 Present Direct Commands from Rendered Content

Present Direct Commands from Rendered Content

AA

passed

2.3.4 Present Direct Commands in User Interface

Present Direct Commands in User Interface

AA

passed

2.3.5 Allow Customized Keyboard Commands

Allow Customized Keyboard Commands

AA

passed

2.4.1 Text Search

Text Search

A

passed

2.4.2 Search Direction

Search Direction

A

passed

2.4.3 Match Found

Match Found

A

passed

2.4.4 Alert on Wrap or No Match

Alert on Wrap or No Match

A

passed

2.4.5 Alternative Content Search

Alternative Content Search

AA

passed

2.5.1 Provide Structural Navigation by Heading and within Tables

Provide Structural Navigation by Heading and within Tables

AA

passed

2.6.1 Allow Persistent Accessibility Settings

Allow Persistent Accessibility Settings

A

passed

2.6.2 Allow Restore All to Default

Allow Restore All to Default

A

passed

2.6.3 Allow Multiple Sets of Preference Settings

Allow Multiple Sets of Preference Settings

AA

passed

2.6.4 Allow Preference Changes from outside the User Interface

Allow Preference Changes from outside the User Interface

AAA

passed

2.6.5 Make Preference Settings Transferable

Make Preference Settings Transferable

AAA

passed

2.7.1 Customize Display of Controls for User Interface Commands, Functions, and Add-ons

Customize Display of Controls for User Interface Commands, Functions, and Add-ons

AA

passed

2.8.1 Adjustable Time Limits

Adjustable Time Limits

A

passed

2.9.1 Three Flashes or Below Threshold

Three Flashes or Below Threshold

A

passed

2.9.2 Three Flashes

Three Flashes

AAA

passed

2.10.1 Time-Based Media Load-Only

Time-Based Media Load-Only

A

passed

2.10.2 Execution Placeholder

Execution Placeholder

A

passed

2.10.3 Execution Toggle

Execution Toggle

A

passed

2.10.4 Adjustable Playback Rate for Prerecorded Content

Adjustable Playback Rate for Prerecorded Content

AA

passed

2.10.5 Stop/Pause/Resume Time-Based Media

Stop/Pause/Resume Time-Based Media

A

passed

2.10.6 Navigation of Time-Based Media by Time

Navigation of Time-Based Media by Time

A

passed

2.10.7 Navigation of Time-Based Media by Semantics

Navigation of Time-Based Media by Semantics

AA

passed

2.10.8 Video Contrast and Brightness

Video Contrast and Brightness

AAA

passed

2.11.1 Text Input With Any Device

Text Input With Any Device

AA

passed

3.1.1 Text Entry Undo

Text Entry Undo

A

passed

3.1.2 Settings Changes can be Reversed or Confirmed

Settings Changes can be Reversed or Confirmed

A

passed

3.1.3 Retrieval Progress

Retrieval Progress

A

passed

3.1.4 Spell Check

Spell Check

AA

passed

3.1.5 Back Button

Back Button

AA

passed

3.1.6 Form Submission Confirm

Form Submission Confirm

AA

passed

3.1.7 Form Auto-Fill

Form Auto-Fill

AA

passed

3.1.8 Save Form Entries

Save Form Entries

AA

passed

3.2.1 Accessible Documentation

Accessible Documentation

A

passed

3.2.2 Describe Accessibility Features

Describe Accessibility Features

A

passed

3.2.3 Document All Features

Document All Features

AA

passed

3.2.4 Changes Between Versions

Changes Between Versions

AA

passed

3.2.5 Centralized View

Centralized View

AAA

passed

3.3.1 Avoid Unpredictable Focus

Avoid Unpredictable Focus

A

passed

4.1.1 Support Platform Accessibility Services

Support Platform Accessibility Services

A

passed

4.1.2 Expose Accessible Properties

Expose Accessible Properties

A

passed

4.1.3 Provide Equivalent Accessible Alternatives

Provide Equivalent Accessible Alternatives

A

passed

4.1.4 DOMs Programmatically Available as fallback

DOMs Programmatically Available as fallback

A

passed

4.1.5 Make Content Interaction Programmatically Available

Make Content Interaction Programmatically Available

A

passed

5.1.1 Comply with WCAG

Comply with WCAG

AA

passed

5.1.2 Implement Accessibility Features of Web Content Technology Specifications

Implement Accessibility Features of Web Content Technology Specifications

A

passed

5.1.3 Implement Accessibility Features of the Platform

Implement Accessibility Features of the Platform

A

passed

5.1.4 Allow Content Elements to be Rendered in Alternative Viewers

Allow Content Elements to be Rendered in Alternative Viewers

AA

passed

5.1.5 Enable Reporting of User Agent Accessibility Faults

Enable Reporting of User Agent Accessibility Faults

AAA

passed

DAISYURS Conformance Results

Thorium Reader Desktop demonstrates strong overall alignment with the DAISY Reading Apps User Requirements, with broad support across core navigation, read-aloud, screen reader interoperability, annotation, and library workflows. Most must-have requirements are passed, while remaining gaps are concentrated in selected advanced or potentially valuable capabilities such as citation support, fixed-layout reflow, tactile graphics support, and some export or recommendation features.

DAISYURS Conformance Details
DAISYURS conformance results (column headers with buttons are sortable).
3.1 Navigation: Forward and Backward

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

Navigation: Forward and Backward

must-have

passed

3.2 Navigation: Table of Contents

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

must-have

passed

3.3 Navigation: By Pages

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

Navigation: By Pages

must-have

passed

3.4 Navigation: Audio Location

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

Navigation: Audio Location

must-have

passed

3.5 Navigation: Return to Last Location

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

Navigation: Return to Last Location

must-have

passed

3.6 Navigation: Determine Current Location

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

Navigation: Determine Current Location

must-have

passed

3.7 Navigation: Return to Previous Location

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

Navigation: Return to Previous Location

must-have

passed

4.1 Screen Reader: User Interface

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

must-have

passed

4.2 Screen Reader: Navigation

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

Screen Reader: Navigation

must-have

passed

4.3 Screen Reader: Continuous Reading

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

Screen Reader: Continuous Reading

must-have

passed

4.4 Screen Reader: Semantic Markup

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

must-have

passed

4.5 Screen Reader: Scrolling Mode

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

Screen Reader: Scrolling Mode

must-have

passed

4.6 Screen Reader: Internal Hyperlinks

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

Screen Reader: Internal Hyperlinks

must-have

passed

4.7 Screen Reader: Actionable Content

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

Screen Reader: Actionable Content

must-have

passed

4.8 Screen Reader: Footnotes/Endnotes

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

Screen Reader: Footnotes/Endnotes

must-have

passed

4.9 Screen Reader: Additional Navigation

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

Screen Reader: Additional Navigation

could-have

passed

5.1 Read Aloud: Text-to-Speech

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

must-have

passed

5.2 Read Aloud: Starting Position

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

Read Aloud: Starting Position

must-have

passed

5.3 Read Aloud: Selected Content

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

Read Aloud: Selected Content

must-have

passed

5.4 Read Aloud: Continuous Reading

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

Read Aloud: Continuous Reading

must-have

passed

5.5 Read Aloud: Logical Reading Order

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

Read Aloud: Logical Reading Order

must-have

passed

5.6 Read Aloud: Appropriate Pauses

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

Read Aloud: Appropriate Pauses

must-have

passed

5.7 Read Aloud: View Text

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

must-have

passed

5.8 Read Aloud: Visual Emphasis

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

Read Aloud: Visual Emphasis

must-have

passed

5.9 Read Aloud: Emphasis Customization

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

Read Aloud: Emphasis Customization

must-have

passed

5.10 Read Aloud: Language

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

Read Aloud: Language

must-have

passed

5.11 Read Aloud: Playback Speed

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

Read Aloud: Playback Speed

must-have

passed

5.12 Read Aloud: Voice Control

User must be able to control voice of read aloud.

Read Aloud: Voice Control

must-have

passed

5.13 Read Aloud: Image Alt Text

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

Read Aloud: Image Alt Text

must-have

passed

5.14 Read Aloud: Math Content

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

Read Aloud: Math Content

must-have

passed

5.15 Read Aloud: Locked Device

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

Read Aloud: Locked Device

must-have

passed

5.16 Read Aloud: Media Controls

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

Read Aloud: Media Controls

must-have

passed

5.17 Read Aloud: Tables

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

Read Aloud: Tables

must-have

passed

5.18 Read Aloud: Expandable Content

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

Read Aloud: Expandable Content

must-have

passed

5.19 Read Aloud: Escape Structures

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

Read Aloud: Escape Structures

must-have

passed

5.20 Read Aloud: Skip Content

User must configure app to not announce skippable elements.

Read Aloud: Skip Content

must-have

passed

5.21 Read Aloud: Reading Modes

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

Read Aloud: Reading Modes

could-have

passed

5.22 Read Aloud: Pause Length

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

Read Aloud: Pause Length

could-have

passed

5.23 Read Aloud: Semantic Expressiveness

User could choose to have semantic expressiveness for read aloud.

Read Aloud: Semantic Expressiveness

could-have

passed

6.1 Embedded Audio: Playback

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

Embedded Audio: Playback

must-have

passed

6.2 Embedded Audio: Starting Position

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

Embedded Audio: Starting Position

must-have

passed

6.3 Embedded Audio: Continuous Playback

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

Embedded Audio: Continuous Playback

must-have

passed

6.4 Embedded Audio: Logical Reading Order

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

Embedded Audio: Logical Reading Order

must-have

passed

6.5 Embedded Audio: Synchronized Text

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

Embedded Audio: Synchronized Text

must-have

passed

6.6 Embedded Audio: Visual Emphasis Toggle

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

Embedded Audio: Visual Emphasis Toggle

must-have

passed

6.7 Embedded Audio: Emphasis Customization

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

Embedded Audio: Emphasis Customization

must-have

passed

6.8 Embedded Audio: Playback Speed

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

Embedded Audio: Playback Speed

must-have

passed

6.9 Embedded Audio: Alt Text

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

Embedded Audio: Alt Text

must-have

passed

6.10 Embedded Audio: Math Content

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

Embedded Audio: Math Content

must-have

passed

6.11 Embedded Audio: Locked Device

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

Embedded Audio: Locked Device

must-have

passed

6.12 Embedded Audio: Device Controls

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

Embedded Audio: Device Controls

must-have

passed

6.13 Embedded Audio: Table Structure

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

Embedded Audio: Table Structure

must-have

passed

6.14 Embedded Audio: Expandable Content

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

Embedded Audio: Expandable Content

must-have

passed

6.15 Embedded Audio: Escape Structures

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

Embedded Audio: Escape Structures

must-have

passed

6.16 Embedded Audio: Skip Content

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

Embedded Audio: Skip Content

must-have

passed

6.17 Embedded Audio: Selected Portion

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

Embedded Audio: Selected Portion

could-have

passed

6.18 Embedded Audio: Playback Modes

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

Embedded Audio: Playback Modes

could-have

passed

6.19 Embedded Audio: Pause Length

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

Embedded Audio: Pause Length

could-have

passed

7.1 Visual: Typeface

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

Visual: Typeface

must-have

passed

7.2 Visual: Line Spacing

User must be able to control line spacing of text.

Visual: Line Spacing

must-have

passed

7.3 Visual: Letter Spacing

User must be able to control letter spacing.

Visual: Letter Spacing

must-have

passed

7.4 Visual: Text Justification

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

Visual: Text Justification

must-have

passed

7.5 Visual: Font Size

User must be able to change font size.

Visual: Font Size

must-have

passed

7.6 Visual: Margins and Line Length

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

Visual: Margins and Line Length

must-have

passed

7.7 Visual: Scrolling View

User must view reflowable content in scrolling view.

Visual: Scrolling View

must-have

passed

7.8 Visual: Platform Features

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

Visual: Platform Features

must-have

passed

7.9 Visual: Math Expressions

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

Visual: Math Expressions

must-have

passed

7.10 Visual: Background and Foreground Colors

User must personalize background and foreground colors.

Visual: Background and Foreground Colors

must-have

passed

7.11 Visual: Brightness

User must change display brightness.

Visual: Brightness

must-have

passed

7.12 Visual: Hide Content

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

Visual: Hide Content

must-have

passed

7.13 Visual: Text Styling

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

Visual: Text Styling

must-have

passed

7.14 Visual: Reading Emphasis

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

Visual: Reading Emphasis

should-have

passed

7.15 Visual: Math Enlargement

User should enlarge math expressions for closer inspection.

Visual: Math Enlargement

should-have

passed

7.16 Visual: Capitalization

User could change capitalization of text to sentence style.

Visual: Capitalization

should-have

passed

7.17 Visual: Pagination

User could view content in paginated view.

Visual: Pagination

could-have

passed

7.18 Visual: Math Color

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

Visual: Math Color

could-have

passed

7.19 Visual: Additional Features

Additional visual adjustment features provided by reading app.

Visual: Additional Features

could-have

passed

8.1 Bookmarking: Create

User must create bookmarks at arbitrary positions within content.

Bookmarking: Create

must-have

passed

8.2 Bookmarking: Delete

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

Bookmarking: Delete

must-have

passed

8.3 Bookmarking: Overview

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

Bookmarking: Overview

must-have

passed

8.4 Bookmarking: Identify

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

Bookmarking: Identify

must-have

passed

8.5 Bookmarking: Auto-Save

User bookmarks must be saved automatically including during offline use.

Bookmarking: Auto-Save

must-have

passed

9.1 Highlighting: Create

User must create, review, edit and delete highlights.

Highlighting: Create

must-have

passed

9.2 Highlighting: Distinguish

User must distinguish highlights.

Highlighting: Distinguish

must-have

passed

9.3 Highlighting: Hide

User should hide highlights.

Highlighting: Hide

must-have

passed

9.4 Highlighting: Change

User must change color or category of highlights.

Highlighting: Change

must-have

passed

9.5 Highlighting: Navigate

User should navigate from highlight to highlight.

Highlighting: Navigate

should-have

passed

9.6 Highlighting: Auto-Save

User highlights must be saved automatically including during offline use.

Highlighting: Auto-Save

must-have

passed

9.7 Highlighting: Export

User should export highlighted sections.

Highlighting: Export

should-have

passed

10.1 Notes: Create

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

Notes: Create

must-have

passed

10.2 Notes: View in Context

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

Notes: View in Context

must-have

passed

10.3 Notes: Auto-Save

User notes must be saved automatically including during offline use.

Notes: Auto-Save

must-have

passed

10.4 Notes: Navigate

Screen reader users should navigate from one note to another.

Notes: Navigate

should-have

passed

10.5 Notes: Formatting

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

Notes: Formatting

should-have

passed

10.6 Notes: Visibility

User should hide or show notes.

Notes: Visibility

should-have

passed

10.7 Notes: Read Aloud

User should have notes read aloud individually or in sequence.

Notes: Read Aloud

should-have

passed

10.8 Notes: Export

User should export notes in structured format.

Notes: Export

should-have

passed

10.9 Notes: Format Variety

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

Notes: Format Variety

could-have

passed

11.1 Answers: Input

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

Answers: Input

must-have

passed

11.2 Answers: Save

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

Answers: Save

must-have

passed

11.3 Answers: View Previous

User must see previously saved answers when reopening book.

Answers: View Previous

must-have

passed

11.4 Answers: Navigate Fields

Screen reader users must navigate between input fields.

Answers: Navigate Fields

must-have

passed

11.5 Answers: Text Formatting

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

Answers: Text Formatting

should-have

passed

11.6 Answers: Share

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

Answers: Share

should-have

passed

11.7 Answers: Custom Fields

User could add custom input fields where none exist.

Answers: Custom Fields

could-have

passed

11.8 Answers: Synchronize

User could synchronize answers across multiple devices.

Answers: Synchronize

could-have

passed

11.9 Answers: Auto-Check

User could have answers automatically checked.

Answers: Auto-Check

could-have

passed

12.1 Library: Login

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

Library: Login

must-have

passed

this remains dependant of the feed provider
12.2 Library: Search and Browse

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

Library: Search and Browse

must-have

passed

this remains dependant of the feed provider
12.3 Library: Add Titles

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

Library: Add Titles

must-have

passed

this remains dependant of the feed provider
12.4 Library: Serial Subscriptions

User must subscribe to and unsubscribe from serial publications.

Library: Serial Subscriptions

must-have

passed

this remains dependant of the feed provider
12.5 Library: Remove Titles

User must be able to remove titles from bookshelf.

Library: Remove Titles

must-have

passed

this remains dependant of the feed provider
12.6 Library: Download

User must be able to download titles and read offline.

Library: Download

must-have

passed

this remains dependant of the feed provider
12.7 Library: Manage Sources

User must be able manage titles from multiple sources.

Library: Manage Sources

must-have

passed

this remains dependant of the feed provider
12.8 Library: Manage Collection

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

Library: Manage Collection

must-have

passed

this remains dependant of the feed provider
12.9 Library: Synchronized Bookshelf

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

Library: Synchronized Bookshelf

must-have

passed

this remains dependant of the feed provider
12.10 Library: Publication Preview

User should be able to preview publication when available.

Library: Publication Preview

should-have

passed

this remains dependant of the feed provider
12.11 Library: Open EPUB from File Manager

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

Library: Open EPUB from File Manager

should-have

passed

this remains dependant of the feed provider
13.1 Misc: Documentation

User must have user-friendly documentation for reading system.

Misc: Documentation

must-have

passed

13.2 Misc: Error Messages

User must receive clear and user-friendly error messages.

Misc: Error Messages

should-have

passed

13.3 Misc: Protected Content

User must access and read protected content using assistive technologies.

Misc: Protected Content

must-have

passed

13.4 Misc: Citations

User should get citations or references in accepted formats.

Misc: Citations

should-have

failed

14.1 Less distraction mode / Zen mode / Simplified interface

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

potentially valuable

passed

14.2 Configurable reading preferences

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

potentially valuable

passed

14.3 Follow external links

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

potentially valuable

passed

14.4 Parallel text viewing and navigation for linked content

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

potentially valuable

Untested

No test file
14.5 Display word counts in tables of contents

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

potentially valuable

failed

14.6 Disclose text style properties to assistive technologies

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

potentially valuable

passed

14.7 Turn hyphenation on/off

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

potentially valuable

cantTell

Hyphenation is turned off when text is not justified
14.8 Reflow of text for fixed layout as well

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

potentially valuable

failed

14.9 Regional navigation features

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

potentially valuable

Untested

No test file
14.10 Support for LLM inference or other processing

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

potentially valuable

failed

This would be subject to respect of copyrighted content by third party AI providers.
14.11 Print or export specific content

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

potentially valuable

passed

PDF only
14.12 Export content for alternative format production

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

potentially valuable

failed

14.13 Support for tactile graphics

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

potentially valuable

failed

14.14 Dynamic content based on user input

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

potentially valuable

passed

14.15 Book recommendations based on personal preferences

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

potentially valuable

failed

14.16 Book recommendation sharing

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

potentially valuable

inapplicable

14.17 Borrowing history indicator

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

Borrowing history indicator

potentially valuable

cantTell

14.18 Digital clippings archive

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

potentially valuable

cantTell