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.

Targets WCAG 2.1 Level AA Last reviewed: May 7, 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 target the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA . Where it’s relevant for higher-education customers, we also reference Section 508 in the United States.

Conformance status

This site substantially conforms to WCAG 2.1 Level AA. “Substantially conforms” means most of the site meets the standard, with some known issues we’re actively working to fix (see Known limitations).

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

Despite our efforts, some areas of the site may not yet fully meet WCAG 2.1 Level AA. Known issues include:

  • Some demonstration screenshots and product mockups may not have detailed text equivalents.
  • Third-party content (such as embedded scripts or media) may not always meet our standard.
  • Older marketing pages may use patterns we’re still updating to current guidance.

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

We currently rely on internal review, including:

  • Manual keyboard and screen reader checks during development.
  • Automated tooling (such as axe-core / browser dev-tool audits) on key pages.
  • Color contrast review of design tokens used across the site.

Self-assessment doesn’t replace user feedback — 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 May 7, 2026 and applies to inclusivecms.com. We update it whenever we make significant changes to the site or our accessibility approach.