legibility

Diagnose and fix typography legibility issues in UI text elements.

8|3|Updated May 3, 2026
One-click install
npx skills add https://github.com/Deibler/universal-design-principles --skill legibility-deibler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: legibility
Source: https://github.com/Deibler/universal-design-principles/tree/main/plugins/perception-and-hierarchy-principles/skills/legibility
Command: npx skills add https://github.com/Deibler/universal-design-principles --skill legibility-deibler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? UI text that users cannot quickly read — ambiguous characters like I/1/l, low-contrast labels, hairline weights at small sizes — causes misread codes, failed forms, and accessibility failures. This Skill provides a systematic framework for evaluating and fixing the legibility of individual characters and short text in interfaces. ## Core Features & Use Cases - Five-input legibility model: Evaluates typeface design, size, weight, contrast, and spacing together, since a legible typeface can still fail under poor rendering conditions. - Diagnostic symptoms: Identifies legibility problems through observable signals like squinting, mistyped confirmation codes, excessive zoom usage, and WCAG contrast audit failures. - Worked patterns: Covers login forms, confirmation codes, display vs. body type pairing, button contrast, and code listings with concrete fixes. - Use Case: A user repeatedly mistypes a 6-character confirmation code because the typeface renders O and 0 identically. The Skill recommends switching to a disambiguation-focused typeface like JetBrains Mono or removing ambiguous characters from the code alphabet. ## Quick Start Audit the typography of my login form and confirmation code display for legibility problems and recommend fixes.

Frequently Asked Questions about legibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve text legibility in UI design?▼

Control the five inputs to legibility: choose a typeface designed for the intended size, keep body text at 14-16px or larger, use regular weight at small sizes, meet WCAG contrast ratios of at least 4.5:1, and set comfortable tracking and leading. Test at actual size on real devices.

What is the difference between legibility and readability?▼

Legibility is the visual clarity of individual characters and short phrases, determined by typeface, size, weight, contrast, and spacing. Readability concerns sustained reading of prose, involving line length, leading, and paragraph rhythm. UI labels are legibility problems; long articles are readability problems.

What typeface should I use for confirmation codes and IDs?▼

Use a monospace typeface designed for character disambiguation, such as JetBrains Mono, Fira Code, or Source Code Pro, which clearly distinguish 0/O and 1/I/l. Alternatively, remove ambiguous characters like 0, O, I, 1, and L from the code alphabet entirely.

What contrast ratio does WCAG require for text?▼

WCAG requires a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text (at least 18pt or 14pt bold). These are floors, not targets; ratios of 7:1 or higher substantially improve legibility for low-vision users and poor viewing conditions.

Why does thin or light font weight fail at small sizes?▼

Hairline and thin weights lose their strokes at small sizes, especially on lower-DPI displays or in glare, making characters disappear. Use regular or medium weights for body text and reserve light weights for large display headlines where strokes remain visible.

When should I use a display typeface versus a body typeface?▼

Use display typefaces only for headlines at large sizes, where their thin strokes and high contrast render correctly. Body copy needs typefaces designed for small-size legibility, such as Inter, IBM Plex Sans, or Source Sans, since display faces lose distinguishing features when scaled down.