Skip to main content

Accessibility document workflow

Produce Braille-ready output within a controlled review process.

AutoDots produces structured Braille-ready output from source documents and keeps review status visible throughout the workflow. It is designed to reduce turnaround time without removing the checks required for formal output.

Structured drafts with visible review status

Suitable for schools, examination teams, and accessibility services

Faster preparation before specialist review

Who it is for

Built for teams who need a document process, not just a quick answer.

Different teams use AutoDots for different reasons, but the common need is consistent: a faster route to a reviewable Braille draft.

Useful when access delay is the real blocker

Vision impairment

Read letters, forms, and school materials faster without waiting on an opaque process.

Built for practical turnaround, not perfect theory

Parents and families

Keep homework and school notices moving when accessibility support cannot match the pace of the week.

Draft-first workflow for overstretched teams

Schools and universities

Reduce repetitive transcription effort so specialist staff spend more time on high-value review.

Useful when deadlines and layout complexity collide

Exam boards

Generate structured Braille-ready output for complex papers while keeping final sign-off where it belongs.

Supports lower-friction response for routine documents

Businesses

Handle accessibility requests through a documented document workflow instead of an ad hoc process each time.

Workflow

A document process designed for review.

The product is most useful when it shortens the path to structured Braille-ready output and makes the handoff to review clearer.

01

Receive the source document

Upload the file or image and prepare structured Braille-ready output without rebuilding the page manually.

Review status retained
02

Preserve structure and identify issues

Keep question order, tables, and flagged sections visible so the next review step is clear.

Review status retained
03

Review and export appropriately

Use the draft where that is suitable, or keep it in review before release when the document is formal or high-stakes.

Review status retained

Output examples

Examples that show structured output in practice.

These samples show the kind of Braille-ready output the workflow produces across text, notation, and visual material.

Technical notation

Notation survives as structured content that can still be checked before final use.

Source

Angle = (frequency ÷ total) × 360°

Braille-ready output

Charts and data

Visual material becomes text and structure that a reviewer can validate rather than infer from a screenshot.

Source

Pie chart: Charity fundraising. Sponsored walk 40%, bake sale 25%, donations 20%, raffle 15%.

Braille-ready output

Structured documents

Headings, lists, and straightforward reading order remain visible in the draft rather than being flattened away.

Source

Course syllabus: Introduction to UEB

Braille-ready output

Why teams trust the workflow

The workflow is designed to make review easier, not unnecessary.

That means preserving structure, surfacing flags, and making clear where human judgement still belongs.

Structured intake

The workflow keeps headings, lists, question order, and page-level structure visible for downstream review.

Layout-aware handling

Tables, notation, and short visual references are treated as part of the document, not as disposable decoration.

Visible uncertainty

Problem areas can be flagged so a reviewer knows where to look instead of discovering risk by accident.

Clear review states

Draft, reviewed, and verified are product states, not marketing claims.

Trust and evidence

Trust should be documented.

AutoDots publishes examples, review states, and benchmark summaries so users can see what has been checked, what has not been checked, and where human review remains necessary.

Braille workflow knowledge

Designed around practical braille production, including the distinction between a useful draft and a publishable final version.

Published methodology

Public trust labels explain how samples are checked and when a document should still be reviewed by your own team.

Public trust page

Review states reflect actual checking.

Draft means unreviewed workflow output. Reviewed means a team member checked the sample. Verified is reserved for entries cleared for public catalogue publication.

Plans

Start on Free. Upgrade when volume or review requirements increase.

Free is intended for occasional document checks. Paid plans provide higher volume, technical handling, review tools, and export options for regular accessibility work.

Included on Free

  • 10 pages each month
  • 1 document upload each month
  • A practical starting point for occasional checks