Our Approach

Accessible Notes is built around a simple idea: accessible documents should be the default, not an extra step. Every choice in the processing pipeline — from how your uploads are transcribed to how each export format is generated — is made with accessibility in mind.

What every export includes

Regardless of which format you export to, your document will contain:

Proper heading hierarchy. Headings flow from H1 down through H2, H3, and so on, without skipping levels. This matters because screen reader users navigate documents by jumping between headings — a consistent hierarchy makes that navigation predictable and efficient.

Alt text for all diagrams. The alt text you write in the Diagrams tab is embedded in every export format. A person using a screen reader will hear your description read aloud in place of the diagram.

Semantic markup. Lists are real lists, tables are real tables, figures are real figures. This gives assistive technology the information it needs to convey structure, not just visual appearance.

Tagged/structured content. In formats that support it (PDF and DOCX in particular), content is tagged so that screen readers can navigate by section, identify reading order, and understand the role of each element.

Format-specific accessibility

PDF — Exports meet the PDF/A-4f standard, which incorporates PDF/UA (Universal Accessibility). Fonts are embedded, document structure tags are included, and diagrams are native TikZ vector graphics that scale without quality loss at any zoom level.

Word (DOCX) — Headings use Word's built-in heading styles, which enable the navigation pane and proper screen reader behavior. Diagrams are embedded as SVG images with alt text set on the image object itself.

HTML — Output uses semantic HTML5 elements with ARIA attributes where helpful. Diagrams are inline SVG with aria-label set from your alt text. The document structure is readable by browser accessibility tools.

Markdown — Headings follow a consistent hierarchy. Diagrams are wrapped in <figure> elements with captions. Callout blocks use the GitHub-style syntax that most markdown renderers understand.

How transcription supports accessibility

The transcription engine is specifically configured to produce accessible output:

• Heading levels are structured logically, not just based on visual size in the original
• Diagram alt text is generated as a starting point — always review and refine it before exporting
• Math notation is formatted as standard LaTeX that renders correctly in all export formats
• Content structure (lists, tables, callouts) is preserved or inferred from the original layout

Auto-generated alt text is a draft, not a final answer. Read each diagram description and ask whether someone who couldn't see the diagram would understand what it shows. If not, update it before exporting.