VPAT - Chromebook Accessibility Conformance Report
WCAG Edition (Based on VPAT® Version 2.5)
Name of Product: ScreenPal Chromebook App
Report Date: February 13th, 2025
Product Description: ScreenPal for Chromebook is a screen recording and video editing mobile software tool that can be launched via a mobile browser, or directly as an app on a ChromeOS device.
Contact information: [email protected]
Evaluation Methods Used: Accessibility testing as per WCAG 2.2 AA guidelines.
The evaluation was performed using below tools/ tests:
- Screen readers:
- ChromeVox on Chromebook/ ChromeOS
- Color contrast testing using Color Contrast Analyzer
- Keyboard-only
Notes:
The VPAT has been prepared based on the accessibility evaluation of the following pages/ flows:
- Screen Recording
- Screen Recording (with System Audio)
- Camera Recording
- Camera + Screen Recording
- Camera + Screen Recording (with Microphone)
- Videos screen
- Cut
- Filter
- Music
- Text
- Overlay
- Overlay - Sticker Library
- Overlay - My Images
- Narrate
- Speed
- Crop
- Effects
- Blur
- Rotate
- Add Videos or Photos
- Add Videos or Photos - Stock Library
- Add Videos or Photos - Camera Roll
- Add Videos or Photos - Existing Recording
- Upload video
- Login flow
- Settings screen
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.2 at https://www.w3.org/TR/WCAG22/ | Level AAA (No) Level AA (Yes) Level A (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.
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
| | |
|---|---|---|
Criteria | Conformance Level | Remarks and Explanations |
1.1.1 Non-text Content (Level A) | Partially Supports | Most images on the app contain relevant alternative text. Exceptions include:
|
Supports | No audio-only or video-only content is present on the app. | |
1.2.2 Captions (Prerecorded) (Level A) | Supports | No multimedia content is present on the app. |
Supports | No multimedia content is present on the app. | |
1.3.1 Info and Relationships (Level A) | Partially Supports | Most parts of the app have consistent headers and global table structures to establish clear information and relationships within the app. Screen readers properly identify most of the information available on the app. Visually impaired users are easily able to perceive the relationships between a particular element and its role. Exceptions include:
|
1.3.2 Meaningful Sequence (Level A) | Partially Supports | The sequence of most of the content present on the app is meaningful and appropriate and does not affect the meaning of the provided content. Exceptions include:
|
1.3.3 Sensory Characteristics (Level A) | Supports | No information is present on the app which is based on sensory characteristics such as shape, size, location, sound, etc. |
1.4.1 Use of Color (Level A) | Partially Supports | Color is not used as the only visual means of conveying most of the information, indicating an action, prompting a response, or distinguishing a visual element. Exceptions include:
|
1.4.2 Audio Control (Level A) | Supports | Appropriate controls are provided for the audio content present on the app. |
2.1.1 Keyboard (Level A) | Partially Supports | The app partially supports standard keyboard navigation and input functions. Exceptions include:
|
2.1.2 No Keyboard Trap (Level A) | Supports | Keyboard focus is moving sequentially throughout the app without the focus getting trapped in any section and it is convenient to access the functionality. |
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) | Supports | No functionalities are dependent on or controlled by character key shortcuts. |
2.2.1 Timing Adjustable (Level A) | Supports | There is no such activity present on the app where time needs to be adjusted or extended. |
2.2.2 Pause, Stop, Hide (Level A) | Supports | There is no such content present on the app that needs to be stopped, paused, or hidden. |
2.3.1 Three Flashes or Below Threshold (Level A) | Supports | There is no flashing content present on the app. |
2.4.1 Bypass Blocks (Level A) | Supports | A bypass mechanism for skipping to the main content is implemented. |
2.4.2 Page Titled (Level A) | Supports | Descriptive and correct page titles are present for pages throughout the app. |
2.4.3 Focus Order (Level A) | Partially Supports | The focus for most of the elements moves in a correct sequence order on the app from left to right and top to bottom. Exceptions include:
|
2.4.4 Link Purpose (In Context) (Level A) | Partially Supports | Most links are provided with appropriate link text and the user would be able to understand the purpose of the link from its link text. Exceptions include:
|
2.5.1 Pointer Gestures (Level A 2.1 and 2.2) | Supports | All functionalities present in the app can be operated with a single pointer without a path-based gesture unless a multipoint or path-based gesture is essential. |
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) | Supports | No down-event of the pointer is used in the app to execute any part of the action. |
2.5.3 Label in Name (Level A 2.1 and 2.2) | Supports | All labels on the app include text and the same text is defined in the code as well to assist speech recognition technologies. |
2.5.4 Motion Actuation (Level A 2.1 and 2.2) | Supports | No functionality is present on the app that is operable only by device motion. |
3.1.1 Language of Page (Level A) | Supports | The language attribute is correctly defined for the webpages. |
3.2.1 On Focus (Level A) | Supports | No interactive element is triggered automatically on receiving the focus. |
3.2.2 On Input (Level A) | Supports | Change of context does not happen when the user changes the setting of any input controls. |
3.2.6 Consistent Help (Level A 2.2 only) | Supports | A sufficient help mechanism is provided in a consistent place on multiple webpages. |
3.3.1 Error Identification (Level A) | Supports | Errors present on the app are notified to the users correctly. |
3.3.2 Labels or Instructions (Level A) | Partially Supports | Most parts of the app provide support for motor-impaired and cognitive users as the labels and instructions are provided for the form fields, which are clearly visible and readable to such users. Exceptions include:
|
3.3.7 Redundant Entry (Level A 2.2 only) | Supports | Users are not required to enter the same details in the same process multiple times. |
4.1.2 Name, Role, Value (Level A) | Partially Supports | Most of the app elements have a proper label associated with their role and the screen reader is recognizing them correctly with updated values as well. Exceptions include:
|
Table 2: Success Criteria, Level AA
| | |
|---|---|---|
Criteria | Conformance Level | Remarks and Explanations |
1.2.4 Captions (Live) (Level AA) | Supports | No live multimedia content is present on the app. |
1.2.5 Audio Description (Prerecorded) (Level AA) | Supports | No multimedia content is present on the app. |
1.3.4 Orientation (Level AA 2.1 and 2.2) | Supports | The app does not restrict its view and operation to a single display orientation. |
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) | Supports | Interactive fields on the app are clearly labeled to direct the user to enter the data expected in the fields. |
1.4.3 Contrast (Minimum) (Level AA) | Partially Supports | Most elements in the app adhere to minimum contrast standards. Exceptions include:
|
1.4.4 Resize text (Level AA) | Supports | The success criterion is not applicable. |
1.4.5 Images of Text (Level AA) | Supports | No information is conveyed to the user via an image of the text. |
1.4.10 Reflow (Level AA 2.1 and 2.2) | Supports | The success criterion is not applicable. |
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) | Partially Supports | Most of the app user interface components have a contrast ratio of at least 3:1 against adjacent color(s). Exceptions include:
|
1.4.12 Text Spacing (Level AA 2.1 and 2.2) | Supports | The success criterion is not applicable. |
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) | Partially Supports | Most of the content that is triggered by hover or focus is dismissible, hoverable, and persistent. Exceptions include:
|
2.4.5 Multiple Ways (Level AA) | Supports | The success criterion is not applicable. |
2.4.6 Headings and Labels (Level AA) | Partially Supports | Most of the headings and labels on the app provide sufficient detail of the content they are describing. Exceptions include:
|
2.4.7 Focus Visible (Level AA) | Partially Supports | Partial elements present in the app have focus visibility. Exceptions include: The focus Indicator is not visible globally on the interactive elements such as: - Save Location - Available Space - Clear Video Cache - Watch Tutorials, etc. |
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) | Partially Supports | Most of the elements that receive keyboard focus are at least partially visible upon receiving the focus. Exceptions include:
|
2.5.7 Dragging Movements (Level AA 2.2 only) | Supports | All actions that involve dragging, are provided with a simple pointer alternative. |
2.5.8 Target Size (Minimum) (Level AA 2.2 only) | Supports | All the interactive pointer targets are at least 24 by 24 CSS pixels or have sufficient spacing around them. |
3.1.2 Language of Parts (Level AA) | Supports | English is the primary and only language of the app. There are no phrases or sentences written in any other language, which need to be defined separately. |
3.2.3 Consistent Navigation (Level AA) | Supports | Navigational mechanisms are repeated on the app and occur in the same relative order each time they are repeated. Hence, consistent navigation is provided to the user. |
3.2.4 Consistent Identification (Level AA) | Supports | Components that provide the same functionality throughout the app can be easily identified by the user. |
3.3.3 Error Suggestion (Level AA) | Supports | The provided error messages are descriptive enough to understand the error and identify the location where they occur. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Supports | There are no critical forms available where error prevention is required. Error suggestions are enough to fill out the form and correct the errors. |
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) | Supports | No such authentication or login steps are present in the app. |
4.1.3 Status Messages (Level AA 2.1 and 2.2) | Partially Supports | Most of the updated content automatically notifies the visually impaired users via a screen reader. Exceptions include:
|