Jadu Accessibility Conformance Report International Edition (Based on VPAT ® Version 2.5)
Name of Product/Version:
Jadu Central 3.4.
Report Date:
15th August 2024
Product Description:
Jadu Central 3.4 is a solution that comprises both content (via web pages) and online forms. It enables you to manage content, forms, and data in one centralized place, on any device.
Contact Information:
- Phone: +44 (0)116 222 7242
- Email: support@jadu.net
Notes:
The scope of this ACR includes the front-end website templates as well as content and forms created using the authoring tool.
Evaluation Methods Used:
Jadu Central 3.4 was evaluated using Chrome and Safari on a MacBook Pro laptop running Mac OS 13.1. Assistive technologies used in this evaluation include the Voice Over screen reader, built in magnification functionality, as well as extensive manual testing and use of the keyboard to navigate and operate the site content and functionality. Additionally, some automated testing tools were used such as the AXE browser extension, the Site Improve browser extension and the IBM Equal Access accessibility checker browser extension.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A (Yes) Level AA (Yes) Level AAA (No) |
| Web Content Accessibility Guidelines 2.1 | Level A (Yes) Level AA (Yes) Level AAA (No) |
| Web Content Accessibility Guidelines 2.2 | Level A (Yes) Level AA (Yes) Level AAA (No) |
| Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 | (Yes) |
Terms
The terms used in the Conformance Level information are defined as follows:
- 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.
- Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.
WCAG 2.2 Report
Tables 1 and 2 also document conformance with Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: Form fields and buttons include labels. Images have capability for alternative text added by the user via the authoring tool. Authoring Tool: When uploading an image the user will be required to add alternative text. For data in charts or graphs, the product also allows for the display of the data in a semantically structured table. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The product does not contain any pre recorded audio-only or video-only media by default. Authoring Tool: The product allows users to embed externally hosted audio and video content. The content editor can be used to add textual alternatives. |
| 1.2.2 Captions (Prerecorded) (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The product does not contain prerecorded synchronized media. Authoring Tool: The product supports the provision of embedded captioned video. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The product does not contain prerecorded video content that would require audio description or a media alternative. Authoring Tool: The product allows users to embed externally hosted audio and video content. The content editor can be used to add textual alternatives. |
| 1.3.1 Info and Relationships (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Partially Supports Electronic Docs: Partially Supports Authoring Tool: Supports | Web: Semantic markup, headings, lists, WAI-ARIA landmarks, ARIA roles, properties and states are used to convey meaning and information to assistive technology. The site meets the requirements of 1.3.1 with one very specific exception: when an embedded form displays input-specific errors, the error text is not programmatically associated with the respective input. Note - this only affects form in embedded mode when embedded on another page, not forms in general. A fix for the issue is currently in progress and is expected to be released in future version of Jadu Central. Electronic Docs: There are two ways in which Jadu Central Forms generates PDFs and the accessibility of the generated PDFs varies according to the method used. PDF of the completed form, generated using a PDF form template: In this case, if you upload an accessible PDF form, the outputted PDF will retain any accessibility information in the original file. However, the user inputted form values will not currently be tagged. We are investigating whether it is possible to tag these values in the PDF output, though initial findings suggest it’s a limitation of the technology. Generated PDF file attachment: PDF file attachments are created using a different code library, and unfortunately at this point it does not support adding tags, and the developer has not given an expected date for when this functionality will be available: https://github.com/dompdf/dompdf/issues/2774. We are currently investigating whether improvements to accessibility can be made in the interim. Authoring Tool: The product allows for the creation of semantic and well structured content through the provision of semantic headings, lists, links and other content through the accessible content editor. The form builder outputs valid semantic markup and allows for the addition of accessible help and errors text to form inputs that work with screen readers. An in-product accessibility checker can also be used to test page content prior to going live, providing notifications against any issues including highlighting any headings to ensure proper nesting and any inputs with missing labels. |
| 1.3.2 Meaningful Sequence (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: Content is tagged, structured and ordered in a meaningful sequence so that a correct reading sequence can be programmatically determined. Authoring Tool: The product allows for the structuring of web pages through rows of widgets. The reordering of these rows does not change their meaning. |
| 1.3.3 Sensory Characteristics (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: Content, controls and components do not rely on sensory characteristics to convey purpose or meaning. Authoring Tool: The product allows for the creation of instructions that do not rely solely on sensory characteristics of components. |
| 1.4.1 Use of Color (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: Content, controls and components do not rely on color alone to convey meaning. Color may be used to add secondary visual cues but any information conveyed by color is also available in text. Authoring Tool: The product supports not using color as the sole means of conveying information. For any native output instances of color conveying information such as links or error text there is also an additional means of conveying the same information. |
| 1.4.2 Audio Control (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The product does not contain audio that plays automatically. Authoring Tool: The product does not provide the option for automatically playing audio content. |
| 2.1.1 Keyboard (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: All content and functionality, including forms, links, buttons, and other components, is keyboard accessible without requiring specific timings for individual keystrokes. Authoring Tool: All content output from the product is keyboard accessible. |
| 2.1.2 No Keyboard Trap (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: All content and controls are keyboard accessible and do not trap users within a subset of content. Authoring Tool: The content output from the product does not contain any keyboard traps. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web: The product does not contain any keyboard shortcuts relevant to this success criteria. Authoring Tool: The product does not provide the option for keyboard shortcuts relevant to this success criteria. |
| 2.2.1 Timing Adjustable (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: Session length and timeout can be configured within the product to meet the 20 hour exception. Authoring Tool: Session length and timeout can be configured within the product to meet the 20 hour exception. Additional options to allow the user to manually extend time limits are roadmapped. |
| 2.2.2 Pause, Stop, Hide (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The product does not contain any moving, blinking, scrolling or auto-updating content. Authoring Tool: The product does not natively provide the option for moving, blinking, scrolling, or auto-updating information. |
| 2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The product does not contain any flashing content. Authoring Tool: The product does not natively provide the option for flashing content. |
| 2.4.1 Bypass Blocks (Level A) Also applies to: Revised Section 508 501 (Web)(Software) – Does not apply to non-web software 504.2 (Authoring Tool) 602.3 (Support Docs) – Does not apply to non-web docs | Web: Supports Authoring Tool: Supports | Web: The product outputs ‘Skip to navigation’ and ‘Skip to content’ links to allow more direct access to the primary content of web pages. The provision of semantic links, headings and landmarks also allow users of assistive technologies to navigate to various sections of web pages with ease. Authoring Tool: Users are able to create semantic headings via the content editor tool. |
| 2.4.2 Page Titled (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: System generated pages have titles that describe the topic and purpose of each page. Pages created via the authoring tool use the user inputted page title. Authoring Tool: The product allows for users to create page titles that are descriptive of topic or purpose. |
| 2.4.3 Focus Order (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: Pages use a logical tab order that preserves meaning and operability. Authoring Tool: The product provides focus to elements in a logical tab order, supporting the order of the content arranged by the user in the product. |
| 2.4.4 Link Purpose (In Context) (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: Pages use descriptive link text. In some areas, the product provides supplementary visually hidden link text that provides further context for screen reader users. Authoring Tool: The product supports the creation of descriptive link text. |
| 2.5.1 Pointer Gestures (Level A 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web & Authoring Tool: All web content output from the product can be operated with single point activation and does not require path based or multipoint gestures. |
| 2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web & Authoring Tool: All functions of content output from the product supports activation occurring on the up-event when the user releases the pointer. No functionality is triggered on the down-event. |
| 2.5.3 Label in Name (Level A 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web: For user interface components natively output from the product, the visual name of the component is the accessible name of the component. Authoring Tool: For user created components, the name of the component can be configured by the user. |
| 2.5.4 Motion Actuation (Level A 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web: The product does not contain any functionality that uses or requires, device or user motion. Authoring Tool: The product does not natively provide the option for operation by device motion or user motion. |
| 3.1.1 Language of Page (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The language of each page can be programmatically determined via the use of the lang attribute and value on the html element. Authoring Tool: Pages created by the product programmatically convey the language of the page via the use of the lang attribute and value on the html element. |
| 3.2.1 On Focus (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The product does not contain any components that initiate a change of context on focus. Authoring Tool: The product does not natively output any components that initiates a change of context when focussed. |
| 3.2.2 On Input (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The product does not contain any components that initiate a change of context on input. Authoring Tool: The product does not natively output any component that initiates a change of context upon user input. |
| 3.2.6 Consistent Help (Level A 2.2 only) Revised Section 508 – Does not apply | Web: Supports | Web: Help mechanisms, where used, are consistently located in the same relative order across pages. |
| 3.3.1 Error Identification (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: Error text is shown next to each form input in an error state. Error text can be customized within the authoring tool. Authoring Tool: The product outputs accessible form input error text by default. Additionally, the product allows for the addition of customizable form input help and error text. |
| 3.3.2 Labels or Instructions (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: A label is provided for all input fields. Authoring Tool: The product supports the creation of descriptive labels and instructions for inputs by outputting the relevant <label> or <legend> element for all form inputs as well as providing the option for instructional help text for user inputs and form controls. |
| 3.3.7 Redundant Entry (Level A 2.2 only) Revised Section 508 – Does not apply | Web: Supports | Web: The product does not natively output any form that requires the user to enter the same information twice in one session, except where needed for security. |
| 4.1.1 Parsing (Level A) Applies to: WCAG 2.0 and 2.1 – Always answer ‘Supports’ WCAG 2.2 (obsolete and removed) - Does not apply Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Supports | For WCAG 2.0, 2.1, EN 301 549, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata. |
| 4.1.2 Name, Role, Value (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: All user interface components provide the relevant programmatic name, role and where relevant state information. Authoring Tool: The product outputs user interface components built with semantic HTML elements in support with WAI-ARIA so the name, role and value can be programmatically determined. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The product does not contain live synchronized media. Authoring Tool: The product does not contain live synchronized media. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The product does not contain prerecorded video content that would require audio description. Authoring Tool: The product supports the embedding of videos from multiple platforms where audio descriptions are provided. |
| 1.3.4 Orientation (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web: The product uses mobile first, responsive design and does not restrict its view and operation to a single orientation. Authoring Tool: The product natively outputs content that is mobile first and responsive to landscape or portrait orientations. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web: The product uses the relevant autocomplete attribute and value where inputs are scoped to. Authoring Tool: The product’s form builder allows for the addition of relevant autocomplete attribute functionality to forms that capture user details. Any natively output inputs scoped to the user from the product support the relevant input type and autocomplete attribute. |
| 1.4.3 Contrast (Minimum) (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web & Authoring Tool: The visual presentation of text across the product has a contrast ratio of 4.5:1 or greater. |
| 1.4.4 Resize text (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The product supports standard browser level zoom allowing text to be resized up to and beyond 200% without loss of content or functionality. Authoring Tool: The product outputs web content which supports standard browser level zoom allowing text to be resized up to and beyond 200% without loss of content or functionality. |
| 1.4.5 Images of Text (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: The product does not natively contain any images of text. Authoring Tool: The product provides a caption field when users upload images to encourage the provision of text that can be visually customized to the end user's requirements. |
| 1.4.10 Reflow (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web: Content is presented without loss of information or functionality and without requiring two dimensional scrolling. Datatables may maintain their tabular layout and use a horizontal scroll bar as is allowed by 1.4.10. Authoring Tool: The product outputs responsive web pages that reflows content to the viewport when set to 400% zoom or viewed on mobile (320px width) without the need of a horizontal scroll bar. Datatables may maintain their tabular layout and use a horizontal scroll bar as is allowed by 1.4.10. |
| 1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web: User interface components, focus indicators and graphics/icons have a contrast ratio of at least 3:1 against adjacent colors. Authoring Tool: The product supports the creation of user-interface components that have a contrast ratio of at least 3:1 against their background. |
| 1.4.12 Text Spacing (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web & Authoring Tool: Text content output from the product natively supports the adjustment of text content through line height, letter spacing, word spacing and paragraph spacing to user-defined text settings to the requirements of this success criteria. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web & Authoring Tool: The product does not natively output any content elements that are activated by hover or focus. |
| 2.4.5 Multiple Ways (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) – Does not apply to non-web software 504.2 (Authoring Tool) 602.3 (Support Docs) – Does not apply to non-web docs | Web: Supports Authoring Tool: Supports | Web: The platform provides configurable navigation links, search functionality and user configured page content allowing for various ways to structure content to meet the requirement. Authoring Tool: The product outputs websites with multiple ways to navigate the content through a main navigation menu and search controls. Users can also add further navigation controls through the addition of widgets such as the site map. |
| 2.4.6 Headings and Labels (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: Heading and labels provided natively by the product describe topic and purpose. Authoring Tool: The product supports the creation of user configurable headings and labels through the content editor and form builder. |
| 2.4.7 Focus Visible (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: Visual changes are applied to elements to indicate the current position of focus. Authoring Tool: Elements by the content editor or by the form builder that can gain keyboard focus display a focus indicator. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) Revised Section 508 – Does not apply | Web: Supports | Web: The product does not hide user interface components when receiving keyboard focus. |
| 2.5.7 Dragging Movements (Level AA 2.2 only) Revised Section 508 – Does not apply | Web: Supports | Web: All functionality that uses dragging movement for operation can be achieved by a single pointer without dragging. |
| 2.5.8 Target Size (Minimum) (Level AA 2.2 only) Revised Section 508 – Does not apply | Web: Supports | Web: The size of all interactive targets is 24px by 24px or greater. |
| 3.1.2 Language of Parts (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web & Authoring Tool: User generated content added via the content editor can be tagged with the relevant language attribute value. |
| 3.2.3 Consistent Navigation (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) – Does not apply to non-web software 504.2 (Authoring Tool) 602.3 (Support Docs) – Does not apply to non-web docs | Web: Supports Authoring Tool: Supports | Web: Navigation mechanisms are consistent across pages. Authoring Tool: The product natively outputs web pages with consistent navigation controls. These mechanisms occur in the same relative order throughout an output website. |
| 3.2.4 Consistent Identification (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) – Does not apply to non-web software 504.2 (Authoring Tool) 602.3 (Support Docs) – Does not apply to non-web docs | Web: Supports Authoring Tool: Supports | Web & Authoring Tool: The product natively outputs web pages with a consistent component layout across a user created website, including header, footer and navigation controls. Functional components are displayed and labeled consistently throughout. |
| 3.3.3 Error Suggestion (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web & Authoring Tool: The product’s form builder supports the addition of user created custom error text that meaningfully describe errors and can provide suggestions for the correction to be displayed to the user in text. If a user marks a form field as required in the product then the product will output an error message suggesting the requirement of a value in the input field. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs) | Web: Supports Authoring Tool: Supports | Web: User created forms include a final confirmation page listing the data entered. Authoring Tool: The form builder in the product natively outputs a review page for confirming data entered prior to final submission. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) Revised Section 508 – Does not apply | Web: Supports | Web: Cognitive function tests are not required for any step in the authentication process. Sign in credentials can be pasted into the respective inputs. Autocomplete attributes are used where security allows browser autocomplete. |
| 4.1.3 Status Messages (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web & Authoring Tool: Dynamically generated status messages are not used in the product. Success and error messages are displayed through a page reload. |
Table 3: Success Criteria, Level AAA
Notes: Not applicable. Jadu Central 3.4 was not evaluated for WCAG 2.2 Level AAA conformance.
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Supports | The product uses semantic HTML markup and WAI-ARIA attributes to describe and convey the identity, role, and state of user interface components to assistive technologies. Refer to the WCAG 2.X section for details. |
| 302.2 With Limited Vision | Supports | The product supports standard device and browser zoom, magnification and contrast adjustments. The product is compatible with assistive technology and supports the use of screen readers for the visually impaired. |
| 302.3 Without Perception of Color | Supports | The product does not use color as the only means of conveying information. Color is only used as a decorative or supplemental attribute of user interface components. |
| 302.4 Without Hearing | Not Applicable | The product does not include any audio-only features that require hearing to be used. |
| 302.5 With Limited Hearing | Not Applicable | The product does not include any audio-only features that require hearing to be used. |
| 302.6 Without Speech | Supports | The product does not require speech to operate or retrieve information. |
| 302.7 With Limited Manipulation | Supports | The product supports standard input mechanisms such as common keyboards and pointing devices. The user interface does not require fine motor skills or simultaneous actions. |
| 302.8 With Limited Reach and Strength | Supports | The product does not use simultaneous actions in either form as a method of operation or information retrieval. Interactions can be executed by standard events such as a tap or click. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | The product does not function in a way that is prohibitive to users with cognitive or learning impairment. |
Chapter 4: Hardware
Notes: The product is a web application and is not subject to the requirements of this section.
Chapter 5: Software
Notes: The product is a web application and is not subject to the requirements of this section.
Chapter 6: Support Documentation and Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 601.1 Scope | Heading cell – no response required | Heading cell – no response required |
| 602 Support Documentation | Heading cell – no response required | Heading cell – no response required |
| 602.2 Accessibility and Compatibility Features | Not Applicable | Not applicable as relates to Chapters 4 and 5. |
| 602.3 Electronic Support Documentation | Support | Support and platform documentation is available via dedicated websites. |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | Support Documentation is web based. |
| 603 Support Services | Heading cell – no response required | Heading cell – no response required |
| 603.2 Information on Accessibility and Compatibility Features | Supports | Information on the accessibility and compatibility features is provided via a separate documentation website. |
| 603.3 Accommodation of Communication Needs | Supports | Support is available partners and/or via our dedicated support portal. Additionally, our support team, contactable at support@jadu.net can accommodate individual communication needs. |
Legal Disclaimer (Company)
Jadu Central includes various settings with accessibility impact. Website templates and Portal pages are accessible at the point of delivery of the Jadu Central to the customer but changes made by the customer’s users may not adhere to accessibility best practices. In such cases, the responsibility for accessibility relies on the customer and in consideration for providing this report to you as requested it is accepted and understood that neither Jadu Inc. nor any Jadu Group Company shall be held liable in relation to any loss or damage sustained by any third party that may arise as result any claims in relation to the information provided in the Report.
This information is true and correct to the best of Jadu’s knowledge as of the date printed on the front page of this Report. This Report is supplied for customer evaluation purposes only. The contents of this Report do not constitute either legal advice, representation, warranty or guarantee regarding a person’s ability to comply with applicable accessibility requirements. Such a determination is the sole responsibility of the customer and its users. However, should you notice any issues, please report these to us so that they can be proactively addressed.