Skip to main content

Accessibility Statement

Last updated: March 20, 2026

Our Commitment

ContentEngine is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards to make our platform inclusive by design.

We believe that accessibility is not an afterthought but a fundamental requirement of good software. Every feature we build is evaluated against accessibility criteria before release.

Conformance Status

ContentEngine targets Web Content Accessibility Guidelines (WCAG) 2.2 Level AA conformance. WCAG 2.2 is the current W3C recommendation for making web content more accessible to a wider range of people with disabilities, including accommodations for blindness, low vision, deafness, hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these.

Our current conformance status is partially conformant with WCAG 2.2 Level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard. We are actively working to resolve any identified gaps. For full details, see our VPAT report.

Accessibility Features

ContentEngine includes the following accessibility features across the platform:

Perceivable

  • All non-text content has text alternatives (alt text for images, ARIA labels for icons)
  • Content can be presented in different ways without losing information or structure
  • Color is not used as the only visual means of conveying information — all status indicators use text labels alongside color
  • Text contrast ratios meet or exceed WCAG 2.2 AA requirements (4.5:1 for normal text, 3:1 for large text)
  • Content reflows properly at up to 400% zoom without loss of functionality
  • Text spacing can be adjusted without loss of content or functionality

Operable

  • All functionality is available from a keyboard with no keyboard traps
  • Focus indicators are visible on all interactive elements
  • Navigation is consistent and predictable across all pages
  • Skip navigation links allow users to bypass repeated content
  • No content flashes more than three times per second
  • Animations and transitions are disabled when the user has enabled the prefers-reduced-motion system setting
  • Pointer gestures have single-pointer alternatives and dragging actions have accessible alternatives
  • Target sizes for interactive elements meet the minimum 24x24 CSS pixel requirement

Understandable

  • The language of each page is identified in the HTML lang attribute
  • Form inputs have descriptive labels and clear error messages
  • Error suggestions are provided when input validation fails
  • Navigation mechanisms are consistent across pages
  • Help and documentation is available for complex features
  • Redundant entry is minimized — information previously entered is auto-populated where possible

Robust

  • Pages use valid, semantic HTML5 markup
  • ARIA roles, states, and properties are used correctly to enhance screen reader support
  • Status messages are communicated to assistive technologies using ARIA live regions
  • The platform is tested with major screen readers (NVDA, JAWS, VoiceOver) and browsers (Chrome, Firefox, Safari, Edge)

Known Limitations

While we strive for full conformance, the following areas have known accessibility limitations that we are actively working to address:

  • Rich text editor: The content editor uses a textarea-based approach. Some advanced editing actions may require workarounds for screen reader users. We are evaluating fully accessible editor alternatives.
  • AI-generated content: Content generated by AI may not always include appropriate heading hierarchy or alt text for images. Users should review generated content for accessibility before publishing.
  • Third-party integrations: OAuth login flows (Google, GitHub) redirect to third-party pages whose accessibility we cannot fully control.
  • Analytics charts: Some data visualizations may not be fully accessible to screen readers. We provide data tables as alternatives where possible.

Assistive Technology Compatibility

ContentEngine is designed to be compatible with the following assistive technologies:

  • Screen readers: NVDA, JAWS, VoiceOver (macOS/iOS), TalkBack (Android)
  • Voice control: Dragon NaturallySpeaking, Voice Control (macOS)
  • Screen magnification: ZoomText, built-in OS magnifiers
  • Keyboard-only navigation across all features
  • High contrast and reduced motion system preferences are respected

Assessment Methods

ContentEngine assesses accessibility through the following methods:

  • Automated testing using axe-core and Lighthouse
  • Manual keyboard navigation testing on all features
  • Screen reader testing with NVDA and VoiceOver
  • Color contrast analysis using WCAG contrast checkers
  • Review against WCAG 2.2 Level AA success criteria
  • Testing with browser zoom up to 400%

Feedback and Contact

We welcome your feedback on the accessibility of ContentEngine. If you encounter accessibility barriers or have suggestions for improvement, please contact us:

We aim to respond to accessibility feedback within 5 business days and to resolve reported issues within 30 days where technically feasible.

VPAT / Accessibility Conformance Report

A detailed Voluntary Product Accessibility Template (VPAT) report documenting our conformance with WCAG 2.2 criteria, Section 508, and EN 301 549 is available on our VPAT report page.

Formal Complaints

If you are not satisfied with our response to your accessibility concern, you may escalate by contacting us at legal@contentengine.ai. We take all accessibility complaints seriously and will work with you to find an acceptable resolution.