Accessible Fonts: Readable Text and Adaptable Layouts

A search for an accessible font should begin with the people and content involved. Compare actual paragraphs, labels and numerals at the intended size, including characters that can be confused. Give readers a way to use their own preferences where the platform permits. W3C guidance emphasizes adaptable text presentation and spacing; choosing a particular family name does not demonstrate that a finished page meets those requirements.

W3C’s explanation of WCAG text spacing concerns whether content survives user overrides. Its baseline adjustments include line height of 1.5 times the font size, paragraph spacing of twice the font size, letter spacing of 0.12 times and word spacing of 0.16 times. These are override tests, not a requirement to make all default typography use those exact values. Relevant exceptions apply where a language or script does not use a particular property.

Increased spacing or a wider chosen font can expose problems in rigid boxes. Review headings, navigation, buttons and form labels for clipping, overlap and missing text. Allow content to wrap where appropriate and keep controls usable after the adjustment. Test long labels and error messages, not just short examples. The same font can be easy to use in a flexible paragraph and difficult to read in a cramped fixed-height control.

W3C’s separate Visual Presentation criterion addresses additional controls over blocks of text and is identified as Level AAA. Do not mix that level with the Level AA text-spacing criterion or claim that a font alone satisfies either. Record which presentation behavior was checked and with what content. For decorative character substitutions, read the Unicode text guide before treating visual similarity as equivalent text.