Blog · Workflows
Reading X (Twitter) with dyslexia
X, still Twitter to most of the people who read it, is built for a kind of reading that dyslexia makes expensive - hundreds of short, unconnected bursts of text scrolling past at speed, each in a different voice, half of them shouting. The typography itself is fine. The problem is the firehose, the small type, and the fact that the app gives you almost no control over either. This is the setup that makes the timeline something you can actually sit with.
Why X is hard before you change anything
Most reading on the web is one long thing - an article, a thread, a document. X is the opposite: it is a thousand tiny things, stacked. For a dyslexic reader that structure is uniquely tiring, because every post is a fresh start. There is no running context to coast on, no paragraph rhythm to settle into. You decode the first few words of a post, decide in a fraction of a second whether to keep going, and then do it again, and again, for as long as you scroll. The cost of that constant cold-starting is what makes ten minutes on X feel like an hour of real reading.
Three of X's defaults make it worse. The first is the type size. X sets its body text fairly small, and the custom typeface it uses (called Chirp) is a tight, modern sans that looks crisp in screenshots and crowds together in a live timeline. The second is the "For you" tab. By default X opens to an algorithmic feed that mixes accounts you follow with recommended posts, paid promotions, and replies from strangers - a stream with no stable rhythm, where the visual texture changes every few posts. The third is media density. Images, quote-posts, embedded videos and link cards break the column into uneven blocks, so your eye never learns where the next line of text will begin.
None of this is fixable inside X's own settings alone. But a short list of changes - some inside X, one outside it - turns the timeline from a thing that ambushes you into a thing you control.
The five-minute setup
Step 1: in Settings, open Display and push the font-size slider up a notch or two, and switch the theme to Dim or Lights out.
Step 2: read the Following tab, not For you - and set it as your default if your app version allows.
Step 3: install a font-override extension and set a dyslexia font for the site.
Step 4: build a List or two of the accounts you actually read, and treat those as your real feed.
That is the floor. The rest of this article is what each choice is doing, and where it falls short.
Step 1 - the two settings X does give you
X hides a surprising amount of control in one place. On the web, click More in the left sidebar, then Settings and privacy, then Accessibility, display and languages, then Display. On mobile the same screen lives under your profile menu. Two controls there matter.
The font size slider bumps the body text up in five steps. Most dyslexic readers are comfortable a notch or two above the default; the timeline gets shorter per screen, which is the point, because fewer posts competing for attention at once is calmer, not less productive. The background control offers three themes: Default (white), Dim (a dark navy) and Lights out (true black). For reading bursts of text against a constant stream of bright images, a dark theme reduces the glare-then-text-then-glare flicker that triggers visual stress in many adult dyslexic readers. We went into why in does inverted contrast actually help; on X specifically, Dim is the pick for most people, because true black against bright media can produce its own halation. If you prefer a warm tinted background to grey, X cannot do that - you will need a browser-level tint, which we cover in Irlen syndrome and tinted overlays.
What this screen will not do is change the font itself. You can make Chirp bigger; you cannot make it OpenDyslexic. For that you have to go outside X.
Step 2 - the font swap X will not do for you
This is the change that does the most work. X gives you no way to replace its typeface, so the only route to a dyslexia font is a font-override extension that rewrites the page after X has rendered it.
Install LexiFont, pick your font, and reload X. Every post body, reply, display name, sidebar link and trending entry swaps together. Because the override happens at the rendering layer, it does not matter that X has no font option of its own - your choice wins.
For X specifically, the strongest pick is usually Atkinson Hyperlegible. The reasoning is the same one that applies to Reddit: the site is short-form reading repeated hundreds of times, where the whole game is telling one character or word apart from a similar one at a glance, and where the cost of misreading is a misunderstood post rather than a lost sentence. Atkinson was drawn for exactly that kind of signal discrimination. For the rare long-form thread you settle into, Lexend's wider spacing can feel better; we put the two side by side in Lexend vs Atkinson Hyperlegible. On the timeline, Atkinson is the safer default.
The difference looks small on a single post. Multiply it by the few hundred posts you scan in a session and it is the difference between a feed you can read and a feed you skim until your eyes give out.
Step 3 - read Following, not For you
The single biggest comfort decision on X is which tab you read. At the top of the timeline there are two: For you, the algorithmic feed, and Following, a reverse-chronological list of only the accounts you actually follow. Tap Following.
The reason is rhythm. The For you feed is engineered to surprise you - it injects recommended posts, replies between strangers, and promoted content between the accounts you chose, and it reorders everything by predicted engagement rather than time. For a dyslexic reader that unpredictability is the enemy, because there is no stable pattern to scan against; every screen is a fresh layout problem. The Following feed is plain chronology. The same accounts, in the order they posted, every time. It is quieter, it is finite, and it does not fight you. Some app versions let you set Following as the default tab so X stops dropping you back into the algorithm; if yours does, do it. If it does not, the habit of swiping or clicking to Following each time you open the app is worth building.
Step 4 - Lists are your real feed
Even a chronological Following feed can be too much if you follow more than a couple of hundred accounts. The fix is Lists - X's most underused feature and, for a dyslexic reader, its most valuable. A List is a hand-picked group of accounts that you read as its own clean, chronological feed, separate from everything else.
Make one called something like "Read every day" and add only the ten or twenty accounts you genuinely want to keep up with. Pin it (there is a pin icon on the List) and it appears as a tab across the top of your home screen. Reading that List instead of the main timeline gives you the same thing a Multireddit gives a Reddit reader: a small, stable, predictable stream with a consistent visual texture, no ads, no recommendations, and a clear end. You can build a second List for a different topic and switch between them deliberately, rather than letting one chaotic feed mix everything together. This is the change that does the most for attention, the way the font swap does the most for the eyes.
Step 5 - quieting the noise
A few smaller settings compound. Mute words (Settings, then Privacy and safety, then Mute and block, then Muted words) lets you strip whole topics out of your timeline - a hashtag that is having a bad week, a piece of slang attached to a pile-on, the name of a show you have not watched yet. Every muted word is one fewer cold-start your eyes have to make. Turn off autoplay for videos on the same Accessibility screen as the font size; motion in your peripheral vision while you are decoding text is a steady, low-level tax on concentration, and it matters more for readers who already lose their place easily - a problem we looked at in why some readers lose their place. And use Bookmarks: when a long thread scrolls past and you do not have the energy for it right now, bookmark it rather than half-reading it in the feed. Long things deserve a calm surface, not the firehose.
Step 6 - long threads and the Reader Mode question
X is mostly short, but its longest content - the numbered mega-thread, and the long-form Articles that paid accounts can now publish - is genuinely long-form reading wearing a timeline costume. The trouble is that a fifteen-post thread is shown as fifteen separate cards with avatars, timestamps and engagement buttons between each one, so the actual prose is broken into fragments separated by clutter.
Two things help. First, click into the thread (tap the first post) so it opens as a single conversation column rather than scattered through your feed; your font override still applies, so you get the whole thread in your dyslexia font on one surface. Second, be realistic about Reader Mode. On most sites, Chrome's Reading Mode is the cleanest way to read long content, and we compared it with dedicated tools in reader mode vs reading extensions. On X it is unreliable, because the site is a single-page app that Reader Mode often cannot parse into an article. So on X the realistic long-read setup is the font override plus the opened-thread view, not Reader Mode. For anything truly long, copying the text into a clean document and reading it there is still the most comfortable option.
Step 7 - the mobile app problem
The official X app, on both iOS and Android, is the hardest reading surface on the platform, for the same reason the Reddit and Slack apps are: there is no way to install a font-override extension inside a native app, so you are stuck with Chirp. The font-size slider and the dark themes are there, which helps, but the font swap that does the most work is simply unavailable.
The fix is to read X on your phone in the browser, not the app. Open Chrome (Android) or Safari (iOS), sign in to x.com, and add it to your home screen so it opens like an app. On Android, your browser-level font extension then applies; on iOS the options are narrower, but the larger system text and a browser tint still help. The broader phone setup - the system accessibility settings that apply everywhere, not just in X - is in reading on mobile with dyslexia. If you only ever read X on your phone, switching from the app to the browser is the highest-value change on this whole page.
The Pro question
The free tier of LexiFont covers OpenDyslexic and the global font override, which is most of what X needs - the timeline, replies, names and sidebar all swap together and the comfort jump is real. The case for LexiFont Pro (a one-time $14.99) is the wider palette, and on X that means Atkinson Hyperlegible specifically. Because the platform is dominated by short, fast bursts where telling characters apart matters more than long-form rhythm, Atkinson is the font that suits it best. If X is a daily habit for you, Pro pays for itself on that one typeface; if you drop in occasionally, the free tier is plenty.
The shorter version
Push the font-size slider up and set the theme to Dim in X's Display settings. Read the Following tab, never For you, and set it as default if you can. Install LexiFont and set Atkinson Hyperlegible as the site font. Build a short List of the accounts you actually read and treat that as your real feed. Mute the words that are having a bad week, turn off video autoplay, and bookmark long threads instead of half-reading them. On your phone, use the browser at x.com, not the app.
Most dyslexic X users have one or two of these set right. The font swap and the Following tab together are what change the day.
Get LexiFont Pro - OpenDyslexic, Lexend, Atkinson Hyperlegible and Comic Neue for $14.99 one-time