惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Spread Privacy
Spread Privacy
V
Visual Studio Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Recorded Future
Recorded Future
云风的 BLOG
云风的 BLOG
Microsoft Azure Blog
Microsoft Azure Blog
I
InfoQ
Apple Machine Learning Research
Apple Machine Learning Research
MyScale Blog
MyScale Blog
M
MIT News - Artificial intelligence
WordPress大学
WordPress大学
Recent Announcements
Recent Announcements
V
V2EX
The GitHub Blog
The GitHub Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Jina AI
Jina AI
小众软件
小众软件
aimingoo的专栏
aimingoo的专栏
V
Vulnerabilities – Threatpost
C
Check Point Blog
C
Cyber Attacks, Cyber Crime and Cyber Security
AI
AI
宝玉的分享
宝玉的分享
P
Proofpoint News Feed
量子位
Attack and Defense Labs
Attack and Defense Labs
H
Hackread – Cybersecurity News, Data Breaches, AI and More
P
Privacy International News Feed
Google DeepMind News
Google DeepMind News
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
C
CERT Recently Published Vulnerability Notes
腾讯CDC
Latest news
Latest news
Google DeepMind News
Google DeepMind News
The Register - Security
The Register - Security
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
G
GRAHAM CLULEY
Blog — PlanetScale
Blog — PlanetScale
博客园_首页
美团技术团队
The Cloudflare Blog
T
Tenable Blog
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
J
Java Code Geeks
SecWiki News
SecWiki News
Webroot Blog
Webroot Blog
N
News | PayPal Newsroom
博客园 - 叶小钗
博客园 - Franky

TetraLogical Blog

Designing for people who are D/deaf - TetraLogical Designing accessible documents - TetraLogical Introduction to creating accessible documents - TetraLogical Inclusive user research: vulnerable people - TetraLogical Designing for people who are blind - TetraLogical Designing for people with low vision - TetraLogical Meet the team: Niamh Madden - TetraLogical Designing for people with anxiety - TetraLogical Designing for people with disabilities - TetraLogical Accessible building blocks for the web videos - TetraLogical Common accessibility misconceptions - TetraLogical Common misconceptions about testing accessibility - TetraLogical Common misconceptions about implementing accessibility - TetraLogical Common misconceptions about WCAG - TetraLogical Common misconceptions about disability - TetraLogical Meet the team: Grace Snow - TetraLogical Sustainable accessibility in complex organisations: strategic foundations - TetraLogical Sustainable accessibility in complex organisations: organisational realities - TetraLogical Sustainable accessibility in complex organisations: external factors - TetraLogical Common misconceptions about screen readers - TetraLogical Guide to the Inclusive Design Principles - TetraLogical Meet the team: Ian Lloyd - TetraLogical Annotating designs using common language - TetraLogical Meet the team: Catriona Morrison - TetraLogical Championing inclusive language - TetraLogical Press release: TetraLogical launches accessible self-led training courses to help digital teams build confidence in accessibility - TetraLogical Why inclusive products are green products - TetraLogical Accessible Recruitment - TetraLogical Accessibility and the agentic web - TetraLogical Meet the team: Craig Abbott - TetraLogical Foundations: types of assistive technology and adaptive strategies - TetraLogical European Accessibility Act (EAA) FAQ - TetraLogical Screen reader HTML support tables - TetraLogical Interview with Lola Odelola - TetraLogical Understanding EN 17161 Design for All - TetraLogical Inclusive user research: building rapport - TetraLogical Foundations: Keyboard accessibility - TetraLogical Can generative AI write contextual text descriptions? - TetraLogical Understanding the European Accessibility Act (EAA) - TetraLogical Meet Josh: a sportsman who has spinal muscular atrophy - TetraLogical Meet Jonathan: a photographer who has ADHD - TetraLogical Foundations: grouping forms with `<fieldset>` and `<legend>` - TetraLogical XR Accessibility: for people with moving disabilities - TetraLogical Meet Andre: a music producer and blind screen reader user - TetraLogical Foundations: types of disability - TetraLogical Meet Lauren: a film editor who has ADHD - TetraLogical Meet Steve: a photographer who is deaf and low vision - TetraLogical Foundations: form validation and error messages - TetraLogical Meet Hasmukh: a blind cricketer and screen reader user - TetraLogical XR Accessibility: for people with hearing disabilities - TetraLogical XR Accessibility: for people with thinking disabilities - TetraLogical XR Accessibility: for people with seeing disabilities - TetraLogical Introduction to XR Accessibility - TetraLogical Foundations: labelling text fields with input and label - TetraLogical Design patterns and WCAG - TetraLogical Does WCAG 2.2 apply to native apps - TetraLogical Why are my live regions not working? - TetraLogical Building a culture of accessibility - TetraLogical When to use tabindex= Accessibility foundations - TetraLogical Meet the team: Demelza Feltham - TetraLogical Can generative AI help write accessible code? - TetraLogical Meet the team: Steve Faulkner - TetraLogical Meet the team: Gez Lemon - TetraLogical Keyboard accessibility myths and WCAG - TetraLogical Amendment to the Public Sector Accessibility Regulations - TetraLogical What Considerations for TV user interface accessibility - TetraLogical Meet the team: Alistair Duggin - TetraLogical Sticky content: focus in view - TetraLogical The only accessibility specialist in the room - TetraLogical Meet the team: Ian Pouncey - TetraLogical Meet the team: Dean Holden - TetraLogical Meeting WCAG Level AAA - TetraLogical Foundations: accessible names and descriptions - TetraLogical Inclusive XR: accessible augmented reality experiences - TetraLogical Foundations: pointer gestures - TetraLogical Meet the team: Graeme Coleman - TetraLogical Adding sign language to videos - TetraLogical Foundations: introduction to WAI-ARIA - TetraLogical Meet the team: Joe Lamyman - TetraLogical Inclusive XR: accessible 3D experiences - TetraLogical Foundations: visible focus styles - TetraLogical Foundations: target sizes - TetraLogical Meet the team: Henny Swan - TetraLogical Meet the team: Ela Gorla - TetraLogical Foundations: native versus custom components - TetraLogical Foundations: HTML semantics - TetraLogical Accessibility and supporting Internet Explorer - TetraLogical Meet the team: Felicity Miners-Jones - TetraLogical Accessibility and QR codes - TetraLogical Inclusive user research: recruiting participants - TetraLogical Research insight: accessibility of images - TetraLogical Meet the team: Léonie Watson - TetraLogical Android accessibility: roles and TalkBack - TetraLogical Accessible design systems - TetraLogical Meet the team: Patrick H. Lauke - TetraLogical Inclusive user research: analysing findings - TetraLogical How to write user stories for accessibility - TetraLogical Triaging WCAG 2.1 Level AAA - TetraLogical
Designing for people with reading disabilities - TetraLogical
2026-06-25 · via TetraLogical Blog

Posted on by Grace Snow in Design and development, User experience

Tags: Inclusive Design Principles

Design can overlook reading disabilities, but many people struggle to process written text. This post explains how to design digital content that's easier for everyone to read.

People we are designing for

Thinking: a bright pink gear connected to a smaller purple gear above it by a wavey line of orange dots. The bright pink gear slots together with a smaller purple gear on the bottom right showing a different way to make a connection.
Thinking

Reading is often treated as a binary skill — you can read or you can't. But reading exists on a broad spectrum of fluency. For many, "decoding" text —turning symbols into meaning — requires a lot of mental effort.

This can affect many people, but especially those with reading disabilities such as:

  • Dyslexia: difficulty connecting the visual shapes of letters to their sounds
  • Hyperlexia: advanced reading ability without understanding the meaning or context
  • Alexia: when a person loses their previous ability to read, usually due to a stroke or injury

Reading disabilities have nothing to do with intelligence. They are a difference in how the brain processes written information. When reading is exhausting, people have less energy for understanding and decision-making.

By designing for these needs, we make life easier for everyone. This includes people in a hurry or those reading in a second language.

Design considerations

Inclusive design goes beyond the Web Content Accessibility Guidelines (WCAG). Designing for reading disabilities is a shared responsibility between editors, copywriters, and designers. The goal is to remove the friction that makes reading feel like hard work.

Use plain language

“If you make your content easy to read, you aren’t ‘dumbing down’, you are opening up your information to anyone who wants to read it. You are making it accessible. You are trying not to exclude people based on their education, cognitive function or reading ability.”

Sarah Winters, Content Design London

We need to unlearn the academic writing style taught at school. Complex sentences create a barrier for people with reading disabilities.

Be direct. Use simple, everyday words and keep sentences short. Instead of "The implementation of the policy will commence", say "The policy starts." This makes your content open to more people.

What about technical writing?

In specialised fields like medicine or law, technical terms are often necessary. In these cases, use short paragraphs and good heading structure. If you must use a complex word, explain it simply the first time it appears. You can also provide a clear link to a glossary.

Format for flow and focus

The way text sits on a screen can affect how easily a person can find and read the next line. To help with this:

  • Align text to the left: avoid "justified" blocks of text. These create uneven gaps between words, which can be distracting
  • Keep lines short: aim for 70 to 80 characters per line at most. If a line is too long, the eye travels too far to find the start of the next line
  • Use clear headings: break your page into small sections with descriptive headings. Use sentence case for headings, for example "Design considerations", not "Design Considerations"
  • Size headings by level: text sizes should reflect the heading order. People should be able to see which sections "belong" to each other at a glance

Prioritise font features

Comparing the small x-height of Joseph Sans font to a better tall x-height in Open Sans font
Annotated x-height comparison between font families

Research shows that letter features matter more than using a specific "accessible" font. Follow these typography guidelines when you can:

  • Distinct shapes: try to choose fonts where its easy to tell letters and numbers apart, like 'l' and '1', or 'O' and 0, and where similar letters aren't exact mirrors of each other.
  • Taller x-height: look for a font where lowercase letters like 'x', 'a', and 'e' are relatively tall. This can make text easier to read at smaller sizes
  • Choose an 'open' font: look for fonts with large gaps inside letters like 'e' or 'p' and between the edges of letters like 'c' and 's'
  • Style with care: avoid large chunks of bold or italic text and don't use all-capitalised text
  • Line and letter spacing: check that lines and letters are not too close together. Use a “squint test” to see if the text is readable when blurred

Aim for a younger reading level

As mentioned in designing for people with anxiety, the average reading age for adults is often around nine to 11 years old. If your content is written at a university level, you could exclude a lot of people.

Use tools like Hemingway to test your content. If the grade level is too high, break down long sentences.

Explain acronyms and abbreviations

Acronyms and abbreviations can slow people down when reading. To minimise their impact:

  • Expand on first use: with acronyms, write the full term followed by the acronym in parentheses. For example, "Web Content Accessibility Guidelines (WCAG)"
  • Limit their use: if an acronym only appears once, you may not need it at all
  • Avoid too many acronyms together: don't crowd several acronyms into a single paragraph
  • Common abbreviations: you may not need to explain very common terms, for example, "USA"

Use images and alternative formats

Text isn't always the best way to share information.

Sometimes a well-placed diagram can explain a complex process faster than text:

A long block of text explaining the process of evaporation next to a simple image showing the same concept of ocean/sea water turning to vapour thanks to the heat of the sun above
Looking at a diagram that explains the process of evaporation may be simpler to understand than reading a block of text

Just ensure visuals have text descriptions for the benefit of people who can't see or understand images. The quality and effectiveness of a text description also affects accessibility of images, so make them clear and meaningful.

Sometimes, a video or audio-only alternative can help people with reading or other disabilities to access the information. Our post on an inclusive approach to video production can help you do this in an accessible way.

Design for low digital literacy

Reading disabilities can impact how people navigate the web in general. To support people with low digital literacy:

  • Pair text with icons: use recognisable icons to provide an extra visual cue for text labels. For example, use a magnifying glass next to a search field
  • Consistent placement: keep navigation and help links in the same place on every page
  • Descriptive link text: avoid "click here" or "read more". Use descriptive labels, for example, "download the 2024 report"

Designing for reading disabilities moves us away from assuming how people consume information. We can all help people by focusing on clear words, good structure, and better fonts. These small changes reduce reading effort and create a better experience for everyone.

Resources

Next steps

For more information about the Web Content Accessibility Guidelines, read our WCAG primer or find out more about how our assessments can help you identify issues in your websites, mobile applications, design systems, and other products and services.