Possip Accessibility Conformance Report
Possip Accessibility Conformance Report
WCAG Edition
(Based on VPAT® Version 2.5)
Report Date: [November, 2024]
Name of Product/Version: Possip Pulse Check® Platform
Product Description: Possip Pulse Check® helps organizations quickly access actionable insights from stakeholders in over 100 languages. Working with over 1,000 organizations across 34 states, the platform provides multilingual Pulse Checks® and reports to capture trends, praise, and feedback in 100+ languages.
Contact Information: Accessibility Inquiries: support@possip.com
Notes
- This report applies to the current version of the Possip Pulse Check® platform available at https://weeklypossip.com.
- Evaluation considers features enabled by the AccessiBe accesswidget integrated into the platform
Evaluation Methods Used
This report is based on the following evaluation methods:
- Manual and automated testing of core platform workflows.
- Testing with tools such as Lighthouse for WCAG 2.1 compliance.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standards/guidelines:
|
Standard/Guideline |
Level A |
Level AA |
Level AAA |
|---|---|---|---|
|
Web Content Accessibility Guidelines 2.0 |
Yes |
Yes |
No |
|
Web Content Accessibility Guidelines 2.1 |
Yes |
Yes |
No |
|
Web Content Accessibility Guidelines 2.2 |
No |
No |
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 only be used in WCAG Level AAA criteria.
WCAG 2.x Report
Scope of Conformance
When reporting on conformance with the WCAG 2.x Success Criteria, the evaluation is scoped for:
- Full pages
- Complete processes
- Accessibility-supported ways of using technology, as documented in WCAG 2.x Conformance Requirements.
Additional Notes
- The AccessiBe accessWidget is used to support partial compliance with WCAG 2.1. Manual adjustments and evaluations were performed to ensure accurate reporting.
Table 1: Success Criteria, Level A
Notes:
|
Criteria |
Conformance Level |
Remarks and Explanations |
|||
|
1.1.1 Non-text Content (Level A) |
Partially Supports |
The AccessiBe widget cannot generate meaningful alt text but helps identify missing attributes |
|||
|
Does Not Support |
Requires text alternatives and transcripts, which are not provided by the AccessiBe widget |
||||
|
1.2.2 Captions (Prerecorded) (Level A) |
Does Not Support |
Captions must be manually added to synchronized media |
|||
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) |
Does Not Support |
Audio descriptions must be created and embedded manually |
|||
|
1.3.1 Info and Relationships (Level A) |
Partially Supports |
Information, structure, and relationships conveyed through presentation can be programmatically determined |
|||
|
1.3.2 Meaningful Sequence (Level A) |
Partially Supports |
Meaningful navigation sequences can be determined |
|||
|
1.3.3 Sensory Characteristics (Level A) |
Partially Supports |
Instructions do not rely solely on sensory characteristics |
|||
|
1.4.1 Use of Color (Level A) |
Supports |
The AccessiBe widget provides options for color adjustments and contrast settings |
|||
|
1.4.2 Audio Control (Level A) |
Partially Supports |
Limited to volume adjustments; cannot override autoplay content |
|||
|
2.1.1 Keyboard (Level A) |
Supports |
The AccessiBe widget ensures all functionality is operable via keyboard |
|||
|
2.1.2 No Keyboard Trap (Level A) |
Supports |
Prevents users from being trapped when navigating via keyboard |
|||
|
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) |
Supports |
Key shortcuts are not provided |
|||
|
2.2.1 Timing Adjustable (Level A) |
Does Not Support |
Does not provide controls for time-based content or settings |
|||
|
2.2.2 Pause, Stop, Hide (Level A) |
Supports |
Moving, blinking, scrolling, or auto-updating information is not part of the platform |
|||
|
2.3.1 Three Flashes or Below Threshold (Level A) |
Partially Supports |
Content design avoids flashing |
|||
|
2.4.1 Bypass Blocks (Level A) |
Partially Supports |
A mechanism is available to bypass blocks of content and widget supports navigation |
|||
|
2.4.2 Page Titled (Level A) |
Does Not Support |
Page titles must be added manually in the HTML |
|||
|
2.4.3 Focus Order (Level A) |
Supports |
The AccessiBe widget ensures focusable elements follow logical order |
|||
|
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 |
Pointer gestures are not part of the platform |
|||
|
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) |
Supports |
Pointer gestures are not part of the platform |
|||
|
2.5.3 Label in Name (Level A 2.1 and 2.2) |
Partially Supports |
Labels are regularly in names |
|||
|
2.5.4 Motion Actuation (Level A 2.1 and 2.2) |
Supports |
Platform does not have motion actuation |
|||
|
3.1.1 Language of Page (Level A) |
Partially Supports |
Default language of the page can be programmatically determined |
|||
|
3.2.1 On Focus (Level A) |
Supports |
Prevents unexpected context changes when focus shifts |
|||
|
3.2.2 On Input (Level A) |
Supports |
Users are advised of changes |
|||
|
3.2.6 Consistent Help (Level A 2.2 only) |
Partially Supports |
Help elements generally occur in same relative order |
|||
|
3.3.1 Error Identification (Level A) |
Supports |
Dynamically generates descriptive error messages. |
|||
|
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 |
Does not exist outside authentication workflow |
|||
|
4.1.1 Parsing (Level A) WCAG 2.0 and 2.1 – Always answer ‘Supports’ WCAG 2.2 (obsolete and removed) – Does not apply |
Supports |
For WCAG 2.0 and 2.1, 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) |
Partially Supports |
Application uses standard HTML controls |
|||
Table 2: Success Criteria, Level AA
Notes:
|
Criteria |
Conformance Level |
Remarks and Explanations |
|||
|
1.2.4 Captions (Live) (Level AA) |
Not Supported |
Platform does not generate captions for live audio or video |
|||
|
1.2.5 Audio Description (Prerecorded) (Level AA) |
Not Supported |
Platform does not provide audio descriptions for pre-recorded video content |
|||
|
1.3.4 Orientation (Level AA 2.1 and 2.2) |
Supports |
Platform adjusts content for different screen orientations |
|||
|
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) |
Partially Supports |
Form inputs have enhanced labels or placeholders |
|||
|
1.4.3 Contrast (Minimum) (Level AA) |
Supports |
AccessiBe provides customizable contrast settings to meet minimum contrast ratios |
|||
|
1.4.4 Resize text (Level AA) |
Supports |
Users can resize text up to 200% using the widget without loss of functionality or content |
|||
|
1.4.5 Images of Text (Level AA) |
Partially Supports |
Text is used wherever possible |
|||
|
1.4.10 Reflow (Level AA 2.1 and 2.2) |
Partially Supports |
Responsive design is used to manage reflow when necessary |
|||
|
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) |
Supports |
The widget includes features for enhancing contrast for non-text elements |
|||
|
1.4.12 Text Spacing (Level AA 2.1 and 2.2) |
Partially Supports |
Users can adjust text spacing via the widget |
|||
|
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) |
Partially Supports |
The widget improves focus handling but cannot control custom hover or focus states implemented in the base code |
|||
|
2.4.5 Multiple Ways (Level AA) |
Partially Supports |
Multiple navigation methods are provided, including breadcrumbs |
|||
|
2.4.6 Headings and Labels (Level AA) |
Partially Supports |
The widget can improve readability of headings, proper semantic HTML and clear labeling is also coded manually |
|||
|
2.4.7 Focus Visible (Level AA) |
Supports |
The widget ensures focus indicators are visible during navigation |
|||
|
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) |
Supports |
Focus elements are not obscured by other elements |
|||
|
2.5.7 Dragging Movements (Level AA 2.2 only) |
Supports |
Dragging gestures (sliders or maps) are not used in the platform |
|||
|
2.5.8 Target Size (Minimum) (Level AA 2.2 only) |
Supports |
Clickable elements have appropriate target sizes |
|||
|
3.1.2 Language of Parts (Level AA) |
Supports |
Language can be programmatically determined |
|||
|
3.2.3 Consistent Navigation (Level AA) |
Supports |
Platform has consistent navigation |
|||
|
3.2.4 Consistent Identification (Level AA) |
Supports |
Functionality of elements is identified |
|||
|
3.3.3 Error Suggestion (Level AA) |
Partially Supports |
Widget may help highlight input fields, error messages are generated |
|||
|
Supports |
Inputs are reversible, checked, and confirmed |
||||
|
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) |
Supports |
Support for password entry by password manager, or copy and paste of password exists |
|||
|
4.1.3 Status Messages (Level AA 2.1 and 2.2) |
Partially Supports |
Status messages are displayed |
|||
Table 3: Success Criteria, Level AAA
Notes:
|
Criteria |
Conformance Level |
||
|
2.4.8 Location (Level AAA) |
Not Evaluated |
||
|
2.4.9 Link Purpose (Link Only) (Level AAA) |
Not Evaluated |
||
|
2.4.10 Section Headings (Level AAA) |
Not Evaluated |
||
|
2.4.12 Focus Not Obscured (Enhanced) (Level AAA 2.2 only) |
Not Evaluated |
||
|
2.4.13 Focus Appearance (Level AAA 2.2 only) |
Not Evaluated |
||
|
2.5.5 Target Size (Level AAA 2.1 and 2.2) |
Not Evaluated |
||
|
2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 and 2.2) |
Not Evaluated |
||
|
3.1.3 Unusual Words (Level AAA) |
Not Evaluated |
||
|
3.1.4 Abbreviations (Level AAA) |
Not Evaluated |
||
|
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) |
Not Evaluated |
||
|
3.3.5 Help (Level AAA) |
Not Evaluated |
||
|
3.3.6 Error Prevention (All) (Level AAA) |
Not Evaluated |
||
|
3.3.9 Accessible Authentication (Enhanced) (Level AAA 2.2 only) |
Not Evaluated |
