Nexthink Infinity VPAT statement

Applicable Standards/Guidelines

This report covers the degree of conformance with 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)

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 be used only in WCAG 2.0 Level AAA.

WCAG 2.x Report

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

Notes:

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Does not support	There were multiple pages that had unlabelled form fields present throughout the website. On the homepage, there are 3 buttons labelled ‘actions’, screen reader users are unable to differentiate between these buttons.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not applicable
1.2.2 Captions (Prerecorded) (Level A)	Not applicable
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not applicable
1.3.1 Info and Relationships (Level A)	Does not support	There were multiple pages that had unlabelled form fields present throughout the website. On the homepage, there are 3 buttons labelled ‘actions’, screen reader users are unable to differentiate between these buttons. There are multiple pages on the website that contain an illogical heading structure. On the homepage, there are several non-image elements that have been given an image role. This role requires this element to include an alternative text. An aria-label should not be used as normal HTML is available. These elements are located within the graphs and are an issue on all pages where graphs are present. On the homepage there is a data table with empty TH cells, making it difficult for screen readers to understand the content. On the ‘Applications - Excel’ page, the ID of ‘time-frame-picker-menu’ is not found on the same page it is referenced. This issue is present across the applications pages.
1.3.2 Meaningful Sequence (Level A)	Supports
1.3.3 Sensory Characteristics (Level A)	Supports
1.4.1 Use of Color (Level A)	Supports
1.4.2 Audio Control (Level A)	Not applicable
2.1.1 Keyboard (Level A)	Supports
2.1.2 No Keyboard Trap (Level A)	Supports
2.1.4 Character Key Shortcuts (Level A 2.1 only)	Not applicable
2.2.1 Timing Adjustable (Level A)	Not applicable
2.2.2 Pause, Stop, Hide (Level A)	Not applicable
2.3.1 Three Flashes or Below Threshold (Level A)	Supports
2.4.1 Bypass Blocks (Level A)	Supports
2.4.2 Page Titled (Level A)	Supports
2.4.3 Focus Order (Level A)	Supports
2.4.4 Link Purpose (In Context) (Level A)	Supports
2.5.1 Pointer Gestures (Level A 2.1 only)	Not applicable
2.5.2 Pointer Cancellation (Level A 2.1 only)	Not applicable
2.5.3 Label in Name (Level A 2.1 only)	Does not support	There were multiple pages that had unlabelled form fields present throughout the website. On the homepage, there are 3 buttons labelled ‘actions’, screen reader users are unable to differentiate between these buttons.
2.5.4 Motion Actuation (Level A 2.1 only)	Not applicable
3.1.1 Language of Page (Level A)	Supports
3.2.1 On Focus (Level A)	Supports
3.2.2 On Input (Level A)	Supports
3.3.1 Error Identification (Level A)	Not applicable
3.3.2 Labels or Instructions (Level A)	Does not support	There were multiple pages that had unlabelled form fields present throughout the website. On the homepage, there are 3 buttons labelled ‘actions’, screen reader users are unable to differentiate between these buttons.
4.1.1 Parsing (Level A)	Not applicable	Criteria removed from WCAG 2.2
4.1.2 Name, Role, Value (Level A)	Supports

Table 2: Success Criteria, Level AA

Notes:

Criteria	Conformance Level	Remarks and Explanations
1.2.4 Captions (Live) (Level AA)	Not applicable
1.2.5 Audio Description (Prerecorded) (Level AA)	Not applicable
1.3.4 Orientation (Level AA 2.1 only)	Supports
1.3.5 Identify Input Purpose (Level AA 2.1 only)	Does not support	There were multiple pages that had unlabelled form fields present throughout the website. On the homepage, there is an empty button on the ‘Metric by’ Combo box. This issue is present on several pages throughout the site. On the homepage, there are 3 buttons labelled ‘actions’, screen reader users are unable to differentiate between these buttons.
1.4.3 Contrast (Minimum) (Level AA)	Supports
1.4.4 Resize text (Level AA)	Does not support	When increasing the text to 200% on the homepage, there is some overlapping and loss of content.
1.4.5 Images of Text (Level AA)	Not applicable
1.4.10 Reflow (Level AA 2.1 only)	Does not support	Nexthink Infinity doesn't support mobile view at this stage
1.4.11 Non-text Contrast (Level AA 2.1 only)	Supports
1.4.12 Text Spacing (Level AA 2.1 only)	Supports
1.4.13 Content on Hover or Focus (Level AA 2.1 only)	Supports
2.4.5 Multiple Ways (Level AA)	Supports
2.4.6 Headings and Labels (Level AA)	Supports
2.4.7 Focus Visible (Level AA)	Supports
3.1.2 Language of Parts (Level AA)	Not applicable
3.2.3 Consistent Navigation (Level AA)	Supports
3.2.4 Consistent Identification (Level AA)	Supports
3.3.3 Error Suggestion (Level AA)	Not applicable
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)	Not applicable
4.1.3 Status Messages (Level AA 2.1 only)	Supports