Preserve the lesson when an EPUB interaction cannot run

Separate the information goal from the interaction

Describe what the reader should learn or decide without naming the control. For a comparison slider, the goal may be to understand a difference between two product configurations. For a self-check, it may be to explain why an answer is appropriate. Identify all information that exists only after an interaction, including qualifications and feedback. A decorative animation needs a different fallback from an essential explanation.

W3C EPUB 3.3 distinguishes scripting contexts and permits intrinsic or manifest-level fallbacks. Its guidance cautions that manifest fallbacks have weak practical support. Therefore, a production declaration alone is not sufficient acceptance evidence; the release owner needs a demonstrated route to the essential content in the intended readers.

Specify an alternative that preserves the learning task

Write the nonscripted alternative in ordinary editorial terms before choosing its technical implementation. A static comparison can retain labeled states and an explanation of their difference. A self-check can expose the question, considered options and reasoning through an appropriate reading sequence. The alternative need not reproduce every gesture, but it should not remove the fact the interaction was meant to teach.

Have the editor compare both routes for factual agreement and completeness. Keep changed quantities, restrictions and labels consistent. Avoid a fallback that says only that interactive content is unavailable or sends the reader to an unrelated homepage. If an external alternative is necessary, state the dependency honestly and establish whether it meets the publication’s promised access conditions rather than assuming every reader has connectivity or an account.

Test the unavailable-feature state deliberately

Ask the qualified production owner to provide a controlled test in the relevant nonscripting or unsupported context. Do not disable security protections or install unrecognized software to make the demonstration run. Inspect what the reader actually encounters: a useful alternative, an empty region, an inert control or contradictory content. Then verify the main reading sequence can continue without a trapped focus or unexplained missing step.

The W3C reading-system specification makes scripting behavior context-dependent and addresses fallback processing when scripting is unsupported. Treat that as a technical review boundary, not proof that a particular export is usable. Keep the system/version, content context and observed result together so a working browser preview is not silently substituted for evidence from the intended EPUB reader.

Accept the two paths as one maintained explanation

For each tested interaction, record the primary result, alternative content and any unresolved loss of meaning. Route implementation failures and editorial omissions to different owners. If the fallback cannot preserve a necessary task within the supported distribution, reconsider the feature or provide a suitable edition rather than labeling the publication universally interactive. A limitation must be specific enough for the publishing owner to make a real distribution decision.

After revisions, compare both paths again. Changing the interactive answer without changing the static explanation creates two competing editions inside one package. Keep the accepted content revision, implementation revision and final export linked. Technical validation and accessibility review remain valuable separate checks; neither should be described as proof that every optional feature ran in every reader. Acceptance means the essential explanation survives the states the team actually evaluated.

Make the reasoning concrete.

A fictional equipment guide uses a slider to compare two storage configurations. The only explanation of reduced usable space appears after dragging it. In an intended EPUB reader the slider does not run, leaving a decorative image and no account of the tradeoff.

The publisher accepts the demonstrated alternate explanation. It does not ask readers to weaken security or infer the missing comparison from the image.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Task

   What essential information should the interaction convey?

2. Alternative

   How can that information be understood without executing it?

3. Context

   Which intended reading states cannot run the feature?

4. Evidence

   What does the final candidate show in each tested state?

5. Maintenance

   Who keeps the primary and alternate explanations consistent?

Watch for the wrong conclusion.

• Equating a browser preview with an EPUB-reader test.
• Treating an unavailable notice as a complete information fallback.
• Updating an interactive answer while leaving its alternate explanation obsolete.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis. W3C specifications support only the attributed format and reading-system distinctions. Named-version tests, qualified accessibility review and editorial acceptance remain separate; no universal compatibility or conformance claim is made.

• W3C: EPUB 3.3 →Primary W3C technical specification · Supports: Supports scripting-context and fallback distinctions, including the practical manifest-fallback caution.
• W3C: EPUB Reading Systems 3.3 →Primary W3C technical specification · Supports: Supports context-dependent scripting and unsupported-script fallback processing.