VPAT - MacOS App Accessibility Conformance Report

WCAG Edition
(Based on VPAT® Version 2.5)
Name of Product: 
ScreenPal MacOS App (https://Screenpal.com/) 
Report Date: 
November 4th, 2024
Product Description: 
ScreenPal is a screen recording and video editing software tool that can be launched directly from a browser.
Contact information: 
[email protected]﻿
Evaluation Methods Used: 
Accessibility testing as per WCAG 2.2 AA guidelines.
The evaluation was performed using the below tools/ tests:
Screen readers:
VoiceOver
Color contrast testing using Color Contrast Analyzer
Keyboard-only
﻿
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 A (Yes)
Level AA (Yes)
Level AAA (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.
Supports: The criterion is not relevant to the product.
Not Evaluated: The product has not been evaluated against the criterion.
﻿
Table 1: Success Criteria, Level A
Criteria
Conformance Level 
Remarks and Explanations
﻿1.1.1 Non-text Content(Level A)
Partially Supports
Images on the app mostly contain relevant alternative text.
Exceptions include:
The screen reader does not announce the alternative text for the 'ScreenPal' logo from the Story from Script screen.
﻿1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
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.
﻿1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Supports
No multimedia content is present on the app.
﻿1.3.1 Info and Relationships (Level A)
Partially Supports
The app mostly has 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 relationship between a particular element and its role. 
Exceptions include:
The text 'your description above... can help' associated with the 'description' edit field is not announced by the screen reader on the Story from the Script screen.
﻿1.3.2 Meaningful Sequence (Level A)
Partially Supports
The sequence of the content present on the app is mostly meaningful and appropriate and does not affect the meaning of the provided content.
Exceptions include:
The screen reader announces the hidden content behind the overlay on the Story from the Script screen.
An incorrect reading order is found on the Story from Script, Blank Storyboard, and Start from a Document screens.
The screen reader announces the hidden content after selecting the 'History' button on the Story from Script screen.
﻿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, in most cases, is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Exceptions include:
The links such as 'Need help' are not distinguished from the surrounding text other than the color on the Story from Script screen.
﻿1.4.2 Audio Control (Level A)
Supports
No audio content is present on the app that plays automatically for more than 3 seconds.
﻿2.1.1 Keyboard (Level A)
Partially Supports
The app mostly supports standard keyboard navigation and input functions (including swiping to move between input fields and pressing [Double tap] to make selections).
Exceptions include:
The 'Release notes' link is not focusable using the keyboard on the Story from Script screen.
The focus is not moving to the hoverable elements such as 'More Options' using the keyboard on the Storyboard From Project Manager screen.
The 'Screen Recorder' options are operable using the mouse alone, they are not accessible for the keyboard users on the Storyboard From Project Manager screen.
The 'X (Close)' button is operable using the mouse alone, it is not accessible to the keyboard users on the Draw on Screen screen.
﻿2.1.2 No Keyboard Trap(Level A)
Partially Supports
Keyboard focus is mostly moving sequentially throughout the app without the focus getting trapped in any section and it is convenient to access the functionality.
Exceptions include:
The screen reader focus gets stuck on the 'Exit Drawing' button on the Draw on Screen screen.
﻿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
The success criterion is not applicable.
﻿2.4.2 Page Titled (Level A)
Supports
The success criterion is not applicable.
﻿2.4.3 Focus Order (Level A)
Partially Supports
The focus mostly moves in a correct sequence order on the app from left to right and top to bottom.
Exceptions include:
The focus moves to the first element of the application instead of returning to the triggered 'Task' button on the Story from Script screen.
After dismissing any tooltip of the application, the focus shifts to the next interactive element instead of staying on the same element on the Story from Script screen.
The focus is moving to the hidden element after the button such as 'Easy Going Life' using the keyboard on the Sound Effect (In Video Editor) screen.
﻿2.4.4 Link Purpose (In Context) (Level A)
Supports
All links are provided with appropriate link text and the user would be able to understand the purpose of the link from its link text.
﻿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 multi-point 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 product inherits the language settings configured through the operating system.
﻿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
The success criterion is not applicable.
﻿3.3.1 Error Identification (Level A)
Supports
The success criterion is not applicable.
﻿3.3.2 Labels or Instructions (Level A)
Supports
The app provides 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.
﻿3.3.7 Redundant Entry (Level A 2.2 only)
Supports
The success criterion is not applicable.
﻿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 recognizes them correctly with updated values as well.
Exceptions include:
The screen reader does not announce the role and link text for the 'Learn more about creating a story' link on the Story from Script screen.
The 'selected' state for the 'US -English' option is not announced by the screen reader on the Story from Script screen.
The screen reader announces the incorrect role as 'Link' for the links such as 'View Pricing' on the Story from Script screen.
The screen reader does not announce the label for the 'Select a Year' combo box on the Story from Script screen.
﻿
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 success criterion is not applicable.
﻿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
The app mostly adheres to minimum contrast standards.

Exceptions include:
The text such as 'Need help' fails the color contrast ratio on the Story from Script screen.
The text such as '[email protected]' fails the color contrast ratio on the Story from Script screen.
The text such as 'Select' fails the color contrast ratio on the hover state on the Story from Script screen.
The date text such as '1' fails the color contrast ratio on the Story from Script screen.s
﻿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
The app user interface components mostly have a contrast ratio of at least 3:1 against adjacent color(s).
Exceptions include:
The focus outline of the elements such as 'Connect with Microsoft Teams' fails the color contrast ratio on the Story from Script screen.
Outline of the 'Checkbox' fails the color contrast ratio on the Story from Script screen.
The 'Accordion' icons fail the color contrast ratio on the Storyboard From Project Manager screen.
﻿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)
Supports
The content that is triggered by hover or focus is dismissible, hoverable, and persistent.
﻿2.4.5 Multiple Ways 
(Level AA)
Supports
The success criterion is not applicable.
﻿2.4.6 Headings and Labels (Level AA)
Partially
Supports
Headings and labels on the app mostly provide sufficient detail of the content they are describing.
Exceptions include:
An insufficient label is announced for 'Select' button on the Story from Script, Blank Storyboard, and, Start from a Document.
The screen reader announces the insufficient label for the button as 'A S' instead of 'Profile and Personal Settings' on the Story from Script screen.
An insufficient label provided to the 'More options' button on the Storyboard From Project Manager screen.
An insufficient label is announced for the 'Select' buttons on the Start from a Document screen.
﻿2.4.7 Focus Visible (Level AA)
Partially
Supports
Most of the elements present in the app have focus visibility.
Exceptions include:
The focus indicator is not available on the 'Show' dropdown using the keyboard on the Storyboard From Project Manager screen.
The focus indicator is not available on the 'X (Close)' and 'Slider' buttons using the keyboard on the Storyboard From Project Manager screen.
The focus indicator is not available on the elements like 'Erase All' using the keyboard on the Draw on Screen screen.
﻿2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)
Supports
All elements that receive keyboard focus are at least partially visible upon receiving the focus.
﻿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)
Partially
Supports
The app mostly inherits the language settings configured through the operating system.
Exceptions include:
Language of parts in languages other than English is not announced on the Story from Script screen.
﻿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 success criterion is not applicable.
﻿3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
 Supports
The success criterion is not applicable.
﻿3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
Supports
The success criterion is not applicable.
﻿4.1.3 Status Messages 
(Level AA 2.1 and 2.2)
Partially
Supports
The updated content automatically notifies the visually impaired users via a screen reader in most of the cases.
Exceptions include:
The screen reader does not announce the notification as 'Submitting error report...' after selecting the 'Submit' button on the Story from Script screen.
The screen reader does not announce the 'Requesting music...' notification automatically when it appears on the screen on the Sound Effect(In Video Editor) screen.
The screen reader remains silent when the user sorts the videos in 'Ascending/ Descending' order on the Storyboard From Project Manager screen.
﻿

Standard/Guideline	Included in Report
Web Content Accessibility Guidelines 2.2 at https://www.w3.org/TR/WCAG22/	Level A (Yes) Level AA (Yes) Level AAA (No)

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content(Level A)	Partially Supports	Images on the app mostly contain relevant alternative text. Exceptions include: The screen reader does not announce the alternative text for the 'ScreenPal' logo from the Story from Script screen.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	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.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Supports	No multimedia content is present on the app.
1.3.1 Info and Relationships (Level A)	Partially Supports	The app mostly has 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 relationship between a particular element and its role. Exceptions include: The text 'your description above... can help' associated with the 'description' edit field is not announced by the screen reader on the Story from the Script screen.
1.3.2 Meaningful Sequence (Level A)	Partially Supports	The sequence of the content present on the app is mostly meaningful and appropriate and does not affect the meaning of the provided content. Exceptions include: The screen reader announces the hidden content behind the overlay on the Story from the Script screen. An incorrect reading order is found on the Story from Script, Blank Storyboard, and Start from a Document screens. The screen reader announces the hidden content after selecting the 'History' button on the Story from Script screen.
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, in most cases, is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Exceptions include: The links such as 'Need help' are not distinguished from the surrounding text other than the color on the Story from Script screen.
1.4.2 Audio Control (Level A)	Supports	No audio content is present on the app that plays automatically for more than 3 seconds.
2.1.1 Keyboard (Level A)	Partially Supports	The app mostly supports standard keyboard navigation and input functions (including swiping to move between input fields and pressing [Double tap] to make selections). Exceptions include: The 'Release notes' link is not focusable using the keyboard on the Story from Script screen. The focus is not moving to the hoverable elements such as 'More Options' using the keyboard on the Storyboard From Project Manager screen. The 'Screen Recorder' options are operable using the mouse alone, they are not accessible for the keyboard users on the Storyboard From Project Manager screen. The 'X (Close)' button is operable using the mouse alone, it is not accessible to the keyboard users on the Draw on Screen screen.
2.1.2 No Keyboard Trap(Level A)	Partially Supports	Keyboard focus is mostly moving sequentially throughout the app without the focus getting trapped in any section and it is convenient to access the functionality. Exceptions include: The screen reader focus gets stuck on the 'Exit Drawing' button on the Draw on Screen screen.
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	The success criterion is not applicable.
2.4.2 Page Titled (Level A)	Supports	The success criterion is not applicable.
2.4.3 Focus Order (Level A)	Partially Supports	The focus mostly moves in a correct sequence order on the app from left to right and top to bottom. Exceptions include: The focus moves to the first element of the application instead of returning to the triggered 'Task' button on the Story from Script screen. After dismissing any tooltip of the application, the focus shifts to the next interactive element instead of staying on the same element on the Story from Script screen. The focus is moving to the hidden element after the button such as 'Easy Going Life' using the keyboard on the Sound Effect (In Video Editor) screen.
2.4.4 Link Purpose (In Context) (Level A)	Supports	All links are provided with appropriate link text and the user would be able to understand the purpose of the link from its link text.
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 multi-point 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 product inherits the language settings configured through the operating system.
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	The success criterion is not applicable.
3.3.1 Error Identification (Level A)	Supports	The success criterion is not applicable.
3.3.2 Labels or Instructions (Level A)	Supports	The app provides 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.
3.3.7 Redundant Entry (Level A 2.2 only)	Supports	The success criterion is not applicable.
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 recognizes them correctly with updated values as well. Exceptions include: The screen reader does not announce the role and link text for the 'Learn more about creating a story' link on the Story from Script screen. The 'selected' state for the 'US -English' option is not announced by the screen reader on the Story from Script screen. The screen reader announces the incorrect role as 'Link' for the links such as 'View Pricing' on the Story from Script screen. The screen reader does not announce the label for the 'Select a Year' combo box on the Story from Script screen.

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 success criterion is not applicable.
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	The app mostly adheres to minimum contrast standards. Exceptions include: The text such as 'Need help' fails the color contrast ratio on the Story from Script screen. The text such as '[email protected]' fails the color contrast ratio on the Story from Script screen. The text such as 'Select' fails the color contrast ratio on the hover state on the Story from Script screen. The date text such as '1' fails the color contrast ratio on the Story from Script screen.s
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	The app user interface components mostly have a contrast ratio of at least 3:1 against adjacent color(s). Exceptions include: The focus outline of the elements such as 'Connect with Microsoft Teams' fails the color contrast ratio on the Story from Script screen. Outline of the 'Checkbox' fails the color contrast ratio on the Story from Script screen. The 'Accordion' icons fail the color contrast ratio on the Storyboard From Project Manager screen.
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)	Supports	The content that is triggered by hover or focus is dismissible, hoverable, and persistent.
2.4.5 Multiple Ways (Level AA)	Supports	The success criterion is not applicable.
2.4.6 Headings and Labels (Level AA)	Partially Supports	Headings and labels on the app mostly provide sufficient detail of the content they are describing. Exceptions include: An insufficient label is announced for 'Select' button on the Story from Script, Blank Storyboard, and, Start from a Document. The screen reader announces the insufficient label for the button as 'A S' instead of 'Profile and Personal Settings' on the Story from Script screen. An insufficient label provided to the 'More options' button on the Storyboard From Project Manager screen. An insufficient label is announced for the 'Select' buttons on the Start from a Document screen.
2.4.7 Focus Visible (Level AA)	Partially Supports	Most of the elements present in the app have focus visibility. Exceptions include: The focus indicator is not available on the 'Show' dropdown using the keyboard on the Storyboard From Project Manager screen. The focus indicator is not available on the 'X (Close)' and 'Slider' buttons using the keyboard on the Storyboard From Project Manager screen. The focus indicator is not available on the elements like 'Erase All' using the keyboard on the Draw on Screen screen.
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)	Supports	All elements that receive keyboard focus are at least partially visible upon receiving the focus.
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)	Partially Supports	The app mostly inherits the language settings configured through the operating system. Exceptions include: Language of parts in languages other than English is not announced on the Story from Script screen.
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 success criterion is not applicable.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)	Supports	The success criterion is not applicable.
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)	Supports	The success criterion is not applicable.
4.1.3 Status Messages (Level AA 2.1 and 2.2)	Partially Supports	The updated content automatically notifies the visually impaired users via a screen reader in most of the cases. Exceptions include: The screen reader does not announce the notification as 'Submitting error report...' after selecting the 'Submit' button on the Story from Script screen. The screen reader does not announce the 'Requesting music...' notification automatically when it appears on the screen on the Sound Effect(In Video Editor) screen. The screen reader remains silent when the user sorts the videos in 'Ascending/ Descending' order on the Storyboard From Project Manager screen.

VPAT - Windows App Accessibility Conformance Report

VPAT - iOS App Accessibility Conformance Report

VPAT - MacOS App Accessibility Conformance Report

Table 1: Success Criteria, Level A

﻿

Table 2: Success Criteria, Level AA