Missing accessibility metadata
schema.org in the file, ONIX for the channels that ignore it
A reader deciding whether to buy your book cannot open it first. Accessibility metadata is how the shop answers that question, and it has to exist in two places because different channels read different sources.
In the file
schema.org properties in the package document: accessMode, accessibilityFeature, accessibilityHazard, and an accessibilitySummary written for a human being.
<meta property="schema:accessMode">textual</meta> <meta property="schema:accessibilityFeature">alternativeText</meta> <meta property="schema:accessibilityHazard">none</meta> <meta property="schema:accessibilitySummary">All images carry human-reviewed descriptions. Page list matches the print edition.</meta>
In the feed
ONIX Code List 196 values on the product record. Confirm the codes against the current Codelist issue before you send them; the list is revised, and a stale code reads as a false claim.
What Reflow does
Writes only what is true of the delivered file. accessibilityFeature gains pageBreakMarkers only when a real page list exists, alternativeText only when the descriptions were actually written, and the summary names what remains open.