Braille and Multi-Format Delivery — One Source, Many Outputs

BRF, EPUB, HTML, and PDF/UA should flow from one structured source — not four separate manual production tracks.

6 min read
Back to BlogVisit Trust CenterRequest SOC 2 Report

If your alternate format shop maintains separate production lines for BRF, accessible PDF, and HTML — and re-keys STEM content manually for Nemeth — you are not running a format pipeline. You are running four factories for the same book.

The fix is structural. When the source carries reliable semantic structure once, every downstream format inherits it, and multi-format delivery stops being four parallel jobs.

One structured source document branching into four output formats: PDF/UA, HTML, EPUB, and BRF braille.
Structure the source once; PDF/UA, HTML, EPUB, and BRF all inherit the same logical content.

Braille is not outdated — unstructured sources are

Digital-first workflows did not replace Braille. They replaced reliable paths to BRF. Students using refreshable Braille displays still need:

  • Correctly structured source text
  • Nemeth code for mathematical content
  • Tactile graphic decisions documented when visual diagrams carry meaning

Braille fails upstream when the source fails structure — not when the embosser fails.

Why source structure determines every format

OutputWhat it needs from source
PDF/UATags, reading order, table headers
HTMLSemantic headings, described figures, MathML
EPUB 3Navigation document, alt text, accessible math
BRFClean text flow + Nemeth for equations

Fix structure once and all formats inherit the same logical content.

Nemeth Braille for math is non-negotiable in STEM

Generic BRF conversion from image-based math produces gaps, placeholders, or prose approximations — unusable for STEM courses.

Morf Transformation integrates Nemeth Braille workflows in the same pipeline as MathML and tagged PDF output — so math courses do not fork into a manual transcription track.

One upload, multiple deliverables

  • Ingest — DOCX, PDF, PPTX, or scan
  • Structure repair — tags, OCR cleanup, math extraction
  • QA — automated validation plus expert review
  • Deliver — PDF/UA, HTML, EPUB, BRF as required

Disability services teams stop choosing one format per crisis and start fulfilling student preference from one job.

Bottlenecks to eliminate this term

  • Re-OCR of the same scan for each output format
  • Manual Nemeth entry parallel to HTML production
  • Faculty PDFs remediated only to tagged PDF, with BRF requested later as an emergency

What changes in your pipeline tomorrow

Tomorrow: For the next student request, ask — "Will anyone else need a different format from this same source within 30 days?" If yes, structure the source first and generate all required formats in one pass. Do not ship tagged PDF today and queue BRF next week.

Next step: Upload a document and request multi-format output (PDF/UA, HTML, BRF).