Support and methodology

Guidance for using AutoDots within a controlled document process.

The product is most useful when it reduces preparation time while leaving review, sign-off, and context in place.

What to expect

Prepare Braille-ready output from the source document.
Apply review where the document carries formal or technical risk.
Choose a plan based on volume, technical content, and review needs.

Braille standards

Unified English Braille

AutoDots is built for Unified English Braille workflows so the output stays aligned with the reading and production practices most teams already use.

That does not mean every document is automatically final. It means the draft is shaped for a braille workflow rather than flattened into plain text.

Workflow posture

Why review stays in the loop

Tables, notation, diagrams, and mixed-layout pages can be prepared more quickly with the product, but they should not be treated as final output in high-stakes contexts without review.

The strongest use of AutoDots is operational: it shortens the path to Braille-ready output and makes the handoff to review clearer.

Review states

Draft

Workflow output that has not been checked by the AutoDots team.

Reviewed

A team member has compared the sample against the source and recorded the known limitations.

Verified

The sample has cleared the current publication checklist and is eligible for the public catalogue.

FAQ

What kinds of files does AutoDots work with?

AutoDots supports common document and image formats, including PDFs, Word documents, and image-based pages. The product is designed to preserve structure and surface visual content where possible so the resulting output is easier to use and easier to check.

Does it handle maths, tables, and technical content?

Yes. Technical content is where structured output matters most, because it gives a reviewer a much stronger starting point than rebuilding the document from scratch.

Can I use AutoDots for school or commercial work?

Yes. Teams use AutoDots in schools, exam support, family workflows, and business accessibility work. The right plan depends on volume, technical complexity, and whether you need review tooling or embosser-ready export.

Is the output final?

AutoDots can produce useful Braille-ready output for everyday work, but formal release still depends on the document, the source quality, and the level of review required. Public examples are labelled Draft, Reviewed, or Verified so that distinction remains clear.

What standards does AutoDots follow?

AutoDots is built for Unified English Braille workflows and practical tactile-formatting review. Final acceptance still belongs to your own organizational or transcriber-led process.