Font selection and accessibility
Font choice can support accessible reading, but no font file makes a product accessible by itself. This guide separates measurable font characteristics from the implementation choices covered by WCAG.
Measured by TS 2.0
These characteristics can be tested consistently on a submitted file and appear in published requirements:
- Character coverage
- Ambiguity pairs (including I / l / 1)
- Recognition at defined rendered sizes
- Font metadata and file integrity
- Packaging and layout metrics (including x-height signals)
Browse the full catalog in Published requirements.
Selection guidance — not a certification requirement
The sections below help teams choose and deploy type. They are not themselves TS 2.0 gates. Intended reading context, display versus body use, line length, weight choice, text spacing, contrast, and human usability testing remain product decisions.
What to look for in a font file
Not every typeface was drawn for reading on screens. Faces with clear letterforms and open counters tend to hold up better at text sizes. Size, color, and contrast on the page also decide whether text is usable — those are deployment choices, not traits baked into every font file.
Files that struggle in production often share one or more of these problems:
- Shapes that are hard to tell apart (imposter I / l / 1 and similar pairs)
- Overlapping or tightly colliding characters that blur word shapes
- Decorative adornments, scripts, and handwriting styles used as text
- Specialty display faces pushed into body copy, forms, or long reading
- Extremes in weight, width, or stroke contrast that slow reading
Why fonts matter for web accessibility
Tens of millions of people in the US experience vision loss or difficulty seeing even with corrective lenses — a population that grows as people age. Reading disorders such as dyslexia also affect a large share of readers; typeface choice can change how hard text feels to process.
Accessible fonts help you serve those audiences and support an inclusive brand. They do not replace full page accessibility testing: color contrast, zoom, focus order, and semantic structure still have to work in the product that uses the font.
Where accessible fonts apply
Accessibility does not stop at the homepage. Use the same clear type system across the channels that carry your writing:
- Websites and landing pages
- Product UI and forms
- PDFs and documents
- On-screen text in video and image graphics (or provide alternatives)
Basic type terms
Understanding type anatomy helps you choose a face for its intended use. These landmarks show up again in TS metrics for x-height, vertical stability, and small-size recognition.
The quick brown fox jumps over the lazy dog.
Counters
A counter is the enclosed or partly enclosed interior of a letter. Tiny counters — especially in heavy weights — collapse at small sizes and make content harder to read.
p
a
Stroke and contrast
A stroke is any linear part of a letterform. Extreme thick-to-thin stroke contrast can make hairlines disappear in print and on screens.
t
t
Character width and font weight
Average widths and book/regular weights usually support longer reading. Ultra-condensed, ultra-extended, hairline, and black extremes slow readers down at text sizes.
Ag
Ag
Ag
Ag
Ag
Ag
Related TS signals: TS2-DEP-003Weight Count TS2-DEP-004Family signal
X-height
X-height is the height of lowercase letters relative to the point size. A taller x-height often means larger counters and stronger small-size recognition.
xoxo
xoxo
xoxo
Measured in TS: TS2-TECH-006x-height Window TS2-LAY-001x-height Consistency
The Il1 rule
Avoid fonts whose visual style makes uppercase I, lowercase l, and digit 1 look the same. Type them side by side. If you cannot tell them apart, the face is a poor fit for codes, passwords, tables, and dense UI.
Il1
Il1
Typography Standard treats this as a mandatory ambiguity gate, with related pairs for O/0, rn/m, and more.
Small-size recognition
Anatomy explains why a face may fail. Render tests show whether it fails at real UI and body sizes.
Font size and zoom
Even a strong typeface can be inaccessible if the page sets text too small, or blocks resizing. Prefer relative units (rem, em, or %) over absolute px / pt so text can scale across devices.
WCAG requires that, except for captions and images of text, users can resize text up to 200% without assistive technology and without loss of content or functionality. Neither ADA nor Section 508 names a single official minimum pixel size — usable scaling and layout matter more than one magic number.
Font color and color contrast
Do not use color as the only way to convey meaning (for example, a link that is colored but not underlined, or status that is color-only). Add another cue: underline, weight, icon, or text.
Accessibility guidelines focus on contrast ratio between text and background — not a ban on specific brand colors:
- Body / main text: at least 4.5:1
- Large text / headings: at least 3:1
- Logotypes & incidental decoration: no contrast requirement when they do not convey essential information
Sample text
Sample text
Practical checks
Selection guidance for teams — not a substitute for measuring the uploaded file against TS 2.0.
Avoid
- Avoid decorative, cursive, or novelty display faces for body copy or dense UI.
- Avoid faces where I, l, and 1 are hard to tell apart — then confirm with TS2-AMB-001.
- Avoid stacking many typefaces; keep the system small and consistent.
- Avoid long passages in all caps, or relying on color alone to convey meaning.
- Avoid locking text to absolute sizes that break browser zoom.
Prefer
- Choose faces with clear letter shapes and open counters for extended reading.
- Verify Il1 / O0 distinction on the specific file you will embed.
- Document the approved face in brand guidelines for web, email, and PDFs.
- Size text in rem/em and meet WCAG contrast on the page.
- Measure the font file with TS 2.0 when you need published evidence.
Serif or sans?
Legibility depends on clear letterforms — counters, distinction, stroke contrast, and size — not the mere presence of serifs. Research is not conclusive that sans is always better than serif for screens.
Typeface or font?
A typeface is the design system for letters. A font is a specific file or style you install or embed. Typography Standard evaluates the uploaded font file against published TS 2.0 requirements.
How TS 2.0 turns guidance into gates
Shortlists and brand guidelines help teams choose. Certification needs thresholds. Every requirement has a permanent TS2 ID, severity, and measurement method. Mandatory failures block certification even when the average score looks strong.
The catalog currently publishes 31 requirements, including 9 mandatory gates across five measurement pillars:
- Character Support — Latin, digits, punctuation, and related coverage.
- Legibility — small-size recognition and ambiguity pairs (Il1, O0, and more).
- Technical Quality — file integrity, WOFF2, glyph inventory, metadata, x-height window.
- Layout — x-height consistency and vertical metrics stability.
- Production Readiness — packaging, size, family signals, and declared license metadata.
Browse the full methodology catalog · Certification rules · Test a font file
Educational framing draws on public accessibility typography guidance, including Choosing the Right Typeface for Accessibility (Apple Education Community) and common WCAG-oriented font guidance. Typography Standard requirements and thresholds are defined by TS 2.0 methodology.