ScribeBloc — home

Accessibility. Built In.

Content as it should be. Readable by all.

ScribeBloc rebuilds inaccessible content — a webpage, a wall-of-text transcript, a form — so it works however people read it: on any screen, with a screen reader, or under pressure.

See a real rebuildHow it works
As issued
Rebuilt
Same words either way. On the left, every line carries equal weight and nothing can be navigated to. On the right, headings, groups and breathing room — the structure a screen reader jumps through.

Enlarging the text is not the same as making it readable.

Ask for a bigger typeface and most content gives you exactly that — and nothing else. Margins narrow to absorb the change. Columns stay put. Seven pages become twenty-plus, and the reader who needed larger text now has three times as much scrolling to reach the dosage.

The text got bigger. The content got harder to use. Nothing was rebuilt — it was only rescaled.

  • 01

    Structure

    Headings, lists, tables and reading order rebuilt so navigation actually works — not styled to look like headings.

  • 02

    Reflow

    Usable at 200% zoom, and at 400% in a 320px viewport, without a page count that punishes you for needing it.

  • 03

    Traceability

    Every line traces back to your original. Nothing appears in the output that was not in the input.

Before / after

A Consumer Medicine Information leaflet, rebuilt

A real pipeline run on a real CMI. Same words, same warnings, same dosage — rebuilt so the reader can find them.

BEFORESource leaflet, as issued
CMI sample 1 — source
page render goes here
AFTERRebuilt, at 200% text size
CMI sample 1 — rebuilt
page render goes here

Awaiting the two CMI samples. Both panels take a render from the pipeline run — nothing here is mocked.

What we will and will not claim

Accessibility is usability. WCAG is how we check it, not how we achieve it. Conformance and comprehension are two separate measurements and we never blend them into one number.

  • Every line traces back to your original.

  • If the system isn't confident, it flags that part rather than guessing.

  • A person checks anything flagged before it goes out.

  • We meet WCAG 2.2 AA and go further where it genuinely helps.

Built for humans. Trusted by machines.

Real headings, honest tables, a reading order that matches the page. A screen reader needs that structure to navigate. So does anything else parsing your content. The same structural work serves both — one job, not two.

For organisations

Web and page remediation for teams and organisations is coming — not built yet.

Get in touch

Have content that fights the people trying to read it? Send it over and say what needs to work.

Or email directly: [email protected]