Blog · Practical Guides
Reading Financial Documents with Dyslexia
Bank statements, tax returns, and insurance policies are some of the hardest documents most adults will ever have to read. For dyslexic readers, the usual problems - letter confusion, losing your place in dense text, number transposition - interact badly with what financial documents actually look like: six-point footnote type, columns of figures that scroll off the screen, and pages of identical-looking legal clauses. Getting these documents wrong has real consequences. This is a guide to doing them better.
Why financial documents are particularly hard
General reading difficulty with dyslexia is well understood. What makes financial reading a specific problem is the combination of document design choices that have been optimised for legal completeness, not for comprehension.
Consider a typical monthly bank statement: transactions are listed in a table with six or seven columns, dates written as DD/MM/YYYY (easy to transpose), merchant names that are often abbreviated or in capitals, and amounts printed in a small serif font chosen for print density rather than screen legibility. That same statement, online, is frequently rendered in the bank's own UI typeface at around 12-13px - and the bank has no obligation to let you change it.
Tax forms compound the problem. Form fields are numbered, cross-referenced, and sometimes carry the same number with a different letter suffix (line 22a, line 22b, line 22c). Instructions typically appear in a separate document, which means you are constantly switching between two large bodies of dense text. Missing a line or transposing a figure has financial and legal consequences that generic reading errors usually do not.
Insurance documents and mortgage agreements add a third layer: long paragraphs with minimal visual structure, buried exclusion clauses, and defined terms that look like ordinary English but mean something narrower. Missing "subject to clause 14(b)" in a block of text can be costly.
The solution is not to develop superhuman focus. It is to change the reading environment so it works with the way your brain processes text, not against it.
Start with the online portal, not the PDF
If you have a choice between reading your bank statement as a downloaded PDF and reading it on your bank's website, start with the website. PDFs are notoriously resistant to intervention - you cannot easily override their fonts, the text is often not reflowable, and zoom behaves differently between PDF viewers. Online portals, by contrast, are live HTML, and that means a font override tool like LexiFont can apply your preferred typeface directly to the text.
LexiFont works on banking portals the same way it works on any other website. If you find your bank's default font hard to parse, open the extension, pick Lexend or Atkinson Hyperlegible, and the transaction table and account summary will re-render in your chosen typeface. This does not change any underlying data - it is a purely visual override in your browser.
Which font works best for financial documents? Most readers doing detailed numerical work find that a clean, upright, wider-spaced sans-serif reduces errors. Atkinson Hyperlegible is designed specifically for legibility at small sizes, and its wide apertures make 0/O and 1/l distinction easy - both common confusion points in account numbers and figures. Lexend is slightly more comfortable for long blocks of text. Either is a significant improvement over a proprietary bank UI font. LexiFont Pro gives you both, plus the ability to set a per-site default so the override applies automatically each time you log in.
Dealing with PDFs when you cannot avoid them
Tax returns and insurance policies are frequently only available as PDFs, and a PDF opened in Chrome behaves differently from a normal web page. The key move here is to get the text out of the PDF and into a format you can control.
The most reliable approach is to copy the text out of the PDF (Ctrl+A, Ctrl+C works in most tagged PDFs in Chrome's built-in viewer) and paste it into a text editor or Google Docs where you can set your own font, size, and line spacing. For tax instructions, paste one section at a time - trying to paste an entire 50-page document and then read it linearly tends to recreate the same problem you started with.
If the PDF is a scanned image rather than genuine text - older insurance documents and paper-filed tax returns sometimes are - you will not be able to copy the text directly. Google Docs has a built-in OCR function: File > Open > Upload the PDF, and Google will convert it to editable text. The output is imperfect on complex tables but usually good enough on body paragraphs to be readable in a font you can control.
For tax-specific documents, the government filing portal (HMRC's Personal Tax Account in the UK, the IRS's Online Account in the US, or similar national equivalents) is nearly always better than the paper form PDF. These portals are live HTML and respond to font overrides. They also tend to break the filing process into sections rather than presenting fifty lines simultaneously.
Number transposition: the specific risk
Dyslexia does not directly cause number transposition - it is not a maths disorder - but the same phonological processing patterns that make letter sequences hard to track can make digit sequences harder too, and the eye-tracking patterns that cause readers to lose their place on a line apply equally to rows of figures. The consequence in financial documents is specific: transposing two digits in an account number, or reading £1,340 as £1,430, is the kind of error that has practical consequences.
A few concrete strategies reduce this risk:
Verify account numbers digit by digit, not as a chunk. Rather than reading "12345678" as a single object, split it: "12 - 34 - 56 - 78" and compare each pair against the reference. Banks typically group sort codes and account numbers in pairs or triplets for exactly this reason; if the grouping has been stripped in a document, re-add it yourself before comparing.
Read amounts aloud, then in reverse order. If you read a figure aloud and then verify it by reading the digits from right to left, transposition errors that your brain autocorrected the first time become obvious the second time.
Increase zoom on transaction tables. Browser zoom (Ctrl+ on Windows/Linux, Cmd+ on Mac) applied to an online portal at 125-140% makes digit groups significantly easier to distinguish. Browser zoom on HTML content generally works well; just be aware that some banking portals have fixed-width layouts that break at high zoom levels, forcing horizontal scrolling. If that happens, the font-size-only approach - available in Firefox's View menu, or achievable via LexiFont's font size control - scales text without breaking the layout.
Online portals: what you can actually change
Not all banking portals are equally resistant to customisation. A few practical options most readers do not know about:
Download statements as CSV, not PDF. Most online banks allow you to export transactions as a CSV spreadsheet. Opened in Excel or Google Sheets, you can apply your own font, adjust column widths, and use row colouring to track your place - the kind of formatting that helps significantly with financial spreadsheets. The CSV format also makes it trivial to search for a specific transaction or merchant without scrolling through a visual list.
Use your browser's reader mode on information pages. Reader mode (available in Firefox, Safari, and via extensions in Chrome) strips navigation, ads, and decorative elements from pages, giving you a clean, reflowable text column. It works poorly on tables and transaction lists - which need their structure - but very well on the explanatory text of bank websites, tax guidance pages, and insurance policy summaries. Reader mode vs reading extensions covers when each approach is more useful.
Text-to-speech for legal clauses. Long contractual paragraphs - the kind buried in mortgage agreements or credit card terms - are often easier to process via text-to-speech than visual reading. Hearing a clause read aloud while your eyes track the text uses a different channel to confirm the same meaning, and errors that slip through visual reading often become obvious in audio. Chrome's built-in "Listen to this page" feature (available from the right-click context menu in recent versions) or a dedicated extension both work. Be aware that TTS rendering of financial tables is poor - it reads every cell in sequence, which becomes incomprehensible quickly. Use TTS for prose, visual reading for tables.
A practical workflow for tax season
Tax filing is where the stakes are highest and the documents are densest. The following workflow is not the fastest approach - it is the one that minimises errors.
Step 1. Gather all source documents (employer statements, bank interest summaries, investment income) and convert any scanned PDFs to text using Google Docs OCR before doing anything else.
Step 2. Read through the filing instructions once in your accessible format (browser with font override, or pasted into Docs) before looking at a single form field. Know the structure before you start filling.
Step 3. Fill one section at a time. Close any documents not relevant to that section. Use the government's online filing portal where available - it enforces one-section-at-a-time and prevents you from seeing fifty lines at once.
Step 4. Before submitting, use the text-to-speech approach for any figure you entered that you are not certain about. Hear it back before committing.
Step 5. If you can, have a trusted person verify the figures (not the prose). You have likely read the instructions correctly - the risk is in the numbers.
What banks and financial services get wrong
The dyslexia-accessibility problem in financial documents is partly a product of how financial services are regulated. Regulators require specific disclosures in specific language, which gives institutions little flexibility to simplify prose even when they want to. Font choice, type size, and column layout are treated as design decisions rather than accessibility ones, and accessibility obligations for financial services typically focus on screen-reader compatibility for blind users rather than on the readable-text needs of dyslexic users.
This is changing slowly. The UK's Financial Conduct Authority has published guidance noting that financial promotions should be "fair, clear and not misleading" - a standard that, properly applied, would prohibit sub-12pt type in key risk disclosures. The US Consumer Financial Protection Bureau has published readability guidelines for consumer finance disclosures. But enforcement is inconsistent, and the practical reality is that most banks are not going to redesign their statements for dyslexic users without external pressure.
In the meantime, the most effective path is to move as much of your financial reading as possible to live HTML portals you can customise, download transaction data in CSV format, and use font-override tools to apply a typeface your visual system can process comfortably. The documents will not change to suit you, but the format in which you read them can.
When it is worth getting help
Some financial documents are simply too consequential to read under adverse conditions. A mortgage agreement, a significant investment contract, or a complex tax situation with meaningful liabilities falls into this category. Many dyslexic adults are reluctant to involve a professional or a trusted person because they feel they should be able to manage their own finances independently - and they are right that they can, with the right tools. But asking an accountant to walk you through a tax return verbally, or asking a solicitor to summarise the key clauses of a mortgage, or asking a family member to verify figures with you, is not an accommodation for incompetence. It is the kind of double-checking that most financial professionals apply to their own work regardless of reading differences.
If you are dealing with significant financial difficulty or legal action arising from a financial dispute, most countries have free advice services - Citizens Advice in the UK, free tax clinics in the US and Canada, legal aid services elsewhere - that can help you understand documents you are struggling with. These services exist precisely because financial documents are difficult even for fluent readers.
Quick setup checklist
- Install LexiFont and apply Atkinson Hyperlegible or Lexend when reading bank and tax portals.
- Configure LexiFont Pro per-site defaults so your preferred font applies automatically each time you log in to your bank.
- When a statement is PDF-only, try the bank's online portal first; if unavailable, use CSV export if the bank offers it.
- For tax forms: use the government's online filing portal rather than the printable PDF where possible.
- Use browser zoom at 125-140% for transaction tables.
- Use text-to-speech for long legal prose; return to visual reading for tables and figures.
- Verify account numbers and amounts in pairs or triplets; read figures aloud then check right-to-left.
None of this requires you to be comfortable with financial jargon from the start. It requires a browser, a font-override tool, and a method. The documents are hard. The environment in which you read them does not have to be.
Get LexiFont Pro - set per-site font defaults for every bank and portal you use
Further reading
- Dyslexia-friendly PDF reading in Chrome - what works and what doesn't
- Reading spreadsheets with dyslexia - fonts, row colouring, and zoom
- Dyslexia and browser zoom - is bigger text always better?
- Reader mode vs reading extensions for dyslexia
- Reading legal documents with dyslexia - contracts, terms, and fine print