Skip to main content
Inclusive CMS

Accessibility

Accessibility Statement

Inclusive CMS is committed to making inclusivecms.com usable for as many people as possible. This page describes our standard, what we do, where we’re still improving, and how to send feedback.

Conforms to WCAG 2.2 Level AA Last reviewed: July 25, 2026

Our commitment

Accessibility is part of why Inclusive CMS exists. We design and build this site so it works well with keyboards, screen readers, and assistive technologies, and so it’s readable across a range of vision, motor, and cognitive needs.

Standard we follow

We build to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA . The legal floor under ADA Title II is WCAG 2.1 Level AA. We build to 2.2, the newer standard, so you clear the rule with margin and stay aligned as the guidelines evolve, the same standard we hold the product to. Where it’s relevant for higher-education customers, we also reference Section 508 in the United States.

Conformance status

This site fully conforms to WCAG 2.2 Level AA. “Fully conforms” means every page meets the standard, with no known exceptions at the time of the last review. We make that claim because we test for it rather than assume it. See How we assess. If you find something that doesn’t meet the standard, that’s a bug and we want to hear about it.

What we do

Specific things we build into the site:

Keyboard support

  • “Skip to main content” link.
  • All interactive elements are reachable by keyboard.
  • Visible focus indicators on links, buttons, and form fields.
  • Dialogs (like the cookie banner) trap focus and close on Esc.

Visual design

  • Color contrast targeted at WCAG AA in light and dark themes.
  • Light/dark mode toggle that respects system preferences.
  • Text reflows on small screens; layouts work down to 320px wide.
  • Icons that convey meaning are paired with text or labels.

Semantic structure

  • Headings are nested in document order.
  • Landmarks (header, nav, main, footer) are used consistently.
  • Form fields have labels; status messages use ARIA live regions.
  • Images use descriptive alt text or are marked decorative.

Motion & media

  • Decorative animations respect prefers-reduced-motion.
  • No auto-playing audio.
  • Embedded media includes captions or transcripts where available.

Known limitations

As of the last review we have no known WCAG 2.2 Level AA failures on this site. Two things are worth stating plainly anyway:

  • Automated testing covers only part of the standard. The rest depends on our manual review, and manual review can miss things.
  • This site loads a small number of third-party resources (web fonts, our tag manager, and an icon kit). We check them, but we don’t control them, and a change on their end could introduce an issue before we notice.

If you run into something that isn’t listed here, please tell us — see Feedback & contact.

Compatibility

We design and test on current versions of common browsers and assistive technologies, including:

  • Chrome, Firefox, Safari, and Microsoft Edge (current major versions).
  • VoiceOver on macOS and iOS.
  • NVDA on Windows.
  • Keyboard-only navigation, with and without screen reader.

This site may not behave as expected on browsers more than two major versions old, or on assistive technologies that are no longer supported by their vendor.

How we assess

This is a self-assessment. We have not commissioned a third-party audit of this site. What we do:

  • Automated testing with axe-core against the WCAG 2.0, 2.1, and 2.2 A and AA rule sets, across every page, in both light and dark themes. The last run returned zero violations.
  • Manual keyboard and screen reader checks during development.
  • Color contrast review of the design tokens used across the site.

Automated tools verify roughly a third of the WCAG success criteria. Passing them is necessary, not sufficient, which is why the manual checks and your feedback matter. Feedback from real visitors is one of our most useful inputs.

Feedback & contact

If something on this site is hard to use, or you can’t access information you need, please let us know. When you can, include the page URL, what you were trying to do, and the assistive technology and browser you were using — that helps us reproduce and fix it faster.

Email howdy@redizoo.com with the subject line “Accessibility feedback.” We aim to acknowledge requests within 5 business days.

This statement was last reviewed on July 25, 2026 and applies to inclusivecms.com. We update it whenever we make significant changes to the site or our accessibility approach.