PrivX UI Accessibility Conformance Report
WCAG Edition
(Based on VPAT® Version 2.5Rev)
Name of Product/Version: PrivX v43 (Web UI)
Report Date: 02 March 2026
Product Description: PrivX is a privileged access management (PAM) solution for hybrid and multi-cloud environments. It supports password vaulting, password rotation, passwordless authentication, and session access workflows.
Contact Information: Not included in this report (see Notes).
Notes: The legal disclaimer in this document applies. The VPAT WCAG edition template (VPAT® 2.5Rev) includes WCAG 2.0, 2.1, and 2.2 rows; this report evaluates WCAG 2.1 and WCAG 2.2 criteria.
Evaluation Methods Used: Evaluation was conducted by an internal team of UI developers and UX specialists.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standards and guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A (No) Level AA (No) Level AAA (No) |
| Web Content Accessibility Guidelines 2.1 | Level A (Yes) Level AA (Yes) Level AAA (Yes) |
| Web Content Accessibility Guidelines 2.2 | 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.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) | Supports | PrivX UI is primarily text-based. Non-text content is limited to session-recording videos. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | PrivX does not provide prerecorded audio-only or video-only content. |
| 1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | PrivX does not provide prerecorded media with audio. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | PrivX does not provide prerecorded media with 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 does not include automatically playing audio content that requires user control. |
| 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 and 2.2) | Not Applicable | PrivX has no Character Key Shortcuts. |
| 2.2.1 Timing Adjustable (Level A) | Supports | Time-limited UI content is limited to toast notifications, which can be paused by pointer hover or keyboard focus. |
| 2.2.2 Pause, Stop, Hide (Level A) | Supports | Session recordings provide playback controls (play, pause, stop). Toast notifications can be paused on hover or keyboard focus. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Supports | No content in evaluated screens is known to flash more than three times in any one-second period. |
| 2.4.1 Bypass Blocks (Level A) | Supports | Large data views provide pagination and search/filtering to help users bypass repeated content. |
| 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 and 2.2) | Supports | All PrivX functionality is accessible with a single pointer and without path-based gestures. |
| 2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) | Supports | No uncancelable pointer-down events were identified in evaluated screens. |
| 2.5.3 Label in Name (Level A 2.1 and 2.2) | Supports | Accessible names of user interface components include visible labels where applicable. |
| 2.5.4 Motion Actuation (Level A 2.1 and 2.2) | 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.2.6 Consistent Help (Level A 2.2 only) | Supports | Help-related components follow a consistent order and interaction pattern across evaluated pages. |
| 3.3.1 Error Identification (Level A) | 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 where errors may be expected. |
| 3.3.2 Labels or Instructions (Level A) | Supports | Labels or instructions are provided when content requires user input. |
| 3.3.7 Redundant Entry (Level A 2.2 only) | Supports | Where forms reuse previously entered information, values are preserved after save operations or validation errors. |
| 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: name and role can be programmatically determined; states, properties, and values can be programmatically set; and notification of changes is available to user agents, including assistive technologies. |
Table 2: Success Criteria, Level AA
Notes:
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Not Applicable | PrivX does not include live audio content. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Not Applicable | PrivX does not include prerecorded audio or video content. |
| 1.3.4 Orientation (Level AA 2.1 and 2.2) | 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 and 2.2) | Supports | The purpose of each input field collecting information about the user can be programmatically determined. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | The default light theme meets contrast requirements in evaluated screens. The dark theme also meets contrast requirements in evaluated use cases. |
| 1.4.4 Resize text (Level AA) | Supports | Text can be resized up to 200% without assistive technology and without loss of content or functionality. This behavior is supported by standard browser capabilities. |
| 1.4.5 Images of Text (Level AA) | Not Applicable | PrivX does not use images of text except for logos and branding assets. |
| 1.4.10 Reflow (Level AA 2.1 and 2.2) | Not Applicable | Core workflows include dense data tables; reflow behavior varies by view. |
| 1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) | Supports | See 1.4.3 notes. |
| 1.4.12 Text Spacing (Level AA 2.1 and 2.2) | Supports | Text-spacing requirements are met in evaluated screens. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) | Supports | PrivX supports standard tooltips as content shown on hover. |
| 2.4.5 Multiple Ways (Level AA) | Supports | Primary pages provide multiple navigation options, including links and contextual navigation controls. |
| 2.4.6 Headings and Labels (Level AA) | Supports | Headings and labels describe a topic or purpose. |
| 2.4.7 Focus Visible (Level AA) | Supports | Interactive UI elements provide a visible keyboard focus indicator. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) | Supports | In evaluated use cases, keyboard focus remains visible and is not obscured by author-created content. |
| 2.5.7 Dragging Movements (Level AA 2.2 only) | Supports | Equivalent functionality is available without drag operations; dragging is an optional convenience in limited scenarios. |
| 2.5.8 Target Size (Minimum) (Level AA 2.2 only) | Supports | Interactive targets in evaluated screens are designed to meet the 24 by 24 CSS pixel minimum where required. |
| 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 repeated on multiple 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) | 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. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) | Supports | Authentication supports platform features such as passkeys and password managers. |
| 4.1.3 Status Messages (Level AA 2.1 and 2.2) | Supports | 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
Notes:
| 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 and 2.2) | 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) | Supports | The UI primarily uses high-contrast text styling in core screens, mainly dark text on a light background. |
| 1.4.7 Low or No Background Audio (Level AAA) | Supports | PrivX does not include background audio. |
| 1.4.8 Visual Presentation (Level AAA) | Not Evaluated | |
| 1.4.9 Images of Text (No Exception) (Level AAA) | Not Applicable | PrivX does not use images of text, except for the 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) | Supports | In evaluated workflows, users can continue core tasks without disruptive, non-essential interruptions from the UI. |
| 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 and 2.2) | Supports | Users receive a session-expiration warning before timeout. No data loss occurs during inactivity; however, unsaved or unsubmitted form input may not persist after final session expiration. |
| 2.3.2 Three Flashes (Level AAA) | Supports | Web pages do not contain content that flashes more than three times in any one-second period. |
| 2.3.3 Animation from Interactions (Level AAA 2.1 and 2.2) | Supports | Animations are limited and are not required to complete core tasks, except where essential to the interaction. |
| 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.4.12 Focus Not Obscured (Enhanced) (Level AAA 2.2 only) | Supports | When a user interface component receives keyboard focus, no part of the component is hidden by author-created content. |
| 2.4.13 Focus Appearance (Level AAA 2.2 only) | Supports | Focus appearance is determined by browser and operating-system settings together with application-defined focus styles. |
| 2.5.5 Target Size (Level AAA 2.1 and 2.2) | Supports | Primary interactive controls in evaluated screens are designed to meet a target size of at least 44 by 44 CSS pixels. |
| 2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 and 2.2) | Supports | Web content does not restrict use of input modalities available on a platform. |
| 3.1.3 Unusual Words (Level AAA) | Supports | PrivX UI text aims to use clear, direct language and to minimize idioms or unexplained jargon. |
| 3.1.4 Abbreviations (Level AAA) | 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) | Supports | No content requiring specific pronunciation to determine meaning was identified in evaluated UI text. |
| 3.2.5 Change on Request (Level AAA) | Supports | Context is changed only by user requests, not automatically. |
| 3.3.5 Help (Level AAA) | Supports | Context-sensitive help is available. |
| 3.3.6 Error Prevention (All) (Level AAA) | Supports | For submissions: reversible, checked, or confirmed (at least one). |
| 3.3.9 Accessible Authentication (Enhanced) (Level AAA 2.2 only) | Supports | A cognitive function test (such as remembering a password or solving a puzzle) is not required for authentication steps, except where an external identity provider outside PrivX control imposes such a requirement. |
Legal Disclaimer (Company)
This Voluntary Product Accessibility Template (VPAT) is provided for informational purposes and describes the identified product version as of the report date. It does not constitute a contractual commitment or legal warranty of compliance. Accessibility outcomes may vary depending on deployment configuration, integrations, customer content, and assistive-technology combinations. SSH may update this document as the product evolves. If accessibility issues are identified, please report them to SSH for review and remediation prioritization.