Platform Accessibility Statement
About this document
This accessibility statement applies to the following Jadu Continuum Platform products.
Scope of this document
This document relates to the Control Center user interfaces for each product. Public websites, such as the ones delivered by CMS and/or XFP are not covered by this document. Please refer to the website's own accessibility statement for more information.
| Product | Version |
|---|---|
| Content Management System (CMS) | 20.0.0 |
| XForms Professional (XFP) | 7.0.0 |
| Customer Experience Management (CXM) | 139 |
Feedback and contact information
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, BSL, large print or audio CD.
Technical information about the software's accessibility
Jadu is committed to making its web based software accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’).
If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Compliance Status
| Product | Status |
|---|---|
| Content Management System (CMS) | This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard |
| XForms Professional (XFP) | This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard |
| Customer Experience Management (CXM) | This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard |
Non-compliance with the accessibility regulations
The content listed below is non-accessible for the following reasons.
- It is not possible for users of the software to disable or extend the default timeout values, they may be signed out before completing their tasks and lose unsaved information. This fails WCAG 2.1 success criterion 2.2.1 (Timing Adjustable). Affects CMS, XFP, CXM, CP
- 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. This fails WCAG 2.1 success criterion 3.2.2 (On Input). Affects CMS, XFP, CP
- When a website theme is previewed in the Galaxies Designer, the theme may contain accessibility, validation or functional issues. Themes should be considered as user-generated content and are not within the scope of our responsibility. Affects CMS
- 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.1 success criterion 1.3.1 (Info and Relationships), 3.3.2 (Labels or Instructions, and/or 4.1.2 (Name, Role, Value). Affects CMS, XFP, CP
- 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 and a path-based gesture. This fails WCAG 2.1 success criterion 2.5.1 (Pointer gestures). Affects CMS, CXM
- 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. This fails WCAG success criterion 2.1.1 (Keyboard), 1.3.1 (Info and Relationships), 3.3.2 (Labels or Instructions, and/or 4.1.2 (Name, Role, Value). Affects CMS, XFP
- Some pages show incorrect, incomplete or otherwise unexpected information following a user-initiated action. This fails WCAG success criterion 1.3.1 (Info and Relationships). Affects CMS, XFP
- Some pages use modals which do not capture and trap focus properly. This fails WCAG 2.1 success criterion 2.4.3 (Focus Order). Affects CMS, XFP, CP
- Some pages contain elements which don’t appropriately reflow causing content to be obscured and require horizontal scrolling to access. This fails WCAG 2.1 success criterion 1.4.10 (Reflow). Affects XFP
- Some pages cannot be found through more than one type of navigation. This fails WCAG 2.1 success criterion 2.4.5 (Multiple Ways). Affects CMS, XFP, CXM, CP
- Some pages contain elements that have poor colour contrast. This fails WCAG 2.1 success criterion 1.4.1 (Use of Colour). Affects XFP
- Some pages use incorrect information in their labelling and/or help text, this makes it difficult for users to orient themselves and find the right content. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships). Affects XFP
- Some pages have HTML validation errors creating an unpredictable environment for assistive technology. This fails WCAG 2.1 success criterion 4.1.1 (Parsing). Affects CMS, XFP
- 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.1 success criterion 3.3.1 (Error identification). Affects CMS, XFP, CXM, CP
- Some pages allow items displayed in a table list to be reordered but don’t provide a way to reorder this without using a pointing device and a path based gesture. This fails WCAG 2.1 success criterion 2.5.1 (Pointer gestures). Affects XFP
- 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.1 success criterion 3.3.2 (Labels or Instructions). Affects CMS, XFP, CXM, CP
Disproportionate burden
We believe that fixing accessibility problems with some content would be disproportionate for the reasons provided.
Picking items from a select element to edit them
Some user interfaces in Jadu CMS use a non-standard pattern which provides a select element containing a list of items available to be edited, choosing an item from this list triggers a change of context where a form is populated with the item’s details, allowing them to be viewed and/or edited. See item 2 in the ‘Non-accessible content’ list above.
The user interfaces which use this pattern are gradually being transitioned to use separate accessible list and edit views, we believe that fixing the problems in the non-standard UI pattern would be disproportionate.
Google ReCaptcha is not sufficiently labelled
Some pages use ReCaptcha as a security or rate-limiting measure. The implementation of ReCaptcha is entirely out of Jadu’s control and any markup changes required to improve accessibility, however minor, are beyond Jadu’s control.
How we tested the software
We use the Web Content Accessibility Guidelines 2.1 level A and level AA to test how accessible Jadu Continuum Platform products are.
We use a combination of semi-automated accessibility tools to test the compliance of all user interfaces against any WCAG 2.1 criteria that can be programmatically tested. This includes, but is not limited to:
- SiteImprove Accessibility Checker
- Axe Accessibility Checker
- WAVE Evaluation Tool
- IBM Equal Access Accessibility Checked
Where video or animations are used, we use the Photosensitive Epilepsy Analysis Tool (PEAT) to identify seizure risks.
We used the Website Accessibility Conformance Evaluation Methodology (WCAG-EM) approach to decide a sample of pages to test against the remaining WCAG criteria that can’t be programmatically tested.
What we're doing to improve accessibility
Jadu product teams are urgently fixing content which fails to meet the Web Content Accessibility Guidelines version 2.1 AA standard. We will update this page for each new release of a Jadu product which fixes a documented issue.
