Document Simplification for Better Accessibility

Every organisation produces documents it considers essential: tenancy agreements, care plans, appointment letters, consent forms, HR policies. Far fewer stop to ask how many of the people receiving them can actually read them. Document simplification for accessibility starts from that uncomfortable question, and it changes how you think about communication altogether. The goal is not shorter documents for their own sake. It is documents that the people affected by them can understand, act on and challenge.

The people your standard documents leave behind

Across the UK, a substantial number of people live with a learning disability, and many more have conditions that affect how they process written information: acquired brain injuries, dementia, low literacy, or English as an additional language. For these readers, a densely worded four-page letter is not merely inconvenient. It is a locked door.

Consider what that means in practice. A care provider sends a resident a letter explaining changes to their support hours. The letter is legally accurate, professionally written and completely opaque to the person it is about. They sign the acknowledgement because someone hands them a pen, not because they have understood what they agreed to. Consent given without understanding is not really consent, and organisations in health, social care and housing know how serious that gap can become.

What document simplification for accessibility actually involves

Simplifying a document properly is a discipline, not a shortening exercise. Easy Read, the format developed for people with learning disabilities and now widely used across UK public services, has clear conventions:

• Short sentences. One idea per sentence, expressed directly.
• Plain words. Everyday vocabulary in place of jargon, with technical terms explained where they cannot be avoided.
• Picture symbols. Images alongside text to support meaning, not decorate the page.
• Large, clear layout. Generous spacing and type sizes that make the page approachable rather than intimidating.

Done by hand, this work is slow. A single policy can take days to convert well, which is why so many organisations produce one or two flagship Easy Read documents and quietly leave the rest of their communications untouched. That is where tools like askVERA change the economics: it converts complex documents from PDF, Word, a URL or pasted text into Easy Read drafts, with a built-in, auto-tagged image library, while a human reviewer stays in control of every page before anything is published.

The legal footing: Equality Act 2010 and the PSED

Accessibility is not only an ethical position. Under the Equality Act 2010, organisations must make reasonable adjustments so that disabled people are not placed at a substantial disadvantage. Public bodies carry the additional weight of the Public Sector Equality Duty, which requires them to have due regard to the need to advance equality of opportunity in everything they do, including how they communicate.

Information that only some people can access is exactly the kind of disadvantage these duties were written to address. When a council publishes a service change in language its residents with learning disabilities cannot follow, or an NHS body issues appointment instructions a patient cannot decode, the disadvantage is real and measurable: missed appointments, unclaimed entitlements, complaints and appeals that could have been avoided. Document simplification for accessibility is one of the most direct, evidenceable ways to meet these obligations.

A worked example: one letter, two outcomes

Take a housing association writing to residents about a change in repair reporting. The standard letter runs to three paragraphs of procedural language: “with effect from”, “the aforementioned service”, “in the event that”. Some residents read it, many skim it, and the residents who most depend on the repairs service understand none of it. The first they know of the change is a repair request that goes nowhere.

Now run the same letter through an Easy Read conversion. The output says, in short sentences with supporting images: the repairs phone number is changing, here is the new number, this starts on this date, here is who to ask for help. A reviewer checks the draft, adjusts one sentence, confirms the images fit, and checks the compliance score against the EU Easy Read Guidelines before sending. The message is the same. The number of residents who can act on it is not.

Keeping humans in control of meaning

Simplification carries a risk worth naming: strip out the wrong words and you change what a document means. A care plan that loses a condition, or a consent form that loses a caveat, is worse than a complicated one. That is why review and edit sits at the centre of askVERA’s five-step process. The AI produces the draft; a person who understands the content approves it, edits it or rejects it. Every document also receives a compliance score against the EU Easy Read Guidelines, with 80% or above indicating a good standard, so quality is measured rather than assumed.

This matters for teams accountable for what goes out of the door. An EDI lead can show not just that documents were simplified, but that each one was reviewed by a person and scored against a recognised standard. It also protects the people doing the reviewing: instead of building each Easy Read page from a blank template, they are checking and refining a structured draft, which is faster, less error-prone and far easier to sustain across a busy team.

Language support is developing too. askVERA offers multiple languages in beta, which matters for organisations whose communities include readers working in a language other than English as well as readers who need simplified structure.

Where to start without boiling the ocean

Most organisations do not need every document in Easy Read on day one. A practical starting order:

1. Decisions about the person. Care plans, assessments, tenancy changes, anything the reader is asked to agree to.
2. Instructions the reader must act on. Appointment letters, service changes, deadlines.
3. Rights and complaints information. If someone cannot understand how to complain, the complaints process does not really exist for them.
4. Everything else, prioritised by audience and volume.

The same starting order works across sectors, even though the documents differ: local councils meeting the Public Sector Equality Duty, NHS teams communicating with patients, charities and care providers, schools supporting SEND pupils, and legal and HR teams making policies genuinely readable.

Entry costs are modest: askVERA’s personal pricing starts from £10 per document, falling to £7.50 per document at volume, with Teams plans from £2,200 to £5,000 per year for organisations producing accessible content regularly. There is a free trial with no credit card required, which makes it straightforward to test the approach on one real document before committing to anything.

Accessibility as an outcome, not a format

It is easy to treat Easy Read as a compliance artefact: produce the accessible version, publish it, tick the box. The organisations that get real value think in outcomes instead. Fewer missed appointments. Fewer complaints rooted in misunderstanding. More residents, patients and service users making informed choices. Those outcomes only arrive when simplified documents are accurate, reviewed and produced consistently rather than occasionally, which is precisely what pairing AI conversion with human oversight makes affordable. It is the same principle that runs through the wider askelie platform: AI does the heavy lifting, people keep control of what matters.

Related reading

• AskVERA Accessability for Local Government
• Governed AI for Public Sector UK Accessibility
• askVERA: Systematic Automated Easy Read Production