Graphic Design & Digital Media · Foundations

Accessibility in Graphic Design

Want it in plain words first? Jump to Eli explains — the same idea, no jargon.
On this page 9 sections
  1. In 30 seconds
  2. Why this matters
  3. The college version
  4. Eli explains
  5. Worked example
  6. Key takeaway
  7. Quick check
  8. Study tools
  9. Sources & references

In 30 seconds

Accessible design makes a layout perceivable and usable by people with disabilities, including those with low vision or color blindness. The main reference is the Web Content Accessibility Guidelines (WCAG) from the W3C Web Accessibility Initiative, built on four principles: Perceivable, Operable, Understandable, Robust. In practice it means enough color contrast, never using color alone to carry meaning, text alternatives for images, and readable type.

Why this matters

Roughly one in five people has a disability, so a design that ignores accessibility excludes a large audience and often reads poorly for everyone else too. Academically, WCAG gives you concrete, testable numbers, such as a 4.5:1 , that turn a vague goal into something you can check and defend. Practically, accessibility is increasingly a legal expectation: the 2024 U.S. Department of Justice ADA Title II rule adopts WCAG 2.1 Level AA for state and local government sites and apps. Learning the standard early means you build inclusion into layouts, type choices, and color systems from the first draft instead of retrofitting it after a complaint.

The college version

What accessibility means and the POUR framework

Accessibility in graphic design means creating visual work that people with disabilities can perceive and use, including people who are blind or have low vision, who are color-blind, or who read with a screen reader or magnifier. The dominant reference is the Web Content Accessibility Guidelines (WCAG), published by the W3C's Web Accessibility Initiative (WAI). WCAG is organized under four principles remembered as POUR: content must be Perceivable (users can sense it through some channel), Operable (they can navigate and interact with it), Understandable (information and operation are clear), and Robust (it works across current and future tools, including assistive technology). Under those principles sit testable success criteria at three conformance levels: A (minimum), AA (the common target), and AAA (the strictest). Most organizations, and most laws that reference WCAG, aim at Level AA. Although WCAG grew up around web content, its criteria for contrast, color, text alternatives, and readable text apply directly to the visual decisions a graphic designer makes in layouts, infographics, social posts, and interface screens.

Color contrast minimums, with the exact numbers

Contrast between text and its background is the single most-tested accessibility requirement. WCAG 2.1 Success Criterion 1.4.3 (Level AA) sets a contrast ratio of at least 4.5:1 for normal text and at least 3:1 for large text. Large text is defined as 18 point, or 14 point bold, which is roughly 24 pixels or 18.5 pixels on a typical screen; larger, heavier letters stay legible at a lower ratio because their strokes are thicker. Contrast ratio is a number from 1:1 (identical) to 21:1 (pure black on pure white), computed from the relative luminance of the two colors, so it is a property of the color pair, not of either color alone. A separate criterion, 1.4.11 Non-text Contrast (also AA), extends a 3:1 minimum to user interface components, such as a button border or a form-field outline, and to graphical objects needed to understand content, such as the bars in a chart or the segments of a pie. Logos and incidental or purely decorative text are exempt. Getting these numbers right is not just compliance: low-contrast text is hard to read for aging eyes, on dim or glary screens, and in bright sunlight, so meeting the ratio helps essentially every reader.

Don't rely on color alone

WCAG 2.1 Success Criterion 1.4.1, Use of Color (Level A, the most basic tier), requires that color never be the only visual means of conveying information, indicating an action, prompting a response, or distinguishing an element. Around one in twelve men and one in two hundred women has some form of color vision deficiency, most commonly difficulty separating red from green, so a cue carried purely by hue can vanish for them. The fix is redundant encoding: pair color with a second signal. A required form field marked in red also gets an asterisk or the word 'required.' An error message uses an icon and text, not just red type. A line chart labels each line directly or varies line style and markers rather than relying on legend color. Links inside body text are underlined, not merely tinted. This rule is one of the clearest places where accessibility overlaps with plain good design, because a second cue helps anyone scanning quickly or viewing on a low-quality display.

Text alternatives for images

Screen readers cannot see a picture; they read its text alternative, the alt text, aloud. WCAG 2.1 Success Criterion 1.1.1 requires a text alternative for non-text content, and the W3C WAI publishes a decision tree for choosing it. If an image carries information, its alt text should convey that meaning concisely: a photo captioned 'a nurse demonstrates a blood-pressure cuff' rather than 'image1.jpg.' If an image is functional, such as a magnifying-glass icon that submits a search, the alt text names the action ('Search'), not the picture. Complex images like detailed charts put their data in nearby text or a table. Crucially, purely decorative images, a background flourish or a divider that adds nothing to meaning, should carry an empty alt attribute, written alt="", so the screen reader skips them instead of announcing clutter. The judgment a designer makes, meaningful versus decorative, is therefore an accessibility decision, and it belongs in the design and handoff, not left to a developer to guess.

Readable typography and inclusive design as a mindset

Accessible type is legible type. That means adequate font size, generous spacing, and line lengths that do not force the eye to hunt for the next line. WCAG 2.1 Success Criterion 1.4.12 Text Spacing (AA) says content must survive when a user overrides spacing to line height of at least 1.5 times the font size, paragraph spacing of at least 2 times, letter spacing of at least 0.12 times, and word spacing of at least 0.16 times the font size; designing near those values from the start prevents text from clipping or overlapping when readers adjust it. Beyond any single rule, accessibility is best held as a mindset rather than a final checklist. The related idea of universal, or inclusive, design, articulated by NC State's Center for Universal Design, aims for products usable by all people to the greatest extent possible without special adaptation. Finally, note the legal backdrop without mistaking this lesson for legal advice: laws such as the Americans with Disabilities Act and Section 508 reference accessibility, and the 2024 DOJ ADA Title II rule names WCAG 2.1 AA for state and local government content. Treat those as reasons the craft matters, and consult a qualified professional for actual compliance questions.

Eli, the EliExplains learning guide

Eli explains

The same idea, in plain words

Explain it like I’m 10

Some people can't see certain colors, can't see the screen well, or use a computer voice that reads pages out loud. Accessible design makes sure your work still gets through to them. Put dark text on a light background so it is easy to read, don't use only color to say 'this is the important one' (add a word, a shape, or an underline too), and give every meaningful picture a short written description so the computer voice can say what it shows. There are official rules called WCAG that even give you exact numbers to check, like how much light and dark a color pair needs.

Picture it like this

Think of accessibility like building with both a ramp and stairs. The stairs work for many people, but the ramp means a person using a wheelchair, someone pushing a stroller, and a delivery worker with a cart can all get in through the same door. Designing accessibly is adding the ramp on purpose, so no one is stuck outside.

Where the picture stops working

The ramp picture makes accessibility sound like one extra add-on you bolt on at the end. Real accessibility is many small choices woven through the whole design (color, type, labels, structure), and unlike a single ramp there is no one feature that covers everyone, since a blind reader, a color-blind reader, and a low-vision reader each need different things.

Worked example

A student designs an event poster: light gray body text (#9AA0A6) on a white background, and a schedule where 'sold out' sessions are shown only in red. Checking against WCAG: the gray-on-white text computes to about 2.6:1, below the 4.5:1 minimum for normal text, so it fails 1.4.3, they darken it to a gray near #595F66 that clears 4.5:1. The red-only 'sold out' cue fails 1.4.1 Use of Color, because a red-green color-blind reader can't tell those sessions apart, so they add the word 'FULL' and a small lock icon next to each. The poster's decorative corner flourish gets alt="" in the digital version, while the informative venue map gets alt text describing the entrance and accessible route. Same design, now perceivable by far more of the audience.

Key takeaway

Accessible graphic design follows WCAG's POUR principles with concrete, checkable rules: 4.5:1 contrast for normal text and 3:1 for large text and graphical objects, never carrying meaning by color alone, and giving meaningful images real alt text while marking decorative ones with empty alt.

Quick check

3 questions here, of 5 in this lesson’s practice set. Answers stay hidden until you check.

Question 1 of 3foundational

Under WCAG 2.1 Level AA, what is the minimum contrast ratio required for normal-size body text against its background?

Choose an answer, then check it.
Question 2 of 3intermediate

A dashboard shows system status using only color: green dots for 'healthy' and red dots for 'error,' with no other indicator. Which WCAG requirement does this most directly violate, and what is the fix?

Choose an answer, then check it.
Question 3 of 3intermediate

A page has a purely decorative swirl graphic in the header that adds no information. What is the correct accessibility treatment for its alt attribute?

Choose an answer, then check it.
Practice all 5

Keep learning

Ready to build on this? Continue to the next lesson.

Practice this lesson
Study tools & related lessonsYou’ll learn to · Common mistakes · Easily confused · Key vocabulary · Related

You’ll learn to

  • Define accessibility in graphic design and identify the WCAG POUR principles.
  • State the WCAG 2.1 AA color-contrast minimums for text and for graphical objects.
  • Explain the don't-rely-on-color-alone rule and apply it to a design decision.
  • Distinguish images that need descriptive alt text from decorative images that take empty alt.
  • Evaluate a layout's typography and color choices against accessibility criteria.

Common mistakes

  • Assuming a color 'looks like enough contrast,' so no measurement is needed.

    Contrast is a computed ratio; check the pair against 4.5:1 (normal text) or 3:1 (large text) with a contrast checker rather than trusting your eye on a good monitor.

  • Using red/green or any single color to mark status, errors, or chart series.

    Add a second cue (text label, icon, pattern, or underline) so the meaning survives for color-blind users, satisfying SC 1.4.1.

  • Writing vague or filler alt text like 'image' or the file name, or giving decorative images long descriptions.

    Describe the meaning or function for informative and functional images; use empty alt (alt="") for purely decorative ones so screen readers skip them.

  • Treating the 3:1 large-text ratio as if it also covered normal body text.

    3:1 only applies to large text (18pt / 14pt bold) and to UI components and graphical objects; normal body text still needs 4.5:1.

  • Believing meeting WCAG guarantees legal compliance, or that the lesson is legal advice.

    WCAG is the technical standard many laws reference, but compliance is fact-specific; treat accessibility as good craft and consult a qualified professional for legal obligations.

Easily confused

Contrast (Minimum), SC 1.4.3 vs. Non-text Contrast, SC 1.4.11

1.4.3 governs text against its background (4.5:1, or 3:1 for large text); 1.4.11 governs UI components and graphical objects at 3:1.

Descriptive alt text vs. Empty alt (alt="")

Meaningful and functional images need a concise description of their content or action; purely decorative images take an empty alt so assistive tech skips them.

Accessibility (this topic) vs. Contrast as a design principle (separate topic)

Accessibility owns the measurable WCAG thresholds and the reasons behind them; the contrast principle is about visual emphasis and hierarchy more broadly.

Key vocabulary

WCAG (Web Content Accessibility Guidelines)
The internationally used set of accessibility guidelines published by the W3C Web Accessibility Initiative, organized as testable success criteria.
W3C WAI (Web Accessibility Initiative)
The part of the World Wide Web Consortium that develops WCAG and related accessibility resources.
POUR principles
WCAG's four organizing principles: content must be Perceivable, Operable, Understandable, and Robust.
Conformance level
One of WCAG's three tiers of requirements: A (minimum), AA (the common target), and AAA (strictest).
Contrast ratio
A number from 1:1 to 21:1 measuring the luminance difference between two colors, such as text and its background.
Large text (WCAG)
Text at 18 point, or 14 point bold (about 24px or 18.5px), which qualifies for the lower 3:1 contrast minimum.
Alt text (text alternative)
A short written description of an image that assistive technology reads in place of the picture.
Decorative image
An image that adds no information and should carry an empty alt attribute (alt="") so screen readers skip it.
Universal (inclusive) design
Designing products and environments to be usable by all people to the greatest extent possible without special adaptation.

Sources & references

  1. WCAG 2 Overview — World Wide Web Consortium (W3C), Web Accessibility Initiative
  2. Understanding Success Criterion 1.4.3: Contrast (Minimum) — World Wide Web Consortium (W3C), Web Accessibility Initiative
  3. Understanding SC 1.4.11: Non-text Contrast (Level AA) — W3C Web Accessibility Initiative (WAI)
  4. Understanding SC 1.4.1: Use of Color (Level A) — W3C Web Accessibility Initiative (WAI)
  5. An alt Decision Tree (Images Tutorial) — W3C Web Accessibility Initiative (WAI)
  6. Understanding SC 1.4.12: Text Spacing (Level AA) — W3C Web Accessibility Initiative (WAI)
  7. Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments — U.S. Department of Justice, Civil Rights Division (ADA.gov)
  8. Low-Contrast Text Is Not the Answer — Nielsen Norman Group (Katie Sherwin)
  9. Center for Universal Design — College of Design, North Carolina State University

EliExplains lessons are original prose written from the open, credible references above. See Copyright & Licensing.

Researched 2026-08-19

Educational content only. It is not medical, legal or professional advice. Found an error? Tell us.