Crius Group

Expertise

Digital Services

Accessible, structured digital output from a single source.

Digital publishing formats (ePub3, XML, and accessibility tooling) layered over a laptop

Overview

Once a title is structured, every digital deliverable the market requires is generated from the same source: accessible ePub3, structured XML, print PDF, and ONIX metadata. The European Accessibility Act has made ePub3 accessibility a legal requirement for most publishers selling into the EU from 28 June 2025. We deliver it by default, not as an add-on. Our digital workflows also future-proof your content: a single validated XML source drives all outputs, so format changes never mean starting again.

Pain points we solve

What makes digital delivery hard to get right.

  • Accessibility compliance (EAA) deadlines creating uncertainty
  • Maintaining separate print and digital sources that drift apart
  • Metadata and validation requirements that slow distribution

Process

How it works

From
Typeset or structured content
To
Accessible ePub3 · XML · PDF · ONIX
  1. Ingest structured or typeset source

  2. Generate accessible ePub3, XML, and PDF

  3. Validate accessibility and metadata

  4. Deliver distribution-ready files with ONIX

Accessible ePub3 vs standard ePub3: what the difference means in practice
FeatureStandard ePub3Accessible ePub3 (EAA-compliant)
Logical reading order declaredNot requiredRequired
Semantic structure (headings, landmarks)RecommendedRequired (WCAG 2.1)
Alt text for imagesOptionalRequired
MathML for equationsOptionalRequired where maths is present
Accessible tablesNo specific requirementRequired (headers, scope)
Accessibility metadata in packageNot requiredRequired (EPUB Accessibility 1.1)
ONIX accessibility metadataNot requiredRequired for EU distribution under EAA
Screen reader compatiblePartial, depends on contentYes, validated
EAA compliant (EU market from June 2025)NoYes

Good to know

Single-source publishing
A content production approach in which one validated source file, typically structured XML, is used to generate all output formats: print PDF, accessible ePub3, web pages, and data feeds. Changes are made once and propagated to every format. This reduces duplication, version drift, and per-format production cost.
ONIX
Online Information eXchange. An XML standard developed by EDItEUR for communicating bibliographic and commercial book metadata between publishers, distributors, retailers, and libraries. ONIX records carry title, author, ISBN, subject classification, pricing, availability, and, for accessible ebooks, the accessibility metadata required under the EAA.

What is the difference between an accessible ePub3 and a standard ePub3?

A standard ePub3 may have valid structure and render correctly in most reading apps, but it may lack features that make it usable by people with disabilities: missing alt text, for example, no logical reading order declaration, or inaccessible tables. An accessible ePub3 additionally conforms to EPUB Accessibility 1.1 and WCAG 2.1: it has a declared reading order, semantic structure, alt text, MathML for equations, and accessibility metadata. The EAA requires accessible ePub3 for EU markets from 28 June 2025.

What is ONIX metadata and who needs it?

ONIX (Online Information eXchange) is an XML-based standard that publishers use to send bibliographic and commercial metadata (title, author, ISBN, price, subject codes, availability) to retailers, aggregators, and libraries. Most major distribution channels require ONIX. Accessibility metadata must also appear in the ONIX feed for ebooks sold in the EU under the EAA.

How does single-source publishing reduce production cost over time?

In a single-source workflow, every output format (print PDF, accessible ePub3, XML data feeds) is generated from one validated source file. Updates, corrections, and new editions require changes in one place only. This eliminates the cost of maintaining parallel files and the errors that arise when files diverge across editions.

Frequently asked questions

  • What digital publishing services does Crius Group provide?

    We produce accessible ePub3 (EAA-compliant), run structured XML publishing workflows, and generate print PDF and ONIX metadata from a single source, so one validated file drives all your output formats.

  • Is accessible ePub3 production included by default or is it an add-on?

    It is included by default. Every ePub3 we produce meets the EPUB Accessibility 1.1 specification and WCAG 2.1 requirements, with accessibility metadata declared in both the package document and the ONIX feed.

  • What is ONIX and why does it matter?

    ONIX (Online Information eXchange) is the standard format for communicating book metadata to retailers, distributors, and libraries. Accurate ONIX is required for most distribution channels. We generate and validate ONIX alongside the ePub3 so your titles are not held up at distribution.

  • Does the European Accessibility Act affect ebooks I am publishing now?

    Yes. The EAA applies to ebooks placed on the EU market from 28 June 2025. If you sell ebooks in any EU member state, new titles should already be accessible. We can assess your current output and remediate existing files.

Ready to start a production line?

Log in to the portal to submit a request, or reach out and we'll set things up together.