Check the following to confirm the quality of an e-book.
Use the ePub Validator tool in the Digital Hub.
Check for common validation errors such as: dead or incorrect links; images or files in the package but not declared in the manifest section of the OPF file—every ePub directory should contain only the files necessary for the ePub.
Use the CSS Lint online validator or another validation method to confirm that there are no errors.
Review in the following devices and apps: Chrome Readium; iPad; Nook; Kindle
Table of Contents
Do a page-by-page review.
Are those styles defined correctly in the CSS?
Irregular page breaks may be due to the automatic division of oversized files.
To ensure proper layout on an iPad, each section that should start on a new page should be in its own HTML file. Scribe’s default standard is to optimize all ePubs for the iPad.
For an ePub to meet the requirements for Apple’s iBooks Store, no individual HTML file can be larger than 300KB.
If not, identify which list classes are not displaying properly and locate them in the CSS to look for possible causes.
Examples: Border vs. no border; do columns have appropriate proportions?
Tables with more than four columns might not render well on reading devices and might be cut off. Search the HTML files for