Outsourcing EPUB production does not outsource responsibility for accessibility metadata. That is the practical point small and midsize publishing teams need to keep straight.
Benetech says publishers are the only entity that can create accessibility metadata for a title, while conversion vendors can add publisher-provided metadata to the file. Its Born Accessible guidance makes the same boundary more operational: publishers should provide title-specific accessibility specifications, review the completed file, and treat ONIX as a supplement to the schema.org metadata carried in the EPUB itself.
That matters because accessibility workflows often break at the handoff. The vendor may do the file work well, but the publisher still owns the claim being made to readers, retailers, libraries, and other downstream partners.
What Benetech actually says about the handoff
In Benetech’s guidance on working with a digital production vendor, the organization says conversion vendors should receive accessibility specifications for each title and that the completed file should be reviewed by the publisher’s production team. The same page says vendors can add publisher-provided accessibility metadata, but cannot create that metadata for the publisher.
The Born Accessible publisher guidance repeats the same rule in slightly plainer workflow terms. The publisher provides the specifications. The vendor executes against them. The publisher reviews the result.
- Publisher role: define accessibility expectations, create the metadata claim, and approve the final file.
- Vendor role: implement the file work, add the publisher-provided metadata, and return a file that can be reviewed against the brief.
- Shared risk: if the handoff is vague, the final EPUB may be cleaner than the metadata suggests, or the metadata may overstate what the file really supports.
That division is useful because it prevents a common excuse. A publisher cannot assume the vendor will invent the right metadata layer on its behalf, and a vendor should not be expected to make the publisher’s conformance claim for it.
Why the metadata owner matters
Accessibility metadata is not just a technical appendix. It is part of how a publishing team describes what a title supports and where its limitations still sit.
Born Accessible says accessible EPUB files in its workflow should include required accessibility metadata and conformance-reporting metadata created with schema.org. It also says vendors must not use the program-specific certification markers unless those are supplied by a certified publisher.
The practical lesson is broader than one certification program. Metadata authority belongs with the party making the publishing claim. That is why the publisher has to own the summary, the features being asserted, and any certification language attached to the file.
Where ONIX fits after the EPUB is done
Born Accessible’s metadata guidance also says ONIX codelist 196 contains EPUB accessibility details and should be treated as a supplement to schema.org accessibility and conformance metadata.
That is an important workflow point for Rex readers. The EPUB file and the commercial metadata record are doing different jobs:
- Schema.org metadata in the EPUB carries file-level accessibility and conformance details.
- ONIX metadata downstream helps distributors, retailers, and library-facing systems expose those details beyond the file package itself.
- Publisher review across both layers keeps the accessibility claim consistent from production through distribution.
Without that connection, teams can end up with a reasonable file and weak discoverability, or with sales metadata that promises more than the reading experience actually delivers.
A safer workflow for small publishing teams
The cleanest way to use this guidance is to treat vendor outsourcing as an execution handoff, not a responsibility transfer.
- Write title-specific accessibility specifications before conversion starts. Do not rely on a generic vendor assumption about what the book should support.
- Decide who owns the metadata package internally. The role may sit with production, metadata, or digital operations, but it should not be ownerless.
- Require the vendor to return both the file and the implemented metadata details. That makes review faster and cleaner.
- Review the completed EPUB against the original specifications. Benetech is explicit that the publisher should check whether the requirements were actually met.
- Push matching accessibility details into ONIX. Distribution metadata should reflect the same reality the EPUB file does.
This is less dramatic than compliance-heavy accessibility talk, but more useful. A disciplined handoff is often what separates an accessible workflow from an accessible-looking one.
The practical takeaway
If your publishing team outsources EPUB production, keep the roles straight. The vendor can execute the work and add the metadata you provide, but the publisher still owns the accessibility specifications, the metadata claim, and the final signoff.
That is the safer rule for authors, rights holders, and publishing teams because it keeps responsibility attached to the organization making the book available in the market.
For related workflow guidance, see our piece on accessibility metadata in ONIX, our guide to manual EPUB accessibility review after automated checks, or contact Rex Publishing.