WCAG 2.2 Colour Contrast Validator
- 1Enter your colours — Type or paste a hex code (e.g. #1a1a2e) into the foreground and background fields, or click the colour swatch to use a colour picker.
- 2Read the ratio — The contrast ratio is calculated instantly. AA requires 4.5:1 for normal text (3:1 for large text). AAA requires 7:1.
- 3Check the previews — The sample text blocks show how your colour pair looks at different sizes. The colour-blindness simulations show how the pairing appears to users with visual impairments.
- 4Adjust until it passes — If the pair fails, adjust the lightness of one colour until the ratio turns green. Use the suggested alternatives below the result if you need help.
Verify AA/AAA compliance, simulate colour blindness, and find the nearest passing colour.
rgb(0, 90, 156) · luminance: 0.0971
rgb(255, 255, 255) · luminance: 1.0000
0.00:1
Heading sample text
Body text: The quick brown fox jumps over the lazy dog.
Small text sample (14px equivalent)
What are you testing?
Select your use case to get a precise requirement and verdict.
✗ Fail — SC 1.4.3 Level AA
Required ratio: 4.5:1 · Your ratio: 0.00:1 · SC 1.4.3 Level AA
All WCAG 2.2 criteria
✗ Fail · 4.5:1
SC 1.4.3 — Contrast Minimum (Level AA)
Normal text: any text below 18pt regular or 14pt bold
This is the baseline requirement for body text, labels, links, and all standard-size content. Required by the EAA, EN 301 549, ADA (DOJ 2024 rule), and Section 508 in the US.
W3C Understanding document →✗ Fail · 3:1
SC 1.4.3 — Large Text (Level AA)
Text at 18pt (24px) regular or 14pt (18.67px) bold or larger
Large text is easier to read, so a lower contrast ratio is acceptable. The 18pt / 14pt bold thresholds come from print typography research. Required under the same regulations as SC 1.4.3 normal text.
W3C Understanding document →✗ Fail · 3:1
SC 1.4.11 — Non-text Contrast (Level AA)
UI components: button borders, input outlines, icons, focus rings, charts
Added in WCAG 2.1. Covers interactive components and graphical objects that convey information. Applies to button outlines, form input borders, checkbox squares, radio buttons, chart lines and segments. Text inside components is still covered by 1.4.3.
W3C Understanding document →✗ Fail · 7:1
SC 1.4.6 — Contrast Enhanced (Level AAA)
Recommended best practice — not required by most regulations
The enhanced level is not required by the EAA or most national laws but is recommended for high-readability content such as body copy for general audiences, and any text displayed on mobile screens in outdoor conditions.
W3C Understanding document →Nearest AA-passing foreground
Change foreground to #005DA1 (lighter) to achieve 4.5:1
CSS Custom Properties
Which laws and standards does this apply to?
Directive 2019/882/EU · Annex I Section IV
EU — products and services sold to consumers from 28 June 2025
The EAA mandates conformance with EN 301 549 v3.2.1, which references WCAG 2.1 Level AA as its web content standard. WCAG 2.2 AA is the current W3C recommendation and is considered best practice under the EAA. Passing SC 1.4.3 AA (4.5:1 normal text, 3:1 large text) and SC 1.4.11 AA (3:1 UI) satisfies the EAA colour contrast obligations.
EAA Directive text →Clause 9.1.4.3 · 9.1.4.11
EU — harmonised standard referenced by EAA and public sector bodies
EN 301 549 is the European harmonised standard for ICT accessibility. Clause 9.1.4.3 directly adopts WCAG 2.1 SC 1.4.3 (contrast minimum) and clause 9.1.4.11 adopts SC 1.4.11 (non-text contrast). Conformance with WCAG 2.2 AA satisfies both clauses because WCAG 2.2 is backwards compatible with WCAG 2.1.
EN 301 549 specification →DOJ Final Rule 28 CFR Part 35 · March 2024
US — Title II public entities. Title III (private businesses) expected to follow same standard
The US Department of Justice March 2024 final rule requires WCAG 2.1 Level AA for state and local government websites and mobile apps. SC 1.4.3 is a Level AA criterion. WCAG 2.2 AA is a superset of WCAG 2.1 AA, so passing here satisfies the ADA web rule. For private businesses, courts and DOJ guidance have consistently applied WCAG 2.1 AA as the benchmark.
DOJ web accessibility rule →36 CFR Part 1194 · E205.4 WCAG 2.0 Level AA
US — federal agencies and entities receiving federal funding
Section 508 currently mandates WCAG 2.0 Level AA. WCAG 2.0 SC 1.4.3 (contrast minimum) is identical in requirement to WCAG 2.2 SC 1.4.3. Passing this tool's AA check satisfies the Section 508 contrast requirement. The Access Board has signalled a future update to WCAG 2.1.
Section 508 ICT standards →Public Sector Bodies Accessibility Regulations · EN 301 549
UK — public sector bodies; private sector covered by Equality Act reasonable adjustment duty
UK PSBAR 2018 (as retained law post-Brexit) requires WCAG 2.1 Level AA for public sector websites and apps, referencing EN 301 549. SC 1.4.3 is a core requirement. For private organisations, the Equality Act 2010 duty to make reasonable adjustments is widely interpreted to include meeting WCAG AA contrast standards.
UK PSBAR legislation →SC 1.4.6 Contrast Enhanced
Best practice — not required by law for most contexts
AAA is recommended for content targeting older users, users with low vision not using assistive technology, or content displayed in challenging environments (outdoor screens, bright sunlight). Achieving AAA (7:1) is not required by the EAA, ADA, or Section 508 but demonstrates a high standard of accessibility commitment. Some internal accessibility policies and premium certification schemes require AAA for body text.
SC 1.4.6 Understanding document →Export as evidence
#005A9C on #FFFFFF = 0.00:1 — WCAG AA Fail
Every export includes a legal-evidence metadata footer with the audit ID, generation date, tool version, EN 301 549 clauses, and the standard disclaimer. Legal-grade evidence — not legal advice.
Important Legal Disclaimer
This tool is a self-assessment aid only and does not constitute legal advice or a formally certified compliance assessment. Outputs — including reports, scores, checklists, and accessibility statements — are for internal use and should be reviewed by a qualified legal representative or independent accessibility auditor before being relied upon for regulatory, procurement, or public-disclosure purposes. All assessment risk lies with the internal assessor. accessibilityref, its developers, and staff accept zero liability for losses arising from use of or reliance on these outputs. Always verify against official sources: the W3C WCAG 2.2 Recommendation, the European Accessibility Act (Directive 2019/882), and your national enforcement authority.