Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 69 of 221; 24 results per page.
An intentionally invalid fixed-layout EPUB: rendition:layout says pre-paginated but no content document declares a viewport meta, so the canvas size is undefined. Intentionally invalid and clearly labelled - for testing validators and the fallback a reader picks when it has no dimensions to scale to.
Exactly the same content and the same set of targets, listed as one flat level. The reference twin for the nested navigation fixture: if a reader renders both identically, it is discarding hierarchy.
A navigation document nested four levels deep with ordered lists inside list items, targeting heading anchors inside two part documents. Paired with a flattened twin so a reader that silently collapses hierarchy is easy to spot.
The same four-level hierarchy expressed as nested NCX navPoints with a depth-first playOrder and a matching dtb:depth, alongside the equivalent nav document. For testing the older navigation path, which nests through element containment rather than through lists.
An EPUB 3 carrying the accessibility metadata distributors now require: schema:accessMode, accessModeSufficient, four accessibilityFeature values, a hazard statement, a written summary, and a dcterms:conformsTo link. The claims are true of the file, so a checker can verify rather than take the metadata's word.
SVG written straight into an XHTML content document, with properties="svg" declared on the manifest item as EPUB 3 requires. The other half of the SVG question: inline vector markup rather than a standalone content document.
An intentionally invalid EPUB whose META-INF/container.xml contains an empty rootfiles element, so nothing points at the package document - even though OEBPS/content.opf is present and correct. Intentionally invalid and clearly labelled; it separates readers that guess from readers that give up cleanly.
An intentionally invalid EPUB where two manifest items carry the same id, so the spine's references become ambiguous and one chapter can be reached twice while another cannot be reached at all. Intentionally invalid and clearly labelled - an XML ID uniqueness violation, not a container defect.
An intentionally invalid EPUB that declares chapter3.xhtml in the manifest, the spine and the contents, while the file itself is not in the ZIP. Intentionally invalid and clearly labelled - for testing the difference between a missing resource and an unreadable book.
An intentionally invalid EPUB 3 that ships only an NCX: no manifest item carries properties="nav", which EPUB 3 requires. Intentionally invalid and clearly labelled - it separates readers that fall back to the NCX from readers that refuse to open a book with no navigation document.
An intentionally invalid EPUB whose spine ends with an itemref pointing at a manifest id that does not exist. Intentionally invalid and clearly labelled - the first three chapters are intact, so a reader can recover if it chooses to.
An intentionally invalid EPUB whose second chapter is declared as text/html instead of application/xhtml+xml, making it a foreign resource in the reading order with no fallback. Intentionally invalid and clearly labelled; the bytes of that file are ordinary, valid XHTML.
The left-to-right control for the direction set: identical package structure to the Arabic fixture, differing only in the language tag and the spine direction. A reference point, not a test case on its own.
The same equation carrying the fallbacks a reader without a MathML engine needs: an altimg raster, its declared dimensions and baseline offset, and an alttext reading of the formula for speech. For testing fallback selection and what a screen reader announces.
An EPUB 3 with a block MathML equation and the required properties="mathml" on its content document. The baseline for MathML support, paired with a twin that omits the declaration.
An intentionally invalid EPUB: the content document contains MathML while its manifest item omits properties="mathml", so the package understates what a reader needs. Intentionally invalid and clearly labelled - identical to its declared twin in every other byte of markup.
An EPUB 3 with a real media overlay: a SMIL document ties three paragraph ids to clip ranges in an embedded MP3, and the package declares media:duration and media:active-class. The narration track is deliberately silent audio, so the fixture stays small and byte-identical on every run.
Three chapters, three SMIL overlays and three MP3 tracks, with a media:duration refines entry per overlay plus the package total. For testing whether a reader plays continuously across document boundaries and whether it sums the per-document durations correctly.
A working media overlay whose package omits the required media:duration metadata entirely. Everything else is intact, so this fixture isolates one question: does the reader refuse the overlay, or fall back to measuring the audio itself?
An intentionally invalid media overlay: the second par's text src points at a fragment identifier that does not exist in the chapter. Intentionally invalid and clearly labelled - for testing whether playback skips the orphaned segment, stops dead, or throws.
Two dc:title elements distinguished only by refines chains into title-type and display-seq, a creator with file-as and a MARC relator role, and a series declared with belongs-to-collection. The structure a catalogue actually needs, and the one flat metadata readers collapse into a single confused string.
A title containing two characters above the Basic Multilingual Plane - a blue book and a musical clef - plus a Japanese description. Anything that counts characters as UTF-16 code units, or truncates a title to a byte length, splits a surrogate pair here.
A package document whose title and creator carry precomposed accents, a combining ring above a bare letter, and a typographic apostrophe. For testing normalisation, sorting and filename derivation - the combining mark is the one that breaks naive length and comparison code.
Every non-ASCII character in the metadata is written as a hexadecimal numeric character reference, so the package document is pure ASCII on disk while the title is Han and Cyrillic once parsed. For testing tools that read metadata with a regex instead of an XML parser.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.
