Accessibility (Typography)
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://fontfyi.com/iframe/glossary/accessibility-typography/" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>
Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://fontfyi.com/glossary/accessibility-typography/
Add a dynamic SVG badge to your README or docs.
[](https://fontfyi.com/glossary/accessibility-typography/)
Use the native HTML custom element.
Typography practices ensuring content is usable by everyone — sufficient contrast, scalable text, clear hierarchy, and appropriate font choices.
Accessible typography ensures that text-based content can be read, understood, and interacted with by the widest possible range of users — including people with low vision, color blindness, dyslexia, cognitive differences, motor impairments, and age-related changes in sight. Typography is arguably the most important accessibility domain on the web, because the vast majority of web content is text.
The foundational principle is this: if users can't read your text, nothing else on the page matters. Accessibility in typography is not a nice-to-have or a compliance checkbox — it's the baseline for functional communication.
Font size is the starting point. Never set body text below 16px equivalent (1rem). For users who have set their browser default font size larger, use relative units so text scales with their preferences:
/* Accessible: scales with user preference */
body {
font-size: 1rem; /* Inherits browser default (typically 16px) */
line-height: 1.6;
}
/* Inaccessible: ignores user preference */
body {
font-size: 14px; /* Always 14px regardless of user settings */
}
Never use px for font-size in body text if you can avoid it. Users who rely on browser zoom or accessibility font size settings expect relative units to honor those preferences.
Line height is often overlooked but critical for users with cognitive differences and dyslexia. WCAG 2.1 Success Criterion 1.4.12 (Text Spacing) requires that no content or functionality is lost when line height is increased to 1.5× font size:
p {
line-height: 1.6; /* Default comfortable reading */
letter-spacing: 0.02em; /* Slight spacing aids many readers */
word-spacing: 0.05em;
}
Color contrast must meet WCAG AA minimums: 4.5:1 ratio for normal text, 3:1 for large text (18pt+ or 14pt+ bold). Never convey meaning through color alone, and test with actual contrast ratio tools rather than visual estimation:
/* Accessible body text */
body {
color: #212121; /* ~16:1 contrast on white */
background: #ffffff;
}
/* Accessible secondary text */
.secondary {
color: #595959; /* 7:1+ contrast on white (passes AAA) */
}
Avoid text in images wherever possible — screen readers can't read it, it doesn't scale, and it fails zoom. Use real HTML text with CSS for all styling.
Focus indicators for keyboard navigation must be visible, especially for linked text. Don't remove outline without providing an equivalent visible indicator.
Typeface choices also affect accessibility. Fonts with high x-heights, open apertures, and clear letterform distinction support more users. System fonts (system-ui, -apple-system) are often an excellent accessible default because users are already familiar with them and they render at native OS quality.
관련 용어
관련 도구
이 개념을 보여주는 폰트
더 알아보기
비영리 타이포그래피는 제한된 예산 안에서 따뜻함, 신뢰성, 접근성 사이의 균형을 맞춰야 합니다. 명분 중심 디자인을 위한 최고의 무료 폰트와 전략을 다룹니다.
폰트 선택이러닝 타이포그래피는 이해도와 참여도에 영향을 미칩니다. 모든 연령과 능력의 학습자를 위한 학습을 향상시키는 폰트를 선택하는 방법입니다.
폰트 선택헬스케어 웹사이트는 모든 대상에게 신뢰할 수 있고, 접근성이 있으며, 읽기 쉬워야 합니다. 케어와 전문성을 전달하는 타이포그래피 선택을 다룹니다.
접근성스크린 리더는 시각적 타이포그래피를 무시하지만 시맨틱 마크업은 중요합니다. HTML 헤딩 구조, 언어 속성, 텍스트가 스크린 리더 사용자에게 미치는 영향을 다룹니다.