Platform Accessibility Statement
About this document
This accessibility statement explains how accessible the Jadu platform is, which products it applies to, and how we are working to meet accessibility standards.
This statement applies to the following Jadu products and versions:
| Product | Version |
|---|---|
| Jadu Central (CMS and Forms) | 4.1.3 |
| Jadu Connect | 1.242 |
Last reviewed and updated April 27th, 2026.
Scope of this document
This statement covers the Control Center user interfaces for each listed product.
Websites delivered by Jadu Central are not covered by this statement. Front-end website templates powered by the Jadu Platform are built and tested to conform with WCAG 2.2 Level AA at a minimum. Please refer to the relevant website’s own accessibility statement for more information.
For technical conformance information relating to front-end website templates as well as content and forms created using the platform, see our Accessibility Conformance Report (ACR).
Technical information about the platform's accessibility
Jadu is committed to making its web-based software accessible to everyone. Our platform is designed and developed to conform with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, as required by many accessibility-related laws and regulations worldwide, including (but not limited to):
- Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations (UK)
- Section 508 (US)
- ADA Title II (US)
Compliance Status
The current compliance status of each product is outlined below:
| Product | Status |
|---|---|
| Jadu Central (Control Center) | This product is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard |
| Jadu Connect (Control Center) | This product is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard |
Accessibility at Jadu
Accessibility is a fundamental part of everything we do at Jadu. It is embedded throughout our development lifecycle, with accessibility considerations included from design through to delivery and ongoing maintenance.
We aim to meet WCAG 2.2 Level AA as a minimum and follow best practices beyond WCAG, supported by regular checks and reviews throughout development.
Our accessibility commitment
At Jadu, we are committed to delivering a platform that is accessible to everyone. This includes:
- Meeting standards: Adhering to the WCAG 2.2 Level AA as a minimum
- Continuous improvement: Regularly testing and improving the accessibility of our platform
- Inclusive features: Creating innovative tools that allow Jadu users to craft wonderfully accessible content
How we manage and improve accessibility
Leadership
Our dedicated Head of Accessibility oversees the accessibility of the platform and works with senior leadership to prioritise improvements based on accessibility testing and user feedback.
Training
We provide regular, role-specific training to our designers, developers, and testers to ensure accessibility knowledge remains current and aligned with updates to standards and best practice.
Testing and continuous improvement
We continuously test the user interfaces, components, and features that make up the Jadu platform. Accessibility is considered throughout the design and development of new features, alongside periodic in-depth accessibility audits.
Testing includes both automated and manual approaches. For automated testing, we use industry-standard tools, including (but not limited to):
- Deque AXE
- IBM Equal Access
- TPGI ARC Toolkit
- WAVE
- Site Improve
- Silktide
Manual accessibility testing follows the Website Accessibility Conformance Evaluation Methodology (WCAG-EM), allowing us to assess criteria that cannot be programmatically tested.
Known issues
We are committed to making our full platform accessible. However, as with any complex, enterprise-level software with hundreds of interfaces and interactions, some accessibility issues are known to exist. These issues are prioritised and actively addressed, with fixes already completed and more scheduled for future releases.
- Some older user interfaces use a select element to provide a list of possible content items to be edited. Choosing an item from this list triggers a potentially unexpected change of context and reloads the page to display the chosen content type.
This fails WCAG 2.2 success criterion 3.2.2 (On Input).
Affects Jadu Central. - Some pages use an enhanced select element, which provides extra functionality such as quick-search. Users of assistive technologies may not be able to access the correct labelling for a form field using these elements.
This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
Affects Jadu Central. - Where the ability to edit images is provided, it is not possible to perform actions like cropping or repositioning images without using a pointing device. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard) and 2.5.7 (Dragging Movements).
Affects Jadu Central and Connect. - Some pages provide an enhanced date field which shows an interactive calendar to choose dates; it is not possible to interact with this calendar using keyboard controls, and the calendar may not be appropriately labelled for users of assistive technologies. In most cases, an accessible alternative, such as a text input, is provided.
This fails WCAG 2.2 success criterion 2.1.1 (Keyboard), and 4.1.2 (Name, Role, Value).
Affects Jadu Central. - Some pages use modals that do not capture and trap focus properly.
This fails WCAG 2.2 success criterion 2.4.3 (Focus Order).
Affects Jadu Central. - Some pages contain elements that don’t appropriately reflow, causing content to be obscured and requiring horizontal scrolling to access.
This fails WCAG 2.2 success criterion 1.4.10 (Reflow).
Affects Jadu Central. - Some forms do not provide a sufficient text description within an error summary panel or alert dialog when mandatory fields are not completed.
This fails WCAG 2.2 success criterion 3.3.1 (Error identification).
Affects Jadu Central. - Some pages allow items displayed in a table list to be reordered, but don’t provide a way to reorder them without using a pointing device.
This fails WCAG 2.2 success criterion 2.1.1 (Keyboard).
Affects Jadu Central. - Some pages have forms with required fields denoted by an asterisk (*), but do not have any text explaining the meaning of the asterisk.
This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions).
Affects Jadu Central.
Feedback and contact information
We want everyone to be able to access the information provided in this statement.
Tell us if you need information in a different format.
In your message, include:
- the name of this content (Platform accessibility statement)
- your email address and name
- the format you need (for example: plain text, braille, or large print)
