URI Patterns
WCAG 2.1 contrast ratio requirements (4.5:1, 3:1, 7:1, etc.)
APCA (Accessible Perceptual Contrast Algorithm) lightness thresholds
List of supported contrast algorithms with descriptions
WCAG 2.1 Thresholds
URI
Response Schema
Requirements for normal text at Level AA
Requirements for large text at Level AA
Enhanced contrast for normal text at Level AAA
Enhanced contrast for large text at Level AAA
Requirements for UI components and graphical objects
Example Response
Quick Reference Table
| Level | Text Size | Required Ratio | WCAG Criterion |
|---|---|---|---|
| AA | Normal (< 18pt) | 4.5:1 | 1.4.3 |
| AA | Large (≥ 18pt) | 3:1 | 1.4.3 |
| AA | Non-text (UI) | 3:1 | 1.4.11 |
| AAA | Normal (< 18pt) | 7:1 | 1.4.6 |
| AAA | Large (≥ 18pt) | 4.5:1 | 1.4.6 |
What is “Large Text”?
Large text is defined as:
- 18pt or larger (24px at default browser settings)
- 14pt bold or larger (18.5px bold at default settings)
APCA Thresholds
URI
Response Schema
Requirements for body text (fluent reading)
Requirements for large text (headings, titles)
Requirements for non-text elements
Example Response
Quick Reference Table
| Use Case | Minimum Lc | Examples |
|---|---|---|
| Body text | 75 Lc | Paragraphs, articles, content |
| Large text | 60 Lc | Headings, titles, hero text |
| Non-text | 45 Lc | Icons, borders, focus rings |
| Placeholder | 60 Lc | Input placeholders |
| Disabled | 30 Lc | Disabled states (informational) |
APCA uses Lightness Contrast (Lc) instead of contrast ratios. Higher Lc values indicate better contrast. APCA is proposed for WCAG 3.0 but is not yet an official standard.
Contrast Algorithms
URI
Response Schema
Returns an array of algorithm information objects:Algorithm identifier:
"WCAG21" or "APCA"Human-readable algorithm name
Detailed explanation of the algorithm
Associated standard or specification
URI to fetch threshold data for this algorithm
Example Response
WCAG 2.1 vs APCA Comparison
| Aspect | WCAG 2.1 | APCA |
|---|---|---|
| Measurement | Luminance ratio (e.g., 4.5:1) | Lightness Contrast (Lc) |
| Formula | (L1 + 0.05) / (L2 + 0.05) | Complex perceptual model |
| Polarity | Same result either way | Different for dark-on-light vs light-on-dark |
| Accuracy | Good approximation | More perceptually accurate |
| Status | W3C Recommendation (current) | Draft (WCAG 3.0 proposal) |
| Legal standing | Widely adopted in regulations | Not yet official |
| Use case | Compliance, legal requirements | Design optimization, future-proofing |
When to Use Each
Use WCAG 2.1 for compliance
Use WCAG 2.1 for compliance
Required for:
- Legal compliance (ADA, Section 508, European Accessibility Act)
- Regulatory audits
- Official WCAG 2.1 conformance claims
Use APCA for design optimization
Use APCA for design optimization
Best for:
- Fine-tuning color palettes
- Dark mode optimization (polarity-aware)
- Future-proofing designs for WCAG 3.0
- More accurate perceptual contrast
Test both for comprehensive analysis
Test both for comprehensive analysis
Recommended approach:
- Use WCAG 2.1 as the compliance baseline
- Use APCA to identify perceptual issues WCAG 2.1 might miss
- Report both results for full transparency
Usage Examples
Check WCAG AA Requirements
Check APCA Requirements
Compare Algorithms
Validate Contrast Ratio
Integration with Tools
Theanalyze-contrast tool uses these thresholds automatically:
Related Resources
WCAG Criteria
Full details on criteria 1.4.3, 1.4.6, and 1.4.11
Contrast Tool
Automated contrast analysis using these thresholds
Contrast Prompt
Guided workflow for contrast checking
Lighthouse Audits
Lighthouse’s
color-contrast audit mappingStandards Reference
This resource is based on:- WCAG 2.1: Success Criterion 1.4.3 Contrast (Minimum)
- WCAG 2.1: Success Criterion 1.4.6 Contrast (Enhanced)
- WCAG 2.1: Success Criterion 1.4.11 Non-text Contrast
- APCA: WCAG 3.0 Draft Specification