Ebook teams often treat accessibility, rights signaling, metadata, interoperability, and final QA as separate conversations. That split is expensive. It creates handoff gaps, makes release checks inconsistent, and leaves small teams depending on whoever happens to notice a problem late.
A new open reference from EDRLab and the French Publishers Association gives the industry a more usable model. Qualebook is presented as a shared quality checklist for digital books, built to help publishing teams coordinate work across the full ebook production process rather than treating each requirement as its own silo.
The important guardrail is that Qualebook is not a formal standard or certification. Its own documentation says it is a practical reference layer meant to make technical expectations easier to understand across design, production, distribution, and management. That is exactly why it matters for Rex readers: it is easier to adopt a checklist than to rebuild your whole workflow around abstract compliance language.
Why this matters now
EDRLab says Qualebook launched in January 2026 as a shared, open-quality reference for digital books and that the framework includes 87 concrete rules. On the project’s About page, Qualebook says the work was incubated in 2023, prepared in 2024, tested with professional teams in 2025, and is now in a 2026 phase focused on consolidation and collaboration.
That timeline matters because it suggests this is not just a one-off blog idea or a vendor pitch. It is an attempt to turn a growing pile of digital-publishing expectations into a common operating language.
Qualebook’s own framing is broader than file validation. The project says publishing teams now need coordinated expertise in performance, interoperability, accessibility, eco-design, security, and personal-data management. In plain terms, ebook quality is no longer just about whether the EPUB opens. It is about whether the publication is reliable, understandable, rights-aware, and ready for distribution.
What makes the checklist operational
The useful part is that the framework is public and concrete. Qualebook exposes the rules in browser form and also offers JSON and CSV exports, which means teams can use the material in internal guidance, production documentation, training, or tooling.
The public rules page already shows why this can work as a workflow reference instead of a vague quality slogan. Early rules include:
- Copyright and reuse information is available.
- The ebook specifies its text and data mining and usage rights.
- The source code of each book section includes metadata describing its content.
- Dates use explicit and unambiguous formats.
That mix is what makes the project interesting. It connects reader-facing quality, machine-readable structure, and rights-related clarity in one place. For small and mid-sized publishers, that is more useful than maintaining separate disconnected checklists for metadata, accessibility, and release QA.
How a small publishing team could use it
Most teams do not need another abstract framework. They need a repeatable pass that catches the same classes of problems before release.
- Use it as a shared review sheet. Put editorial, production, metadata, and distribution teams on the same checklist instead of letting each group keep private assumptions.
- Map the rules to your handoff points. Some checks belong at manuscript preparation, some at EPUB creation, and some right before channel delivery.
- Treat rights signaling as production data. If copyright, reuse, or text-and-data-mining information matters, it should not live only in contracts or email threads.
- Fold training into production. Because the rules are open and concrete, they can double as onboarding material for staff and freelancers.
- Adapt, do not worship. Since Qualebook is not a norm or certification, teams can use it as a practical baseline without pretending every title needs the exact same implementation depth.
This is also the safest way to talk about the framework. It is a reference for better decisions, not proof that an ebook is automatically excellent because boxes were ticked.
The real takeaway for Rex readers
The strongest idea in Qualebook is not that it has 87 rules. It is that ebook quality becomes more manageable when one checklist can connect accessibility, metadata, rights communication, and technical release readiness.
That matters for authors and rights holders because many avoidable downstream problems start as workflow fragmentation: metadata does not match the file, rights language is unclear, accessibility work is hard to discover, or production teams are asked to fix policy questions at the end.
If your digital publishing process still treats those issues as separate cleanup tasks, Qualebook is worth studying as a coordination tool. Just keep the framing honest. It is an open reference checklist, not an official industry mandate.
If you are tightening multilingual or digital-production workflows, see our guide to accessibility metadata in ONIX or contact Rex Publishing.