Jaggaer UK Accessibility Statement

This accessibility statement applies to the JAGGAER ONE solution

How accessible this website is

JAGGAER develops our solutions to be compliant with WCAG 2.1 AA standard.

We know that some parts of this website are not yet fully accessible in so far as the User must manually select the “Use Accessible Controls” option, and the “High Contrast Stylesheet” option, in order to fully access the content.

Users are therefore advised to enable both options in order to make the solution display fully accessible pages.

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille please contact our Global Customer Care team (see Contacting Global Customer Care).

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please contact our Global Customer Care team (see Contacting Global Customer Care)

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).

Contacting Global Customer Care

JAGGAER Global Customer Care provides support to Suppliers and nominated customer contacts. You can contact us through the channels shown on the portal homepage.

Technical information about this website’s accessibility

JAGGAER, on behalf of our UK public sector customers, are committed to making our platform accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

JAGGAER’s application Supports, and Supports with Exceptions, all applicable WCAG 2.1 A and AA guidelines as of May 17, 2021.

This website is therefore partially compliant with the Web Content Accessibility Guidelines version 2.1 standards, with the few exceptions listed below.

Support with exception content

The WCAG criteria listed below are not fully compliant in some areas of the platform unless the user selects the “Use Accessible Controls” option or the “High Contrast Stylesheet” option available on the User Preferences page or in the page headers.

With these options enabled, the platform will produce content compliant with all the WCAG criteria listed below:

1.1.1 Informative images/icons are missing alt text or have inaccurate alt text assigned.
1.3.1 Bold subheading text is missing subheading tags, and some layout tables are not coded correctly for screen readers.
1.4.11 Not all non-text elements automatically meet the minimum contrast requirements.

1.4.3 Some content/functionality is not automatically visible in High Contrast Mode, some text on specific backgrounds do not automatically have sufficient colour contrast.

2.1.1 “X” close buttons are not keyboard or screen reader operable.
2.4.3 Some visually hidden content is being spoken by screen readers; the Save button on the Registration page is not in its proper location on the page.
2.5.3 Some fields/select lists do not have permanently displayed or associated labels.
3.3.2 No instructions are provided for the purpose of red asterisks on the Registration page. Format requirements for date form fields filters are not permanently displayed.

Further exceptions present in some limited areas of the platform

1.3.1 Site is missing Aria landmarks like <main> and <footer>, and radio buttons are missing the fieldset legend grouping.
2.4.2 Page titles do not reflect the main subject or topic of the page and are not unique or meaningful.
2.4.3 Back-to-top link is spoken incorrectly by a screen-reader and does not send the keyboard focus back to the top of the page.
3.1.2 Language of page and language of parts missing required lang attributes with correct values.
3.3.1 Errors are not announced in forms when identified in Chrome browser.
4.1.2 Buttons/icons are missing a correct accessible name or state, table column headers are missing sorted state and incorrect title attributes, expand/collapse controls are missing aria-expanded=true/false state, aria-current is used incorrectly and aria tab pattern is coded incorrectly.

What we are doing to improve accessibility

We execute regular accessibility audits via specialised third-party companies, and we commit to plan and fix all issues found during the audits following a scaled approach depending on the issue severity and resolution complexity.

The last accessibility audit that we completed was in January 2021. This audit produced several mitigation activities that were planned and released in our 21.1 and 21.2 version releases.

We plan to complete addressing all the exceptions indicated above in the version release to be deployed at the end of Q1 2022 (i.e. version release 22.1).

We will then plan a new accessibility audit before the end of 2022 in order to assess the correct execution of the aforementioned plan.

JAGGAER are committed to receiving and evaluating all the accessibility issues found by our users and to addressing these issues where appropriate through a maintenance release or main version release – depending on the issue severity and resolution complexity.

Preparation of this accessibility statement

This statement was prepared on 29 September 2021.

The platform was last audited on the 21.1 version release in February 2021. The test was carried out by Criterion 508 Solutions, Inc.

We used a risk-based approach to identify the areas used most heavily by users, and to identify areas with the most important business-related functionality, in order to decide on the use cases for the accessibility audits. In any case, our platform uses centralised components to manage the display of all pages and page elements, so we are confident that the accessibility level will be consistent across the platform regardless of which use cases are audited.

Note that specific areas such as real-time Auction monitors and graphic Dashboards have been excluded from the accessibility audits because the features available in those pages are also available through alternative and fully accessible pages.

Users can obtain a copy of our full accessibility test report on demand using the contact information above.