About
Why this exists, and why I am building it.
Why ScribeBloc exists
ScribeBloc began with a simple problem: information can be available, accurate and technically accessible — and still be difficult to use.
A document can contain the answer and still make someone work too hard to find it. A webpage can meet a technical standard and still be confusing. A student can have all the material they need and still struggle to turn it into something they can study from.
The gap between information being available and information being usable is where ScribeBloc began.
Why I am building it
My background is in helping people navigate complex information. As a university librarian, I taught students how to find, evaluate and use research. Later work has included digital content, accessibility, , design and AI-enabled content systems.
How information is organised, labelled and connected, so someone can find what they need and know where they are while they look for it.
I have also contributed to AI content governance and publishing. That work sharpened my focus on trustworthy AI-assisted content, human review, source fidelity and the risk of unsupported generated material.
My web development and AI architecture experience means I can build and operate the first ScribeBloc engine myself. What I learn from users can feed directly into the next information journey, workflow or test without waiting for an external development cycle.
Across these experiences, the same issue kept appearing: access to information is not the same as being able to use it.
How it is designed
There is no average reader
People differ in knowledge, language, attention, time, device, context and purpose. One standard version cannot work equally well for every person, situation and task.
- KnowledgeWhat someone already knows about the subject
- LanguageReading in a first, second or third language
- AttentionFocused, interrupted, or exhausted
- TimeTen minutes, or a full study session
- DeviceA phone on a train, or a desktop at work
- ContextRevising, deciding, checking or acting
- PurposeWhat the information is actually needed for
ScribeBloc restructures information around what the person needs it for, rather than assuming everyone can adapt to a “standard” version.
Accessibility should be considered a baseline. Usability is our goal.
matter. For universities and other organisations, WCAG conformance, screen-reader compatibility, readable typography, layout and mobile usability are essential baselines.
WCAG — the Web Content Accessibility Guidelines — is the international baseline: content has to be perceivable, operable, understandable and robust. It is what most universities and government bodies are measured against.
This approach is informed by : designing for human variation from the beginning. The same source may need to work differently for different people and tasks.
Judging the work by whether the result can actually be used for the job someone needs it for — not by whether it satisfied a checklist.
Designing for the full range of human variation from the beginning, rather than building one standard version and adapting it afterwards for the people it left out.
One engine. Different information journeys.
Accessibility is one path among several — alongside plain language, study-ready structure, translation and other fit-for-purpose versions. One underlying restructuring engine, instead of a separate product for every audience.
Where ScribeBloc is now
ScribeBloc is in development and customer discovery.
The aim is simple: you bring the source, you get something you can actually use, and you can see what changed.
See a worked example — a spoken law lecture restructured into study-ready notes.
References
The sources behind the terms used on this site. These links leave ScribeBloc.
- Accessibility and usabilityAccessibility: Usability for allInteraction Design Foundation
- Information architectureWhat is Information Architecture?Interaction Design Foundation
- Accessibility standardsAccessibility fundamentalsW3C Web Accessibility Initiative
- Universal DesignCenter for Universal DesignNorth Carolina State University
- Outcome-oriented designOutcome-oriented design (video)YouTube
Get in touch
If you have information that is hard to use, or you want to follow the build, email [email protected].