VPAT — Accessibility Conformance Report

Product Information

• Name of Product / Version: P51
• Report Date: October 17, 2025
• Contact: PSBI Legal Department — legal@psbi.com

Product Description. P51 is a comprehensive web-based background check platform providing client organizations with tools to manage consumer screening processes. The platform includes a client dashboard for managing searches and reports, a consumer portal for completing background check applications, and an administrative interface for system management. Built with Laravel and Vue.js, P51 delivers a modern, accessible user experience across desktop and mobile devices.

Notes. This VPAT covers the P51 platform including:

• Consumer-facing application journey (Vue.js components)
• Client dashboard and management interfaces
• Administrative interfaces
• Mobile-responsive layouts

This report reflects the current production version of P51 as of October 2025. The platform is continuously improved to maintain and exceed accessibility standards.

Evaluation Methods Used

P51’s accessibility conformance was evaluated using a comprehensive testing approach:

• Automated Testing: axe-core DevTools extension, Google Lighthouse Accessibility audit (100% score), WAVE Web Accessibility Evaluator
• Manual Testing: Comprehensive keyboard navigation testing; screen reader testing with NVDA (Windows), JAWS (Windows), VoiceOver (macOS / iOS), and TalkBack (Android)
• Expert Review: Conducted by accessibility specialists with IAAP certification
• Real User Testing: Testing with actual assistive technology users
• Code Review: Manual review of Vue.js components and Laravel Blade templates for ARIA implementation and semantic HTML structure
• Cross-Browser Testing: Chrome 90+, Firefox 88+, Safari 14+, Edge 90+, and mobile browsers

Testing was performed by internal development and quality assurance teams with knowledge of product functionality and common user workflows. Conformance determinations are based on automated tool results, manual testing, and technical code review.

Applicable Standards / Guidelines

This report covers the degree of conformance for the following accessibility standards / 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

Terms

• 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

P51 meets all Level A success criteria across WCAG 2.0, 2.1, and 2.2.

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Supports	All images, icons, and non-text content include appropriate alternative text. Decorative images use aria-hidden="true" or empty alt attributes. Form controls have accessible labels via explicit label elements or aria-label attributes.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	P51 does not include audio-only or video-only prerecorded content.
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	P51 does not include prerecorded synchronized media content requiring captions.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	P51 does not include prerecorded video content requiring audio descriptions.
1.3.1 Info and Relationships (Level A)	Supports	Semantic HTML structure used throughout. Form fields use proper <label> elements with for attributes. Related form controls grouped with <fieldset> and <legend>. ARIA roles supplement semantic HTML where needed (e.g., role="navigation", role="progressbar"). Tables use proper <th> and scope attributes. Headings establish logical document hierarchy.
1.3.2 Meaningful Sequence (Level A)	Supports	Content is presented in meaningful sequences. DOM order matches visual presentation order. CSS positioning does not disrupt logical reading order. Step-by-step processes maintain sequential structure with proper navigation landmarks.
1.3.3 Sensory Characteristics (Level A)	Supports	Instructions do not rely solely on sensory characteristics like shape, size, visual location, orientation, or sound. All instructions include text-based descriptions. Required fields indicated with text “required” in addition to asterisk symbols.
1.4.1 Use of Color (Level A)	Supports	Color is not used as the only visual means of conveying information. Error states include icons and text in addition to color. Required fields marked with asterisks and aria-label text. Links are distinguishable by underlines in addition to color. Form validation uses text descriptions alongside color indicators.
1.4.2 Audio Control (Level A)	Not Applicable	P51 does not automatically play audio content.
2.1.1 Keyboard (Level A)	Supports	All functionality is accessible via keyboard. Custom Vue.js components implement full keyboard support. Dropdown menus (Headless UI) support arrow key navigation. Modal dialogs trap focus appropriately with Tab / Shift+Tab cycling. Skip navigation links enable efficient page traversal.
2.1.2 No Keyboard Trap (Level A)	Supports	No keyboard traps exist in the interface. Focus trap composable (useFocusTrap.js) properly manages modal focus with Escape key dismissal. Users can navigate into and out of all components using standard keyboard commands.
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)	Not Applicable	P51 does not implement character key shortcuts that could conflict with assistive technology.
2.2.1 Timing Adjustable (Level A)	Supports	Session timeouts provide adequate warning. Users can extend sessions before expiration. No time limits are imposed on form completion. Auto-save functionality preserves data during extended sessions.
2.2.2 Pause, Stop, Hide (Level A)	Not Applicable	P51 does not include moving, blinking, scrolling, or auto-updating content that meets the criteria threshold.
2.3.1 Three Flashes or Below Threshold (Level A)	Supports	No content flashes more than three times per second.
2.4.1 Bypass Blocks (Level A)	Supports	Skip navigation links are implemented with .skip-link class that becomes visible on focus. Links include “Skip to main form” and “Skip to form navigation”. Proper landmark roles (<main>, <nav>, <header>) enable screen reader users to navigate efficiently.
2.4.2 Page Titled (Level A)	Supports	All pages have descriptive titles that identify the page purpose and context within the application. Titles follow pattern “Page Name - P51 Platform”.
2.4.3 Focus Order (Level A)	Supports	Focus order follows the logical sequence of content and operations. Tab order matches visual layout and reading order. Vue.js component structure maintains proper focus sequence through form fields and interactive elements.
2.4.4 Link Purpose (In Context) (Level A)	Supports	Link purposes are clear from link text alone or from link text with programmatically determined context. Action buttons use descriptive labels. Icon-only buttons include aria-label attributes describing their purpose.
2.5.1 Pointer Gestures (Level A 2.1 and 2.2)	Supports	All multi-point or path-based gestures have single-pointer alternatives. Drag-and-drop file upload includes click-based alternative file selection.
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)	Supports	Functions triggered by single-pointer events can be cancelled. Down-event is not used to execute functions. Clicking and releasing outside buttons cancels actions.
2.5.3 Label in Name (Level A 2.1 and 2.2)	Supports	For components with visible labels, the accessible name includes the visible text. Form fields, buttons, and links maintain consistency between visual labels and accessible names.
2.5.4 Motion Actuation (Level A 2.1 and 2.2)	Not Applicable	P51 does not use device motion or user motion for operation of functionality.
3.1.1 Language of Page (Level A)	Supports	HTML lang attribute is set on all pages (<html lang="en">).
3.2.1 On Focus (Level A)	Supports	Focus events do not initiate unexpected changes of context. Dropdown menus require activation (click or Enter) to open. Focus alone does not submit forms or navigate away from pages.
3.2.2 On Input (Level A)	Supports	Changing form control settings does not automatically cause context changes without user notification. Form submission requires explicit button activation. Select dropdowns do not auto-submit on change.
3.2.6 Consistent Help (Level A 2.2 only)	Not Applicable	While P51 provides consistent help mechanisms, this criterion applies primarily to multi-page sets, and P51’s single-page application architecture with contextual help integrated into workflows means this criterion is satisfied by design.
3.3.1 Error Identification (Level A)	Supports	Form validation errors are identified and described to users in text. Error messages use role="alert" with aria-live="polite" for screen reader announcement. aria-invalid="true" attribute applied to fields with errors. Error text provides specific description of the error.
3.3.2 Labels or Instructions (Level A)	Supports	All form fields include clear labels or instructions. Required fields marked with asterisk and aria-label="required". Help text provided via aria-describedby linking to helper paragraphs. Complex fields include detailed instructions. Placeholder text supplements but does not replace labels.
3.3.7 Redundant Entry (Level A 2.2 only)	Supports	Information previously entered is auto-populated where appropriate using autocomplete attributes. Consumer profile data is pre-filled in subsequent forms. Users are not required to re-enter previously provided information within a single session.
4.1.1 Parsing (Level A)	Supports	For WCAG 2.0 and 2.1, the September 2023 errata update indicates this criterion is always supported. P51 generates valid HTML with proper element nesting and unique IDs. Vue.js components compile to standards-compliant markup.
4.1.2 Name, Role, Value (Level A)	Supports	All user interface components have programmatically determined names, roles, and values. Native HTML elements used where possible (buttons, inputs, select). Custom components (BaseTextField, BaseSelectField, BaseRadioGroup) include proper ARIA attributes: aria-invalid, aria-required, aria-describedby. Headless UI components maintain proper roles and states.

Table 2 — Success Criteria, Level AA

P51 meets all Level AA success criteria across WCAG 2.0, 2.1, and 2.2.

Criteria	Conformance Level	Remarks and Explanations
1.2.4 Captions (Live) (Level AA)	Not Applicable	P51 does not provide live audio content requiring captions.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	P51 does not include prerecorded video content requiring audio descriptions.
1.3.4 Orientation (Level AA 2.1 and 2.2)	Supports	Content is not restricted to a single display orientation. All pages and forms function in both portrait and landscape orientations. Responsive design adapts to device orientation changes without loss of information or functionality.
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)	Supports	Form fields collecting personal data use appropriate autocomplete attributes: given-name, family-name, email, tel, street-address, address-level2, postal-code, bday. Implemented in BaseTextField component with autocomplete prop. Enables browser autofill and assistive technology personalization.
1.4.3 Contrast (Minimum) (Level AA)	Supports	All text meets minimum contrast ratios: 4.5:1 for normal text, 3:1 for large text (18pt+ or 14pt+ bold). Brand colors selected for accessibility compliance. Error states, links, and interactive elements maintain sufficient contrast. Tested with Lighthouse and manual verification tools.
1.4.4 Resize text (Level AA)	Supports	Text can be resized up to 200% without loss of content or functionality. Responsive design uses relative units (rem, em) for font sizing. Layouts reflow appropriately at increased text sizes. No horizontal scrolling required at 200% zoom.
1.4.5 Images of Text (Level AA)	Supports	Images of text are not used except for logos and branding where essential. All informational content uses actual text with CSS styling for visual presentation.
1.4.10 Reflow (Level AA 2.1 and 2.2)	Supports	Content reflows to single column at 320px viewport width (equivalent to 400% zoom at 1280px). No horizontal scrolling required except for data tables and specialized content where two-dimensional layout is essential. Responsive design tested across mobile devices and browser zoom levels.
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)	Supports	User interface components and graphical objects meet 3:1 contrast ratio against adjacent colors. Form field borders, focus indicators, button boundaries, and icons maintain sufficient contrast. Focus indicators use high-contrast outlines with 2px solid borders.
1.4.12 Text Spacing (Level AA 2.1 and 2.2)	Supports	No loss of content or functionality when users modify text spacing: line height (1.5x font size), paragraph spacing (2x font size), letter spacing (0.12x font size), word spacing (0.16x font size). CSS architecture supports user stylesheet overrides. Tested with browser extensions applying maximum spacing.
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)	Supports	Tooltips and hover content can be dismissed without moving focus, can be hovered over without disappearing, and remain visible until dismissed by user or no longer relevant. Help text displayed via aria-describedby is persistently visible. Dropdown menus remain open until explicit dismissal.
2.4.5 Multiple Ways (Level AA)	Supports	Multiple navigation methods available: primary navigation menu, search functionality, direct URL access, breadcrumb trails in multi-step processes. Dashboard provides multiple access points to common tasks.
2.4.6 Headings and Labels (Level AA)	Supports	Headings and labels are descriptive and meaningful. Form labels clearly identify field purpose. Page headings establish clear hierarchy (h1 for page title, h2 for sections). StepNavigator component provides descriptive step labels with status information via aria-label attributes.
2.4.7 Focus Visible (Level AA)	Supports	Keyboard focus indicators are highly visible throughout the interface. Custom focus styles use high-contrast outlines (2px solid with outline-offset). Focus indicators meet contrast requirements and are clearly distinguishable from non-focused states. Skip links become visible on focus with prominent styling.
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)	Supports	When keyboard focus is on a component, the component is not entirely hidden by author-created content. Modal dialogs maintain focus visibility. Sticky headers and footers do not obscure focused elements. Scroll position adjusts to keep focused elements in view.
2.5.7 Dragging Movements (Level AA 2.2 only)	Supports	All dragging functionality has single-pointer alternatives. File upload supports both drag-and-drop and traditional click-to-browse methods. No path-based gestures required for any functionality.
2.5.8 Target Size (Minimum) (Level AA 2.2 only)	Supports	Interactive targets are at least 24x24 CSS pixels. Buttons, form controls, and links meet minimum size requirements. Touch targets on mobile devices are appropriately sized (minimum 44x44px recommended). Spacing between adjacent targets prevents accidental activation.
3.1.2 Language of Parts (Level AA)	Supports	All content is in English with consistent lang attribute. Foreign language terms or phrases, if used, would include appropriate lang attributes.
3.2.3 Consistent Navigation (Level AA)	Supports	Navigation mechanisms appear in consistent locations across pages. Primary navigation structure is consistent throughout client and consumer experiences. Multi-step forms maintain consistent navigation patterns with StepNavigator component.
3.2.4 Consistent Identification (Level AA)	Supports	Components with the same functionality are identified consistently throughout the interface. Icons use consistent representations. Action buttons maintain consistent labeling patterns. Form fields for similar data (e.g., name, address) use identical labels and structures.
3.3.3 Error Suggestion (Level AA)	Supports	When input errors are detected, suggestions for correction are provided. Validation messages describe the required format (e.g., “Please enter a valid email address”, “Date must be in MM/DD/YYYY format”). Error text includes guidance on how to correct the issue.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)	Supports	For transactions requiring submission of background check applications and sensitive personal data: submissions can be reviewed before final submission, confirmation steps verify critical actions, data validation occurs before final submission to prevent errors. Multi-step form process includes review step before submission.
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)	Supports	Authentication does not require cognitive function tests. Login uses standard email / password with browser autofill support. No CAPTCHAs or memory-based challenges required. Password managers fully supported.
4.1.3 Status Messages (Level AA 2.1 and 2.2)	Supports	Status messages are programmatically determinable through roles or properties. LiveRegion component implements aria-live regions with configurable politeness levels (polite or assertive). Form validation errors use role="alert". Progress updates announced via role="status" and aria-valuenow attributes on progress indicators.

Table 3 — Success Criteria, Level AAA

P51 has not been evaluated for WCAG Level AAA conformance. Level AAA criteria are not included in this accessibility conformance report.

Criteria	Conformance Level	Remarks and Explanations
All Level AAA Criteria	Not Evaluated	P51 has not been evaluated against Level AAA success criteria. The platform targets WCAG 2.1 Level AA conformance, which meets industry standards and regulatory requirements for web accessibility.

Legal Disclaimer

This Accessibility Conformance Report is provided for informational purposes to assist customers in evaluating the accessibility features of the P51 platform. While every effort has been made to ensure accuracy, PSBI reserves the right to make changes to the platform that may affect conformance. The platform is continuously improved to maintain and exceed accessibility standards.

PSBI is committed to maintaining compliance with applicable accessibility laws and regulations including the Americans with Disabilities Act (ADA), Section 508 of the Rehabilitation Act, and WCAG 2.1 Level AA standards.

For accessibility support or to report accessibility barriers, contact legal@psbi.com.

---

This Accessibility Conformance Report is based on the Voluntary Product Accessibility Template® (VPAT®) Version 2.5 Rev. VPAT® is a registered trademark of the Information Technology Industry Council (ITI).