Accessibility Statement

Last updated: November 2026

Our Commitment

OmniColor is committed to ensuring digital accessibility for all users, including people with disabilities. We believe that a color tools website — especially one that teaches accessibility — must itself be accessible. We continuously work to improve the experience for everyone and apply the relevant accessibility standards.

Conformance Status

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. These guidelines explain how to make web content more accessible for people with disabilities and more user-friendly for everyone.

OmniColor is designed and developed with WCAG 2.2 AA as the baseline conformance target. We test our pages regularly and address any issues we find.

Accessibility Features

OmniColor includes the following accessibility features:

Semantic HTML

  • All pages use semantic HTML5 landmarks: <header>, <nav>, <main>, <footer>, <article>, <section>
  • Proper heading hierarchy (single H1 per page, logical H2/H3/H4 progression)
  • Descriptive link text — no "click here" or "read more" links without context
  • Form labels properly associated with inputs via for and id

Keyboard Navigation

  • All interactive elements are reachable by keyboard (Tab key)
  • Focus indicators are visible on all focusable elements
  • Modal dialogs trap focus and restore it on close
  • Skip-to-content link appears on first Tab press
  • Dropdown menus are keyboard-navigable with arrow keys and Escape to close

Color and Contrast

  • All body text meets WCAG AA contrast (4.5:1 minimum)
  • All large text meets WCAG AA large-text contrast (3:1 minimum)
  • Interactive elements have contrast that clearly identifies them
  • Information is never conveyed by color alone — we pair it with text, icons or patterns
  • Our own contrast checker uses the exact WCAG formula — the same tool you can use on your own projects

Responsive Design

  • All pages are responsive and usable from 320px width to 4K displays
  • Content reflows without horizontal scrolling at 400% zoom
  • Text resizes up to 200% without loss of functionality
  • Touch targets meet minimum size guidelines (44x44px)

Screen Reader Support

  • ARIA landmarks and labels where semantic HTML is not sufficient
  • Live regions announce dynamic changes (copy success, form errors, etc.)
  • Images have descriptive alt text (or empty alt for decorative images)
  • SVG icons are marked aria-hidden="true" when decorative

Motion and Animation

  • The site respects prefers-reduced-motion — animations are disabled for users who request it
  • No auto-playing media
  • No content that flashes more than 3 times per second

Form Accessibility

  • All form inputs have associated labels
  • Required fields are marked both visually and programmatically
  • Error messages identify the field and describe the problem clearly
  • Form controls have sufficient size and spacing

Color Blindness

  • We provide a Color Blindness Simulator to test color combinations
  • Our palettes are tested against protanopia, deuteranopia and tritanopia
  • Where color conveys meaning, we supplement with icons, text or patterns

Known Limitations

Despite our best efforts, some areas may have limitations:

  • Third-party advertisements: Advertisements are served by third-party networks and we cannot guarantee their accessibility. If an ad causes accessibility problems, please report it and we will investigate.
  • PDF and CSV exports: Files downloaded from our tools may not be fully accessible without PDF remediation or proper CSV structure. We are working on improving exports.
  • Color picker canvas: The visual color picker relies on pointer interaction; we provide alternative text input for HEX, RGB and HSL values as accessible alternatives.
  • Complex gradient editors: Advanced gradient editors require drag-and-drop; we provide alternative numeric inputs where possible.

We are actively working to address these limitations in future releases.

Assessment Approach

OmniColor evaluates accessibility through:

  • Automated testing (Lighthouse, axe DevTools, WAVE)
  • Manual testing with keyboard navigation
  • Manual testing with screen readers (NVDA, VoiceOver)
  • Manual testing at multiple zoom levels
  • Testing our own tools with our contrast checker

We aim for ongoing evaluation rather than one-off audits.

Feedback and Reporting Issues

We welcome your feedback on the accessibility of OmniColor. If you encounter any accessibility barriers, please let us know:

When reporting an issue, please include:

  • The URL of the page with the issue
  • A description of the problem
  • The assistive technology you are using (browser, screen reader version, operating system)

We aim to respond to accessibility reports within 3 business days and to resolve confirmed issues within 10 business days.

Compatibility with Browsers and Assistive Technology

OmniColor is designed to work with recent versions of:

  • Browsers: Chrome, Firefox, Safari, Edge (latest 2 versions)
  • Screen readers: NVDA (Windows), JAWS (Windows), VoiceOver (macOS, iOS), TalkBack (Android)
  • Assistive technologies: Voice control software, switch access, screen magnification

If you use an older browser or assistive technology and encounter issues, please let us know.

Technical Specifications

Accessibility of OmniColor relies on the following technologies:

  • HTML5
  • CSS3 (including CSS custom properties, prefers-reduced-motion, prefers-color-scheme)
  • WAI-ARIA (Accessible Rich Internet Applications)
  • JavaScript (for interactive tools)

These technologies are relied upon for conformance with the accessibility standards used.

Formal Complaints

If you are not satisfied with our response to your accessibility concern, you may file a formal complaint through our feedback page. We treat formal accessibility complaints with priority and will respond within 5 business days.

Commitment to Ongoing Improvement

Accessibility is not a one-time achievement. We continue to:

  • Test new features with assistive technology before release
  • Train our team on accessibility best practices
  • Review existing features for accessibility regressions
  • Incorporate user feedback into our design process

Date of Last Review

This accessibility statement was last reviewed on November 2026. It will be reviewed at least annually.