Questions answered by this guide
- What contrast ratio does my text need?
- How do I check color contrast in Storyline or Rise?
- What's the difference between WCAG AA and AAA contrast?
- Do buttons and icons need contrast too, or just text?
- Why can't I just use red and green to show right and wrong answers?
- Which WCAG criterion covers color contrast?
What you'll learn
- Text needs a contrast ratio of at least 4.5 to 1 against its background
- Large text and headings can use a slightly lower ratio of 3 to 1
- Never use color alone to communicate meaning
What's inside
Instructional designers checking color contrast in any authoring tool
- 01The concept
- 02What WCAG requires for text
- 03What WCAG requires for icons and UI components
- 04How to check it
- 05Common mistakes
Why it matters
Low contrast text is hard to read for learners with low vision, color blindness, or anyone using a screen in bright light. This is WCAG success criterion 1.4.3 (Contrast Minimum, Level AA): normal text needs a ratio of at least 4.5 to 1, and large text, defined as at least 18pt, or 14pt bold, needs at least 3 to 1. A separate, easy-to-miss criterion, 1.4.11 (Non-text Contrast, Level AA), applies the same 3 to 1 minimum to icons, button borders, form field outlines, and other graphical UI components, contrast rules aren't only about body text. Good contrast is not just an accessibility requirement, it makes your course easier for every learner to read, especially on a laptop screen in a bright office or a phone screen outdoors.
When you'll encounter this
- You're styling body text, captions, or headings against a background color or image.
- You're designing a custom button, icon, or form field and choosing its border or outline color.
- Your course's theme uses light gray or pastel colors for text, common in "clean" or minimalist templates.
- A11yCheck flags a color contrast issue on a scan report.
Examples
Body text
✕ Incorrect
Body text set in #999999 light gray on a white (#FFFFFF) background.
This combination measures about 2.8 to 1, well under the 4.5 to 1 WCAG 1.4.3 requires for normal text, so it reads as faint and low-effort for learners with low vision, and genuinely hard to read for everyone in bright light.
✓ Correct
Body text set in #595959 dark gray on the same white background.
This combination measures about 7 to 1, comfortably clearing the 4.5 to 1 minimum, still reads as a soft neutral gray rather than harsh black, and holds up on a low-brightness screen or in a sunlit room.
Icon or button outline
✕ Incorrect
A custom icon-only button uses a 1.5px border in a pale blue (#BFDBFE) against a white card, no visible fill.
The border measures well under 3 to 1 against the white background, so the button's boundary is nearly invisible, this falls under WCAG 1.4.11, not 1.4.3, since it's a UI component, not text.
✓ Correct
The border is darkened to a mid-tone blue (#2563EB) at the same 1.5px weight.
This clears the 3 to 1 minimum 1.4.11 requires for UI components, so the button's clickable boundary is clearly visible against its background.
Best practices
- Use a contrast checker to test your actual text and background colors, not just a visual guess.
- Aim for a contrast ratio of at least 4.5 to 1 for normal-sized text.
- Larger text, like headings, can use a slightly lower ratio of at least 3 to 1.
- Icons, button borders, and other meaningful UI components need at least 3 to 1 too, this is a separate WCAG requirement (1.4.11) from body text.
- Never rely on color alone to communicate meaning. Add an icon or label alongside a color change.
Common mistakes
- Light gray text on a white background.
- Using red and green alone to show correct and incorrect answers, with no other indicator.
- Text placed directly on a busy image background with no way to check contrast.
- A pale, low-contrast border on a button or icon, checked as if only body text needed to meet a ratio.
Practical checklist
- Every block of text meets a contrast ratio of at least 4.5 to 1.
- Large text and headings meet at least 3 to 1.
- Icons, button borders, and form field outlines meet at least 3 to 1.
- Nothing relies on color alone to communicate meaning.
- Text on an image background has been checked, not just assumed to be readable.
How A11yCheck reviews this
A11yCheck's scan measures the actual contrast ratio of text against its background across every slide and flags anything under the WCAG 1.4.3 thresholds. It's still worth spot-checking custom icons, borders, and UI components by hand, since 1.4.11's non-text contrast rule covers more visual elements than an automated text-focused scan can exhaustively catch.
Frequently asked questions
What is a contrast ratio?
A number describing how different two colors are in brightness. A higher ratio means text is easier to read against its background.
Is there a stricter contrast requirement for higher accessibility levels?
Yes. WCAG's AAA level (1.4.6) asks for 7 to 1 for normal text and 4.5 to 1 for large text. Most eLearning accessibility targets, including A11yCheck's default checks, aim for AA (4.5 to 1 / 3 to 1), which is the level most organizations require, but AAA is worth the extra effort where it's achievable.
How do I check contrast in Storyline or Rise?
Neither tool has a built-in checker. Use a free online contrast checker, enter your text color and background color, and it will tell you the ratio.
Why can't I just use color to show correct and incorrect answers?
Learners with color blindness may not be able to tell red from green. Add an icon, like a checkmark or an X, alongside the color.
Related Guides
WCAG for eLearning: A Practical Introduction→
What WCAG actually is, and what it means for a Storyline or Rise course. No legal jargon.
Storyline Accessibility Quick Checklist→
A fast, practical pass through your Storyline course before you publish it, 20 checks, about 15 minutes.
Rise 360 Accessibility Quick Checklist→
A fast, practical pass through your Rise course before you publish it, 19 checks, about 15 minutes.
Low Colour Contrast→
Step-by-step guide to fixing low colour contrast and colour-only feedback in Articulate Storyline 360.
Low Colour Contrast→
Step-by-step guide to fixing low colour contrast and colour-only feedback in Articulate Rise 360.
Summary
Normal text needs at least 4.5 to 1 contrast, large text needs at least 3 to 1, and icons or UI components need at least 3 to 1 too, these are WCAG 1.4.3 and 1.4.11. Check actual colors with a contrast checker, and never rely on color alone to communicate meaning.
Review your course before you publish it.
A11yCheck reviews Storyline and Rise courses for:
- Accessibility
- Course Quality
- Course Engagement
www.a11ycheck-dev.com