Accessibility Statement

Our commitment

VeloCMS is committed to making its website and platform accessible to people with disabilities. We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA across all public-facing surfaces.

We use automated testing via axe-core integrated into our end-to-end test suite, combined with manual review for keyboard navigation, focus management, and screen reader behaviour.

Conformance status

VeloCMS is substantially conformant with WCAG 2.1 Level AA. This means most of the success criteria are met. Any known gaps are documented below, and we are actively working to address them.

Our CI pipeline enforces zero critical and zero serious axe-core violations on every pull request via an automated gate. The following surfaces are covered:

• Landing page (/)
• Blog listing and article pages (/blog, /blog/[slug])
• Help Center (/help, /help/[slug])
• Documentation (/docs)
• Pricing and comparison pages (/pricing, /compare)
• Authentication flows (/login, /signup)
• Admin dashboard and all admin sub-pages
• Developer portal (/developers)
• Accessibility statement (/accessibility)

Technical approach

• Semantic HTML structure — one h1 per page, no skipped heading levels, landmark regions
• Skip-to-content link on every page (visible on keyboard focus, targets #main-content)
• Focus-visible styles on all interactive elements — keyboard users always see a clear focus indicator
• All images carry descriptive alt text; purely decorative images use alt=""
• All form inputs have visible labels associated via for attribute or aria-label
• lang="en" declared on every HTML document
• Colour contrast meets the WCAG AA 4.5:1 ratio for normal text and 3:1 for large text across all theme presets
• ARIA attributes (aria-label, aria-current, aria-expanded, aria-hidden) used where HTML semantics alone are insufficient

Known limitations

The following areas have known accessibility limitations. We document them here in the interest of transparency:

• Rich text editor (TipTap) — The visual block editor uses a ProseMirror contenteditable region. Keyboard navigation within complex block structures (tables, nested lists) may be inconsistent in some screen reader and OS combinations. We are tracking upstream TipTap accessibility improvements.
• Third-party embeds — User-embedded content (YouTube iframes, Twitter widgets, Stripe Checkout) may not fully conform to WCAG 2.1 AA. These surfaces are outside our direct control.
• Drag-and-drop page builder — The visual page builder uses pointer-based drag interactions. Keyboard-accessible reordering (via arrow keys) is provided as a fallback but may require additional testing on specific assistive technology combinations.

How to get accessible content

If you need information from VeloCMS in a different format (for example, a plain-text version of a page, or information delivered via email rather than a form), please contact us:

We aim to respond to accessibility enquiries within five working days.

Formal complaints

If you are not satisfied with our response or believe we have not met our obligations under the EU Web Accessibility Directive or the UK Equality Act 2010, you may contact the relevant enforcement body in your jurisdiction.

For EU residents, the relevant national authority is the competent monitoring body designated by your EU member state under Directive (EU) 2016/2102 and the EU Accessibility Act (Directive 2019/882).

Enforcement — EU Accessibility Act

VeloCMS is a commercial service accessible to consumers in the European Union. As a product covered by the European Accessibility Act (Directive 2019/882), which entered into force 28 June 2025, we are committed to meeting the applicable accessibility requirements. If you believe we are not meeting our obligations, contact us at [email protected] before escalating to a national authority.

How this statement was prepared

This statement was last updated 19 May 2026 following the Plan 03 WCAG 2.1 AA audit (readiness programme). The audit covered automated axe-core scanning across all critical user-facing surfaces (public routes, auth flows, admin console, developer portal), manual keyboard-navigation walkthrough, ARIA landmark review, colour-contrast token audit, and focus indicator verification. We review and update this statement at least once per quarter, or whenever a significant design change is released.