PrivX Accessibility Conformance Report
(Based on VPAT Version 2.5)
Product Information
Name of Product: PrivX
Platform: Web
Product Description: PrivX is a scalable, cost-efficient, and highly automated privileged access management (PAM) solution for hybrid and multi-cloud environments, quantum-safe connections and any combination of password vaulting, rotation, and passwordless authentication.
Last update: 09.12.2024
Evaluation Methods Used: Evaluation is conducted by an internal group of UI developers and UX experts.
Applicable Standards/Guidelines
Standard/Guideline |
Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.1 | Level A (Yes) Level AA (Yes) Level AAA (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.1 Report
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations | ||
|---|---|---|---|---|
| 1.1.1 Non-text Content (Level A) | Supports | Normal PrivX usage has no non-text content, except videos for session recordings. | ||
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | PrivX has no pre-recorded video or audio. | ||
| 1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | PrivX has no prerecorded video or audio. | ||
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | PrivX has no pre-recorded video or audio. | ||
| 1.3.1 Info and Relationships (Level A) | Supports | Information, structure, and relationships can be programmatically determined and are available in text. | ||
| 1.3.2 Meaningful Sequence (Level A) | Supports | Correct reading sequence can be programmatically determined. | ||
| 1.3.3 Sensory Characteristics (Level A) | Supports | Color/Shape/Size is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element | ||
| 1.4.1 Use of Color (Level A) | Supports | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | ||
| 1.4.2 Audio Control (Level A) | Not Applicable | PrivX Web UI has no sounds shipped, so nothing to pause. | ||
| 2.1.1 Keyboard (Level A) | Supports | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. | ||
| 2.1.2 No Keyboard Trap (Level A) | Supports | Focus can be moved away from any UI component using only a keyboard interface. | ||
| 2.1.4 Character Key Shortcuts (Level A 2.1 only) | Not Applicable | PrivX has no Character Key Shortcuts. | ||
| 2.2.1 Timing Adjustable (Level A) | Partially Supports | Most time limits are adjustable or essential for secure usage. | ||
| 2.2.2 Pause, Stop, Hide (Level A) | Partially Supports | We have play/pause/stop functionality for sessions video records, but no pause for essential real-time happening UX functionality like toasts/alerts. | ||
| 2.3.1 Three Flashes or Below Threshold (Level A) | Supports | Web pages do not contain known places that flash more than three times in any one second. | ||
| 2.4.1 Bypass Blocks (Level A) | Supports | Most big blocks of data have paging and search/filtering. | ||
| 2.4.2 Page Titled (Level A) | Supports | Web pages have titles that describe topic or purpose. | ||
| 2.4.3 Focus Order (Level A) | Supports | Focusable components receive focus in an order that preserves meaning and operability. | ||
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context. | ||
| 2.5.1 Pointer Gestures (Level A 2.1 only) | Supports | All PrivX functionality is accessible with a single pointer and without path-based gestures. | ||
| 2.5.2 Pointer Cancellation (Level A 2.1 only) | Supports | There are no known places with uncancelable pointer-down events. | ||
| 2.5.3 Label in Name (Level A 2.1 only) | Partially Supports | Most names in PrivX UI have a label. | ||
| 2.5.4 Motion Actuation (Level A 2.1 only) | Not Applicable | There is no device motion related functionality. | ||
| 3.1.1 Language of Page (Level A) | Supports | The default human language of each Web page can be programmatically determined. | ||
| 3.2.1 On Focus (Level A) | Supports | When any component receives focus, it does not initiate a change of context. | ||
| 3.2.2 On Input (Level A) | Supports | Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. | ||
| 3.3.1 Error Identification (Level A) | Partially Supports | If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text for most of the UI where errors may be expected. | ||
| 3.3.2 Labels or Instructions (Level A) | Supports | Labels or instructions are provided when content requires user input. | ||
| 4.1.1 Parsing (Level A) | Supports | For WCAG 2.0, 2.1, and the EN 301 549, 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) | Supports | All user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. | ||
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations | ||
|---|---|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Not Applicable | PrivX has no live audio. | ||
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Not Applicable | PrivX ships without any pre-recorded audio or video. | ||
| 1.3.4 Orientation (Level AA 2.1 only) | Supports | Content does not restrict its view and operation to a single display orientation, such as portrait or landscape. | ||
| 1.3.5 Identify Input Purpose (Level AA 2.1 only) | Supports | The purpose of each input field collecting information about the user can be programmatically determined. | ||
| 1.4.3 Contrast (Minimum) (Level AA) | Partially Supports | The aim is to maintain contrast ratio over 4.5 for all product parts. | ||
| 1.4.4 Resize text (Level AA) | Supports | Text can be resized without assistive technology up to 200 percent without loss of content orfunctionality. This is supported by client’s browser itself. | ||
| 1.4.5 Images of Text (Level AA) | Not Applicable | PrivX ships without images of texts, except of company logo. | ||
| 1.4.10 Reflow (Level AA 2.1 only) | Not Applicable | Major parts of product are tables with data. Other parts of UI usually support reflow. | ||
| 1.4.11 Non-text Contrast (Level AA 2.1 only) | Partially Supports | Most parts of the product UI maintain a contrast ratio over 3:0. | ||
| 1.4.12 Text Spacing (Level AA 2.1 only) | Partially Supports | Most parts of of PrivX UI follow the principle. | ||
| 1.4.13 Content on Hover or Focus (Level AA 2.1 only) | Partially Supports | PrivX supports standard tooltips as content shown on hover. | ||
| 2.4.5 Multiple Ways (Level AA) | Supports | Most of the pages have unique user-readable and understandable link. | ||
| 2.4.6 Headings and Labels (Level AA) | Supports | Headings and labels describe topic or purpose. | ||
| 2.4.7 Focus Visible (Level AA) | Partially Supports | Most interactable elements have focus visible. | ||
| 3.1.2 Language of Parts (Level AA) | Supports | The human language of each passage or phrase in the content can be programmatically determined. | ||
| 3.2.3 Consistent Navigation (Level AA) | Supports | Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated. | ||
| 3.2.4 Consistent Identification (Level AA) | Supports | Components that have the same functionality within a set of Web pages are identified consistently. | ||
| 3.3.3 Error Suggestion (Level AA) | Partially Supports | Suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. | ||
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Not Applicable | PrivX does not ask users for financial or legal commitments. | ||
| 4.1.3 Status Messages (Level AA 2.1 only) | Partially Supports | In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. | ||
Table 3: Success Criteria, Level AAA
| Criteria | Conformance Level | Remarks and Explanations | ||
|---|---|---|---|---|
| 1.2.6 Sign Language (Prerecorded) (Level AAA) | Not Applicable | |||
| 1.2.7 Extended Audio Description (Prerecorded) (Level AAA) | Not Applicable | |||
| 1.2.8 Media Alternative (Prerecorded) (Level AAA) | Not Applicable | |||
| 1.2.9 Audio-only (Live) (Level AAA) | Not Applicable | |||
| 1.3.6 Identify Purpose (Level AAA 2.1 only) | Supports | In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined. | ||
| 1.4.6 Contrast (Enhanced) (Level AAA) | Partially Supports | Most parts are black on white text. | ||
| 1.4.7 Low or No Background Audio (Level AAA) | Supports | PrivX has no background audio. | ||
| 1.4.8 Visual Presentation (Level AAA) | Not Evaluated | |||
| 1.4.9 Images of Text (No Exception) (Level AAA) | Not Applicable | PrivX ships with no images of text, except of company logo. | ||
| 2.1.3 Keyboard (No Exception) (Level AAA) | Supports | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. There is no functionality requiring timings for keystrokes. | ||
| 2.2.3 No Timing (Level AAA) | Supports | Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. | ||
| 2.2.4 Interruptions (Level AAA) | Not Evaluated | |||
| 2.2.5 Re-authenticating (Level AAA) | Supports | When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. | ||
| 2.2.6 Timeouts (Level AAA 2.1 only) | Not Evaluated | |||
| 2.3.2 Three Flashes (Level AAA) | Supports | Web pages do not contain anything that flashes more than three times in any one second period. | ||
| 2.3.3 Animation from Interactions (Level AAA 2.1 only) | Partially Supports | There are almost no motion animations, with very minimal essential exceptions. | ||
| 2.4.8 Location (Level AAA) | Supports | Information about the user's location within a set of web pages is available. | ||
| 2.4.9 Link Purpose (Link Only) (Level AAA) | Supports | A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. | ||
| 2.4.10 Section Headings (Level AAA) | Supports | Section headings are used to organize the content. | ||
| 2.5.5 Target Size (Level AAA 2.1 only) | Partially Supports | The size of the target for pointer inputs is at least 44 by 44 CSS pixels. Usually we have a lot of data presented in one screen and can't afford using so big controls, also standard controls like checkboxes or dropdowns are smaller than 44px in height. | ||
| 2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 only) | Supports | Web content does not restrict use of input modalities available on a platform. | ||
| 3.1.3 Unusual Words (Level AAA) | Partially Supports | PrivX tries to always have clear language and never uses idioms or jargon. | ||
| 3.1.4 Abbreviations (Level AAA) | Partially Supports | A mechanism for identifying the expanded form or meaning of abbreviations is available. | ||
| 3.1.5 Reading Level (Level AAA) | Not Evaluated | |||
| 3.1.6 Pronunciation (Level AAA) | Not Evaluated | |||
| 3.2.5 Change on Request (Level AAA) | Supports | Context is changed only by user requests, not automatically. | ||
| 3.3.5 Help (Level AAA) | Partially Supports | Context-sensitive help is available. | ||
| 3.3.6 Error Prevention (All) (Level AAA) | Supports | For Web pages that require the user to submit information, at least one of the following is true: Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before inalizing the submission. | ||
Legal Disclaimer
This Voluntary Product Accessibility Template (VPAT) is provided for informational and promotional purposes only and does not constitute a legally binding claim of compliance. The information reflects the product as of the date of this report and does not necessarily cover subsequent new product versions. While SSH strives for accuracy and compliance with applicable accessibility standards, we can't guarantee all the information provided or our assessment of compliance to be accurate, complete, reliable or error-free in all respects. SSH also acknowledges that there may be instances of non-conformity. We encourage users to report any such instances to SSH so we can address them promptly. No liability is assumed for the accuracy of this document or the decisions made based on its content.