VPAT — Accessibility Conformance Report
Based on VPAT 2.5 | WCAG 2.2 Edition — Last updated: March 20, 2026
Product Information
| Product Name | ContentEngine |
|---|---|
| Product Version | Web Application (SaaS) |
| Report Date | March 20, 2026 |
| Contact | accessibility@contentengine.ai |
| Evaluation Methods | Automated testing (axe-core, Lighthouse), manual keyboard and screen reader testing (NVDA, VoiceOver), expert review against WCAG 2.2 success criteria. |
| Applicable Standards | WCAG 2.2 Level A and AA, Section 508 (Revised), EN 301 549 V3.2.1 |
Conformance Summary
Of the 47 applicable WCAG 2.2 Level A and AA criteria evaluated, ContentEngine fully supports 47 criteria (100% full conformance rate).
Supports
Partially Supports
Does Not Support
Not Applicable
Conformance Level Definitions
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
Table 1: WCAG 2.2 Level A
| Criterion | Name | Conformance | Remarks |
|---|---|---|---|
| 1.1.1 | Non-text Content | Supports | All images, icons, and non-text elements have text alternatives via alt attributes or ARIA labels. Decorative SVGs are marked aria-hidden. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | Not Applicable | The platform does not include prerecorded audio-only or video-only content. |
| 1.2.2 | Captions (Prerecorded) | Not Applicable | The platform does not include prerecorded synchronized media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | Not Applicable | No prerecorded video content is present. |
| 1.3.1 | Info and Relationships | Supports | Semantic HTML5 elements are used. Forms use proper labels. Tables use appropriate headers. ARIA roles supplement where needed. |
| 1.3.2 | Meaningful Sequence | Supports | DOM order matches visual presentation. Reading order is logical throughout. |
| 1.3.3 | Sensory Characteristics | Supports | Instructions do not rely solely on shape, color, size, or visual location. |
| 1.4.1 | Use of Color | Supports | Color is supplemented by text labels, icons, shapes, or screen-reader text for all meaningful distinctions. Status badges use text, SEO scores include status labels, trend indicators have sr-only direction text, and credit meters include textual warnings. |
| 1.4.2 | Audio Control | Not Applicable | The platform does not auto-play audio. |
| 2.1.1 | Keyboard | Supports | All interactive elements are keyboard accessible. Custom components use appropriate keyboard handlers. |
| 2.1.2 | No Keyboard Trap | Supports | Focus can be moved away from all components using standard keyboard navigation. Modals trap focus correctly and release on close. |
| 2.1.4 | Character Key Shortcuts | Not Applicable | No single character key shortcuts are implemented. |
| 2.2.1 | Timing Adjustable | Supports | No time limits are imposed on user interactions. Session timeouts provide adequate warning. |
| 2.2.2 | Pause, Stop, Hide | Supports | Loading spinners are the only auto-updating content and are purely decorative with ARIA labels. |
| 2.3.1 | Three Flashes or Below Threshold | Supports | No content flashes more than three times per second. |
| 2.4.1 | Bypass Blocks | Supports | Skip-to-main-content links are provided in all layouts (app, marketing, admin). They are visually hidden until focused via keyboard. |
| 2.4.2 | Page Titled | Supports | All pages have descriptive, unique titles set via Next.js metadata. |
| 2.4.3 | Focus Order | Supports | Focus order follows a logical sequence matching the visual layout. |
| 2.4.4 | Link Purpose (In Context) | Supports | Link text is descriptive. Icon-only links use aria-label attributes. |
| 2.5.1 | Pointer Gestures | Supports | No multipoint or path-based gestures are required. All actions have single-pointer alternatives. |
| 2.5.2 | Pointer Cancellation | Supports | Actions trigger on click/up events, not on down events. Users can abort by moving pointer away. |
| 2.5.3 | Label in Name | Supports | Accessible names of UI components contain the visible label text. |
| 2.5.4 | Motion Actuation | Not Applicable | No device motion-triggered functionality exists. |
| 3.1.1 | Language of Page | Supports | HTML lang attribute is set to 'en' on all pages. |
| 3.2.1 | On Focus | Supports | No context changes occur on focus alone. |
| 3.2.2 | On Input | Supports | Form submissions require explicit user action. No automatic context changes on input. |
| 3.2.6 | Consistent Help | Supports | Help mechanisms are in consistent locations across pages. |
| 3.3.1 | Error Identification | Supports | Form errors are clearly identified with descriptive text messages adjacent to the field. |
| 3.3.2 | Labels or Instructions | Supports | All form fields have visible labels. Required fields are indicated. Placeholder text supplements but does not replace labels. |
| 3.3.7 | Redundant Entry | Supports | Previously entered information is auto-populated. Users are not asked to re-enter data within the same session. |
| 4.1.2 | Name, Role, Value | Supports | Standard HTML elements and ARIA attributes ensure name, role, and value are programmatically determined for all UI components. |
| 4.1.3 | Status Messages | Supports | Toast notifications and status updates use ARIA live regions to announce changes to assistive technologies. |
Table 2: WCAG 2.2 Level AA
| Criterion | Name | Conformance | Remarks |
|---|---|---|---|
| 1.2.4 | Captions (Live) | Not Applicable | No live audio content is present. |
| 1.2.5 | Audio Description (Prerecorded) | Not Applicable | No prerecorded video content is present. |
| 1.3.4 | Orientation | Supports | Content displays correctly in both portrait and landscape orientations. |
| 1.3.5 | Identify Input Purpose | Supports | Form inputs use appropriate autocomplete attributes (email, name, etc.). |
| 1.4.3 | Contrast (Minimum) | Supports | Text contrast ratios meet 4.5:1 for normal text and 3:1 for large text in both light and dark themes. |
| 1.4.4 | Resize Text | Supports | Text can be resized up to 200% without loss of content or functionality. |
| 1.4.5 | Images of Text | Supports | No images of text are used. All text is rendered as actual text. |
| 1.4.10 | Reflow | Supports | Content reflows at 400% zoom (320px equivalent) without horizontal scrolling for vertical content. |
| 1.4.11 | Non-text Contrast | Supports | UI components and graphical objects have at least 3:1 contrast against adjacent colors. |
| 1.4.12 | Text Spacing | Supports | Content adapts to user-defined text spacing adjustments without loss of content or functionality. |
| 1.4.13 | Content on Hover or Focus | Supports | Tooltips and popovers are dismissible, hoverable, and persistent until dismissed. |
| 2.4.5 | Multiple Ways | Supports | Multiple navigation methods: sidebar nav, search, direct URLs, breadcrumbs. |
| 2.4.6 | Headings and Labels | Supports | Headings and labels accurately describe the topic or purpose of content. |
| 2.4.7 | Focus Visible | Supports | Keyboard focus indicators are clearly visible on all interactive elements using ring styles. |
| 2.4.11 | Focus Not Obscured (Minimum) | Supports | Focused elements are not entirely hidden by other content. Sticky headers account for scroll offset. |
| 2.5.7 | Dragging Movements | Supports | Any dragging operations have accessible click-based alternatives. |
| 2.5.8 | Target Size (Minimum) | Supports | Interactive targets are at least 24x24 CSS pixels or have sufficient spacing. |
| 3.1.2 | Language of Parts | Supports | The application is in English throughout. No mixed-language content requiring lang attributes on parts. |
| 3.2.3 | Consistent Navigation | Supports | Navigation sidebar and top navigation maintain consistent order across all pages. |
| 3.2.4 | Consistent Identification | Supports | Components with the same functionality are identified consistently throughout the platform. |
| 3.3.3 | Error Suggestion | Supports | When input errors are detected, suggestions for correction are provided in text. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | Supports | Destructive actions (delete workspace, remove member) require confirmation dialogs. Billing changes are reversible. |
| 3.3.8 | Accessible Authentication (Minimum) | Supports | Authentication supports password managers, copy-paste, and OAuth social login. No cognitive function tests are required. |
Section 508 Report
ContentEngine's WCAG 2.2 Level AA conformance as documented above satisfies the Revised Section 508 Standards (36 CFR 1194) requirements for web-based intranet and internet information and applications (Chapter 5, 602.3). The WCAG 2.2 criteria listed in Tables 1 and 2 above map directly to the Section 508 functional performance criteria.
EN 301 549 Report
ContentEngine's WCAG 2.2 Level AA conformance as documented above satisfies the applicable requirements of EN 301 549 V3.2.1 (Accessibility requirements for ICT products and services), Chapter 9 (Web) and Chapter 11 (Software) where applicable to web applications. The WCAG criteria mapped above apply to EN 301 549 Clauses 9.1 through 9.4 and 11.1 through 11.4.
Legal Disclaimer
This report is provided for informational purposes and represents the product's accessibility status at the time of evaluation. Accessibility conformance is an ongoing effort. This document does not constitute a warranty or guarantee of full accessibility. For the most current information, please contact us at accessibility@contentengine.ai. See also our Accessibility Statement.