KDP Publishing 05: Run Local EPUB QA

A pass badge does not guarantee the entire reading experience.

What You Will Produce

• Objective: Record EPUBCheck and visual QA results with location, impact, disposition, reviewer, and retest status.
• Action: Complete three QA records and decide whether each correction requires a new hash.
• Evidence: A QA log with error and warning dispositions, retest results, and explicit author visual approval.

Automated Validation Finds Structural Failures

Check chapters, navigation, links, images, language metadata, and alternative text. Record every warning instead of deleting it from the story. A warning needs a disposition and evidence.

Visual QA Finds Reading Failures

Preview on more than one device profile and vary font size, theme, and orientation. Look for broken hierarchy, clipped images, poor contrast, awkward page breaks, and navigation that behaves differently from the source.

Practice: Complete Three QA Records

For each sample defect, write the location, reader impact, correction, reviewer, and retest result. When content changes, record that the build hash and downstream evidence must also change.

Where This Fits in the Series

Closing Principle

Automated checks and human reading checks find different classes of failure; neither replaces the other.

References

• Amazon KDP Help

This article is for preparation and quality assurance. Never capture or record passwords, cookies, tokens, tax identifiers, bank identifiers, or private manuscript identifiers.

Series Navigation

Previous: KDP Publishing 04: Produce Evidence for a Reflowable EPUB
Next: KDP Publishing 06: Lock the Listing Snapshot