Accessibility Statement

Last updated: April 28, 2026

Our commitment

ColorUI is built with accessibility as a first-class concern. We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA and the European Accessibility Act (EAA) requirements that take effect June 28, 2025. Color is a powerful design medium and an accessibility risk if used carelessly - so we design for both.

What we've implemented

Keyboard navigation. Every tool is fully operable with the keyboard. Visible focus rings on every interactive element. A "Skip to main content" link is the first focusable item on every page.
Color contrast. Body text and UI controls meet WCAG 2.2 AA contrast ratios in both light and dark themes. Our own Contrast Checker is used to audit every release.
Reduced motion. We respect prefers-reduced-motion: reduce: animations and transitions are stripped to near-instant for users who request reduced motion at the OS level.
Semantic HTML and ARIA. Headings, landmarks, lists and form labels follow the HTML standard. ARIA is added only where native semantics are insufficient.
Screen reader support. Tested with VoiceOver (macOS), NVDA (Windows) and TalkBack (Android) on the most-used tool flows.
Color-blind safety. Our Colorblind Simulator lets you preview any palette through deuteranopia, protanopia, tritanopia, and achromatopsia simulations.
Responsive design. Layouts work from 320 px viewports up to 4K. Touch targets meet the 24x24 CSS pixel minimum (WCAG 2.2 SC 2.5.8).
Theme awareness. Light and dark themes are first-class, with a system-preference fallback. The chosen theme is applied before first paint to avoid flashes.

Known limitations

The 3D Spatial and Worlds visualizers depend on WebGL. Devices without a working GPU will see a flat fallback experience.
Some advanced color tools (Mesh Gradient editor, Paint canvas) require pointer input and are not yet fully keyboard-equivalent. We're working on accessible alternatives.
Color visualizations are intrinsically visual. Where possible we expose numeric values, but a screen reader cannot describe the felt experience of a hue.

Standards we follow

WCAG 2.2 Level AA
EN 301 549 (European harmonized accessibility standard)
Section 508 (US federal)
European Accessibility Act (EAA) effective June 28, 2025

Reporting an issue

Found a barrier? We want to fix it. Please reach out via the channels listed on our About page. Include the URL, the device and assistive technology you were using, and what you expected to happen. We aim to respond within 5 business days and resolve confirmed accessibility defects in the next release cycle.

Formal complaints

If you are not satisfied with our response, EU users may contact the national enforcement body for the EAA in their country. US users may file a complaint with the relevant federal or state authority under the ADA.

Review cadence

We re-audit the full surface of ColorUI against WCAG 2.2 AA at least once per quarter and after any major release. This statement is updated whenever conformance status changes.

Our commitment

What we've implemented

Keyboard navigation. Every tool is fully operable with the keyboard. Visible focus rings on every interactive element. A "Skip to main content" link is the first focusable item on every page.

Color contrast. Body text and UI controls meet WCAG 2.2 AA contrast ratios in both light and dark themes. Our own Contrast Checker is used to audit every release.

Reduced motion. We respect prefers-reduced-motion: reduce: animations and transitions are stripped to near-instant for users who request reduced motion at the OS level.

Semantic HTML and ARIA. Headings, landmarks, lists and form labels follow the HTML standard. ARIA is added only where native semantics are insufficient.

Screen reader support. Tested with VoiceOver (macOS), NVDA (Windows) and TalkBack (Android) on the most-used tool flows.

Color-blind safety. Our Colorblind Simulator lets you preview any palette through deuteranopia, protanopia, tritanopia, and achromatopsia simulations.

Responsive design. Layouts work from 320 px viewports up to 4K. Touch targets meet the 24x24 CSS pixel minimum (WCAG 2.2 SC 2.5.8).

Theme awareness. Light and dark themes are first-class, with a system-preference fallback. The chosen theme is applied before first paint to avoid flashes.

Known limitations

The 3D Spatial and Worlds visualizers depend on WebGL. Devices without a working GPU will see a flat fallback experience.

Some advanced color tools (Mesh Gradient editor, Paint canvas) require pointer input and are not yet fully keyboard-equivalent. We're working on accessible alternatives.

Color visualizations are intrinsically visual. Where possible we expose numeric values, but a screen reader cannot describe the felt experience of a hue.

Reporting an issue