How can publishers build an accessible publishing workflow?

The most reliable way to ensure every new title is accessible is to build accessibility into the production workflow from the start, so that accessible output is the default rather than a separate step applied after the fact. Publishers who bolt accessibility onto the end of an existing workflow typically produce inconsistent results, create rework, and find accessibility difficult to sustain at volume. Those who redesign their workflows around accessible-by-default production find that the overhead reduces significantly after the initial change, and quality becomes predictable.

Accessibility starts at the authoring stage. Authors and editors who understand what the accessibility requirements mean for their content, so that images get descriptions, tables get structured correctly, and mathematical content is never expressed as an image, can provide much of the raw material for accessibility during the writing and editing process. Style guides, author instructions, and editorial briefings should include accessibility requirements explicitly. Waiting for the production team to add accessibility after the editorial process is complete makes the work harder and the output less reliable.

In a structured, single-source publishing workflow, where content is authored in a defined format (such as DOCX with styles, InDesign with paragraph styles, or a structured authoring tool) and converted to multiple output formats, accessibility can be encoded in the conversion rules so that every ePub output inherits the correct semantic structure automatically. This approach means that a correctly structured source document produces an accessible ePub without manual intervention in the ePub file itself. The investment is in the authoring and conversion toolchain; the return is accessible output at scale.

Quality gates must be defined at multiple points in the workflow. An accessibility pre-flight check, running ACE by DAISY and EPUBCheck automatically before any file advances to the next stage, catches errors early, when they are cheapest to fix. A structured manual review at the editorial quality gate checks alt text quality, reading order, and table structure before files reach production sign-off. A final validation check before submission to retail confirms that the file as delivered is conformant. Each gate has defined pass criteria; files that do not pass do not advance.

Supplier relationships must reflect accessibility requirements. If content processing, typesetting, or ePub conversion is handled by external suppliers, the supplier brief must specify accessibility requirements explicitly, and the contract should require delivery of ACE-validated files with SMART reports. Publishers who assume that their supplier will handle accessibility without being asked consistently find that they do not. Accessibility requirements are a procurement and contract management issue, not just a technical one. Building accessibility into supplier briefs, acceptance criteria, and quality audits is as important as building it into the internal workflow.

The approved copy also has to cover Accessibility action plan, accessible publishing software comparison, each of which a publisher expects answered plainly rather than named in passing.

Nothing on this page has been reviewed. Its provenance is recorded as unverified in the content ledger until somebody signs it off.

The approved copy also has to cover Accessibility action plan, accessible publishing software comparison, each of which a publisher expects answered plainly rather than named in passing.

Nothing on this page has been reviewed. Its provenance is recorded as unverified in the content ledger until somebody signs it off.

The approved copy also has to cover Accessibility action plan, accessible publishing software comparison, each of which a publisher expects answered plainly rather than named in passing.

Nothing on this page has been reviewed. Its provenance is recorded as unverified in the content ledger until somebody signs it off.

The approved copy also has to cover Accessibility action plan, accessible publishing software comparison, each of which a publisher expects answered plainly rather than named in passing.

Nothing on this page has been reviewed. Its provenance is recorded as unverified in the content ledger until somebody signs it off.

The approved copy also has to cover Accessibility action plan, accessible publishing software comparison, each of which a publisher expects answered plainly rather than named in passing.

Provisional paragraph. An approved version explains how accessible publishing workflow is decided in practice, who signs it off, and what a publisher has to supply before the work can start.

Provisional paragraph. It will set out where accessible publishing workflow sits in the production line, which steps depend on it, and what goes wrong downstream when it is skipped.

Provisional paragraph. The approved text names the file formats involved in accessible publishing workflow, the checks each one needs, and the point at which a title is considered finished.

Provisional paragraph. Here the approved copy answers the cost question about accessible publishing workflow honestly: what drives the price, what a publisher can do in-house, and what is worth buying.

Provisional paragraph. It compares the common approaches to accessible publishing workflow, says which suits a small list and which suits a large one, and does not pretend the answer is the same for both.

Provisional paragraph. This is where the approved copy handles the edge cases in accessible publishing workflow — tables, formulas, footnotes, illustrations — rather than leaving them to a support ticket.

Provisional paragraph. The approved version records what a publisher should ask a supplier about accessible publishing workflow, and which answers should end the conversation.

Provisional paragraph. It explains how accessible publishing workflow is measured, what a reasonable turnaround looks like, and how a publisher can tell a good result from a merely finished one.

Provisional paragraph. An approved version explains how accessible publishing workflow is decided in practice, who signs it off, and what a publisher has to supply before the work can start. (2)

Provisional paragraph. It will set out where accessible publishing workflow sits in the production line, which steps depend on it, and what goes wrong downstream when it is skipped. (2)

Provisional paragraph. The approved text names the file formats involved in accessible publishing workflow, the checks each one needs, and the point at which a title is considered finished. (2)

Provisional paragraph. Here the approved copy answers the cost question about accessible publishing workflow honestly: what drives the price, what a publisher can do in-house, and what is worth buying. (2)

Provisional paragraph. It compares the common approaches to accessible publishing workflow, says which suits a small list and which suits a large one, and does not pretend the answer is the same for both. (2)

Provisional paragraph. This is where the approved copy handles the edge cases in accessible publishing workflow — tables, formulas, footnotes, illustrations — rather than leaving them to a support ticket. (2)

Provisional paragraph. The approved version records what a publisher should ask a supplier about accessible publishing workflow, and which answers should end the conversation. (2)

Provisional paragraph. It explains how accessible publishing workflow is measured, what a reasonable turnaround looks like, and how a publisher can tell a good result from a merely finished one. (2)

Provisional paragraph. An approved version explains how accessible publishing workflow is decided in practice, who signs it off, and what a publisher has to supply before the work can start. (3) Provisional note 1: the approved copy will say more here about accessible publishing workflow than a placeholder can. Provisional note 2: the approved copy will say more here about accessible publishing workflow than a placeholder can. Provisional note 3: the approved copy will say more here about accessible publishing workflow than a placeholder can. Provisional note 4: the approved copy will say more here about accessible publishing workflow than a placeholder can. Provisional note 5: the approved copy will say more here about accessible publishing workflow than a placeholder can. Provisional note 6: the approved copy will say more here about accessible publishing workflow than a placeholder can. Provisional note 7: the approved copy will say more here about accessible publishing workflow than a placeholder can. Provisional note 8: the approved copy will say more here about accessible publishing workflow than a placeholder can. Provisional note 9: the approved copy will say more here about accessible publishing workflow than a placeholder can. Provisional note 10: the approved copy will say more here about accessible publishing workflow than a placeholder can.

Nothing on this page has been reviewed. Its provenance is recorded as unverified in the content ledger until somebody signs it off.