Accessibility metadata work is easy to over-credit once the technical fields are filled in.
But a complete ONIX or EPUB record does not help much if the reader-facing display is awkward, English-only, or invisible where discovery happens.
That is the practical point behind DAISY’s Accessibility Metadata Display Guide 2.1 release. The guide is aimed at implementers such as bookstores, retailers, distributors, and libraries, but it also matters to publishers because it shows what happens after metadata leaves the production system. If accessibility information is supposed to help readers choose usable books, it has to make sense on the surface.
For Rex readers, the business lesson is simple: accessibility metadata is not finished when it becomes machine-readable. It also has to become understandable.
Why display is part of the workflow, not an afterthought
DAISY says the display guide exists to help implementers present machine-readable accessibility metadata in clear, user-friendly ways so users can judge whether a digital publication meets their needs before purchase or use. That framing matters because it shifts the work from pure compliance language into discoverability and reader decision-making.
BISG makes a similar supply-chain point in its Accessibility Working Group overview. The group describes accessibility information as something that must be created, communicated, and displayed, with discoverability, library procurement, and public-sector sales all part of the value. In other words, accessibility metadata that never becomes legible to buyers, librarians, or readers is only doing part of its job.
That fills an important gap in our earlier accessibility metadata ONIX workflow guide. Entering the right metadata is necessary. It is just not the end of the workflow.
What changed in version 2.1, and why it matters
DAISY says version 2.1 keeps the guide’s high-level display principles stable, but updates the EPUB and ONIX techniques in a way that matters operationally. Earlier approaches used concatenation to combine static text and dynamic values. The 2.1 update instead uses placeholders that insert metadata values into display strings.
That may sound like a small implementation detail, but it solves a real localization problem.
When display strings are hard-coded around one language’s sentence structure, the result can be stiff, confusing, or inaccurate once a storefront or library interface has to serve multiple languages or date formats. Placeholder-based strings give implementers more flexibility to express the same metadata naturally in different languages rather than forcing every locale to mimic English phrasing.
The W3C localization repository for the display guide makes the rationale explicit: readers want consistent accessibility information across bookstores and libraries, but simply translating strings is not enough. Accessibility concepts have to be localized for effective communication. That is a workflow issue, not just a copy-editing issue.
Where publishers should pay attention
Most publishers will not be the final team rendering every user-facing accessibility label. Even so, the display guide has practical implications upstream.
- Use metadata that can survive downstream display. Vague, inconsistent, or incomplete accessibility fields are harder for partners to translate into useful statements.
- Check how key accessibility claims appear in real interfaces. If a distributor or retailer surfaces the information awkwardly, the issue may be partly display logic and partly input quality.
- Plan for multilingual markets early. A metadata workflow built around one language can create expensive cleanup once books move across regions or public-sector channels.
- Treat discoverability as part of accessibility. If a reader cannot tell whether a book supports their needs, the technical accessibility work is still partly hidden.
This is especially relevant for teams already working through broader accessibility changes in ebook production. Our EPUB accessibility under the EAA guide focuses on file-level and process-level readiness. Display guidance addresses the next problem: whether that work becomes understandable in the market.
The practical takeaway for small and midsize publishing teams
The safest approach is to think of accessibility metadata as a chain with three separate jobs:
- Create accurate metadata. The record has to describe the publication honestly.
- Transmit it cleanly. ONIX, EPUB, and partner feeds need to preserve the signal.
- Display it clearly for humans. The final wording has to be visible, natural, and meaningful in the reader’s language.
That third job is where many workflows still feel unfinished. A standards-compliant record is useful infrastructure, but it does not automatically become a good discovery experience.
So the real lesson from the updated display guide is not that publishers need one more abstract standard to track. It is that accessibility information has to travel all the way from metadata entry to reader understanding. If the chain breaks at the display layer, the market signal weakens right where it is supposed to help.
If you need help tightening accessibility, metadata, or multilingual publishing workflows, contact Rex Publishing.