Readability and Language
Typography Fundamentals
Course 1 · Chapter 7 · Readability and Language
In Typography Fundamentals 6 you got a typeface onto the reader's screen, with a sensible fallback if the file arrived late. But "it appears" is not the same as "it can be read". Some of your readers have tired eyes, small phones, dim rooms, dyslexia or low vision. Others read in a language your first font never planned for. This chapter is about making type work for the widest range of people: enough contrast, sizes that respect the reader, and fonts that actually contain the letters a text needs.
Contrast: Can the Text Be Seen?
The most common readability failure on the web is not an odd typeface; it is pale grey text on a white background. Contrast is the difference in brightness between text and its background, and the Web Content Accessibility Guidelines (WCAG) turn it into a number: the contrast ratio, written like 4.5:1. It runs from 1:1 (identical colours, invisible text) to 21:1 (black on white).
| Text kind | Minimum ratio (level AA) | Higher target (level AAA) |
|---|---|---|
| Body text | 4.5:1 | 7:1 |
| Large text (roughly 24px, or 19px bold; check the exact definition) | 3:1 | 4.5:1 |
| Icons and interface outlines | 3:1 | (no separate target; check) |
Calculating a Ratio Yourself
The formula looks scary but is short: convert each colour's red, green and blue values to a "relative luminance" (how bright the eye perceives it, with green counting most), then divide the brighter by the darker, each with a small offset added. This script does exactly that for a handful of colour pairs.
Notice that #999999, a grey many designers reach for because it "looks subtle", fails even the large-text threshold. And notice the dark-theme row: this course's own page colours pass comfortably. Light-on-dark text can be perfectly readable, though very bright white on pure black can shimmer for some readers, which is why many dark themes use a soft off-white (check).
Dark grey on white reads comfortably, even in a bright room.
Mid grey on white looks tidy but tires the eye, and vanishes in sunlight.
Live text with fixed colours, so you can judge the difference on your own screen.
Choices That Help Readers with Dyslexia or Low Vision
People read differently, and no single setting suits everyone. Research on "dyslexia-friendly" fonts has been mixed, and claims that one special typeface fixes reading difficulty should be treated with caution (check current studies). What does have wide agreement is that a handful of ordinary choices help many readers at no cost to anyone else:
| Choice | Why it helps | In practice |
|---|---|---|
| Clear letter shapes | Letters like I, l and 1, or b and d, are easily confused if the design makes them near-identical | Look at a sample of your typeface with those characters side by side |
| Generous spacing | Crowded letters and lines blur together | Line-height around 1.5 and a little extra word spacing for long text (check ranges) |
| Left-aligned, ragged-right text | Justified text can open uneven "rivers" of white space | text-align: left for body copy |
| Sturdy weight | Hairlines fade for low-vision readers | Regular or medium for body text |
| Avoid long italic and all-caps passages | Both slow down reading | Keep them to short emphasis (Typography Fundamentals 4) |
| Short, plain paragraphs | Gives the eye regular places to rest | Break long blocks up with subheads |
Size and Zoom
Typography Fundamentals 6 recommended rem for text. Here is the accessibility reason. If the reader raises their browser's default font size, rem and em values grow with it, while fixed px text may ignore the setting (check how your target browsers behave). Page zoom is the other tool: pressing Ctrl and plus should enlarge everything, up to 200% and beyond, without hiding or cutting off any content.
A useful test: zoom your page to 200%, then resize the window to phone width. Does any line need sideways scrolling? Is anything overlapping? If so, a fixed-width layout is working against the reader.
Line Length on Small Screens
Typography Fundamentals 3 gave you a comfortable measure of roughly 45 to 75 characters. On a phone the screen is narrow, so lines can become too short: with large text at 200% zoom you may see only 20 or 25 characters per line, which makes the eye jump back constantly and leaves words hyphenated or broken awkwardly. The remedy is not to shrink the type but to let the column fill the width with sensible margins, and use a max-width in ch units so that on wide screens the lines do not become too long.
Diacritics: The Marks Above and Below
So far the chapter has assumed readers can see your letters. The other half is making sure they can see the right letters. Many languages add marks, called diacritics, to a base letter: the acute in é, the tilde in ñ, the cedilla in ç, the double acute in the Hungarian ő. These marks change the meaning and the pronunciation, so they are not decoration: dropping them can turn one word into another.
Good typography treats a letter with a mark as a designed character, not a letter with a mark stuck on. Marks need room, which affects line-height (tall capitals with accents can collide with the line above if leading is too tight, as seen in Typography Fundamentals 3), and the mark's position should be refined for each base letter. Inside the computer, text is stored as numbered code points from the Unicode standard, and a character with a mark can be stored in two ways. This script shows both.
UnicodeEncodeError. The fix was to print only the code point and the name. The takeaway applies to the web too: a character is only as visible as the whole chain behind it (file encoding, console or page encoding, and font) allows. On a web page, declare UTF-8 with <meta charset="utf-8"> so the browser reads the characters correctly.
Non-Latin Scripts and Why Coverage Matters
A single font file covers only the characters its designer drew. The set of characters a font includes is its coverage, and it is not the same for every font. Many popular fonts cover the basic Latin alphabet plus the accents of Western European languages, then stop. Central European languages, Greek, Cyrillic, Arabic, Hebrew, the scripts of India, and Chinese, Japanese and Korean each need their own glyphs, and each script has its own typographic traditions.
| Script family | A typographic point worth knowing |
|---|---|
| Latin with diacritics | Needs accent-aware spacing; check that a font includes the extended Latin range for languages such as Polish, Hungarian and Turkish |
| Cyrillic and Greek | Have their own capitals, lower-case forms and italic traditions; not every Latin font includes them |
| Arabic and Hebrew | Read right to left; Arabic letters change shape depending on their position in a word, and the text flows in the opposite direction to the page's usual layout |
| Chinese, Japanese, Korean | Thousands of characters; fonts are very large, so subsetting and web delivery need special care (check) |
| Indic scripts (Devanagari and others) | Letters combine into joined forms, so the font and the browser together must apply the right substitutions (check specifics per script) |
When a font lacks a character, the browser does not stop. It quietly borrows the character from the next font in the fallback stack, and, failing that, from another font on the system, or shows an empty box (often called "tofu"). The text is technically displayed, but with mismatched shapes and sizes in the middle of a word. This is why Typography Fundamentals 6 stressed fallback stacks and why subsetting is risky: if you strip a font down to English-only glyphs and a reader's name contains an accented letter, that one character will look wrong. This script checks coverage the way you might audit a font before choosing it.
The Hungarian line is the sneaky one: the sample sentence is mostly fine, because ö and ó live in the Western European range, but ű is missing. A designer who tested a font only on French and Spanish would never notice. Always test a font with the real text of every language you serve.
Telling the Browser the Language
Browsers and assistive software need to know which language a page, or a stretch of it, is written in. The lang attribute does this, and it affects hyphenation, quotation marks, which regional variant of a character is drawn (check; some scripts share characters between languages but draw them differently) and what a screen reader pronounces.
| Idea in this chapter | An idea you may already know |
|---|---|
| Contrast ratio | A signal-to-noise ratio: how far the text stands above the background |
Relative units (rem) | Responsive design: values that adapt instead of being fixed |
| Unicode normalisation | Comparing strings after trimming and lower-casing them |
| Font coverage | A library that supports only some of the locales your users need |
The lang attribute | A locale setting: it changes behaviour without changing the text |
user-scalable=no; a pixel-locked layout that breaks at 200% zoom; justified text in narrow columns; subsetting a font until names with accents break; testing only with English; forgetting lang and charset; and assuming a "dyslexia font" replaces good spacing, sizing and contrast.
Hands-On Exercises
Three exercises: a written accessibility review of a flawed page, a code task that audits a stylesheet's colours, and a CSS task that builds a flexible, language-aware text style. Each has a solution file that opens in a new tab.
A local library's event page uses light grey (#aaaaaa) 12px text on white, justified paragraphs about 120 characters wide, all-caps italic for every event description, blocks pinch-zoom with a viewport setting, and shows a red word for "sold out" with no other cue. On paper, write a review: list each problem, say who it affects and why, and give a specific fix for each (with numbers where you can). Finish by naming the three fixes you would make first and the reason for that order.
📄 View solutionWrite a Python script that holds a list of text and background colour pairs for a website (at least six, including headings, body text, links and a footer), calculates the WCAG contrast ratio for each, and prints a table showing the ratio, a pass/fail for body text (4.5:1) and for large text (3:1). For each failing pair, suggest a darker text colour by darkening the text step by step until it passes, and print the colour that works. Run it and show the output.
📄 View solutionWrite the CSS and the small HTML skeleton for a multilingual article page. Include the language declarations, a body style in rem that respects the reader's settings, a column capped in ch units that still fits a phone at 200% zoom, a fallback stack for Latin text, a different font stack for Japanese and for Arabic passages chosen with :lang(), right-to-left handling, and a prefers-reduced-motion rule. Add a comment on each part explaining its job.
Chapter 7 Quick Reference
- Contrast ratio runs from 1:1 to 21:1; aim for at least 4.5:1 for body text and 3:1 for large text (check the current guidelines)
- Mid grey on white fails: #999999 on white measures 2.85:1; #595959 measures 7:1
- Helpful for many readers: clear letter shapes, generous spacing, left-aligned body text, sturdy weights, short paragraphs; no single "dyslexia font" is a cure (check studies)
- Respect the reader: size in
rem, never block zoom, test at 200% and at phone width - Cap the measure with
max-widthinch, with padding for small screens - Diacritics are letters, not decoration; Unicode can store them as one code point or as a base plus a combining mark, and normalisation makes them comparable
- Coverage: a font draws only the characters it includes; missing ones fall back to another font or show as boxes; test with real text in every language you serve
- Declare language and encoding:
lang,dirand<meta charset="utf-8">