Product Information
Product: Your SaaS Product
Product Description: We’re on a mission to improve enrollment marketing while empowering students to make confident choices.
Date: September 2025
Contact: support@truleague.com
Evaluation Methods Used: The accessibility evaluation of the SaaS web lesson included direct inspection by software testers, keyboard-only navigation, and manual testing with assistive technology. The web application was tested using a web browser on a Windows desktop computer using Chrome and FireFox with NVDA ,Firefox using Jaws Mac using VoiceOver on Safari and Chrome browser, iOS using Voiceover on Safari browser, and Android using Talkback on Chrome browser.
Conformance to WCAG 2.0 Level AA satisfies the Revised Section 508 web content requirements
“Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information Technology Industry Council (ITI).
Applicable Standards/Guidelines
| Standard/Guideline | Included in Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A, Level AA |
| Web Content Accessibility Guidelines 2.1 | Level A, Level AA |
| Web Content Accessibility Guidelines 2.2 | Level A, Level AA |
Terms
- Supports: At least one method fully meets the criterion without known defects (or via equivalent facilitation).
- Partially Supports: Some functionality does not fully meet the criterion.
- Does Not Support: Most functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
WCAG 2.2 – Level A
| Criteria | Conformance Level | Remarks / Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | All frames and images have accessible names. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | This criterion is not relevant to the product. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | This criterion is not relevant to the product. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | This criterion is not relevant to the product. |
| 1.3.1 Info and Relationships | Supports | All structural elements such as headings, lists, and form fields are programmatically defined, ensuring that screen reader users can perceive the correct relationships |
| 1.3.2 Meaningful Sequence | Supports | Content is structured with proper HTML semantics and ARIA markup so that assistive technologies convey information in the correct order |
| 1.3.3 Sensory Characteristics | Supports | Instructions should not rely solely on sensory cues such as shape, color, size, visual location, or sound to be understood |
| 1.4.1 Use of Color | Supports | Content is structured with proper HTML semantics and ARIA markup so that assistive technologies convey information in the correct order |
| 1.4.2 Audio Control | Not Applicable | This criterion is not relevant to the product. |
| 2.1.1 Keyboard | Supports | All interactive elements, menus, and navigation are operable using only the keyboard. |
| 2.1.2 No Keyboard Trap | Supports | Focus can be moved into and away from all interface components using the keyboard without trapping the user |
| 2.5.1 Pointer Gestures | Not Applicable | This criterion is not relevant to the product. |
| 2.5.2 Pointer Cancellation | Supports | Most pointer interactions (like clicks and taps) are triggered on release, allowing users to cancel actions by moving away before lifting |
| 2.5.3 Label in Name | Supports | The accessible name for components matches or contains the visible label for voice-control compatibility |
| 2.5.4 Motion Actuation | Not Applicable | This criterion is not relevant to the product. |
| 2.2.1 Timing Adjustable | Not Applicable | This criterion is not relevant to the product. |
| 2.2.2 Pause, Stop, Hide | Not Applicable | This criterion is not relevant to the product. |
| 2.3.1 Three Flashes or Below Threshold | Not Applicable | This criterion is not relevant to the product. |
| 2.4.1 Bypass Blocks | Partially Supports | Minimal repeated navigation; no explicit skip link; impact is low but a skip link is recommended. |
| 2.4.2 Page Titled | Supports | Each page includes a descriptive and unique title that identifies its purpose |
| 2.4.3 Focus Order | Supports | Interactive components receive focus in a logical and predictable order that preserves meaning and operability |
| 2.4.4 Link Purpose (In Context) | Supports | Links clearly describe their purpose |
| 3.1.1 Language of Page | Supports | The default language of each page is correctly identified in the HTML lang attribute |
| 3.2.1 On Focus | Supports | Elements do not trigger unexpected changes in context when they receive focus |
| 3.2.2 On Input | Supports | User input does not automatically trigger context changes without warning |
| 3.3.1 Error Identification | Supports | When input errors are detected, they are clearly indicated with accessible text |
| 4.1.2 Name, Role, Value | Supports | All interactive components expose appropriate name, role, state, and value information programmatically. |
| 3.2.6 Consistent Help | Supports | A consistent “Tech Support” option is available on every page of the platform, ensuring users can easily access assistance whenever needed |
| 3.3.7 Redundant Entry | Supports | The platform prevents users from having to re-enter information that has already been provided, ensuring they do not need to input the same data multiple times |
WCAG 2.2 – Level AA
| Criteria | Conformance Level | Remarks / Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | This criterion is not relevant to the product. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | This criterion is not relevant to the product. |
| 1.3.4 Orientation | Not Applicable | The Web application works in both portrait and landscape modes without loss of content or functionality |
| 1.3.5 Identify Input Purpose | Supports | Input fields use semantic HTML and programmatic labels so their purpose can be determined by assistive technologies |
| 1.4.3 Contrast (Minimum) | Supports | All text meets or exceeds the 4.5:1 contrast ratio; large text meets 3:1 contrast |
| 1.4.4 Resize Text | Not Applicable | Text can be resized up to 200% using browser zoom or assistive technology without loss of functionality |
| 1.4.5 Images of Text | Supports | No images of text are used in the platform, except for essential branding or logos |
| 1.4.10 Reflow | Does Not Support | Most pages reflow correctly up to 400% zoom and on small screen sizes, maintaining readability without horizontal scrolling. Some complex layouts may require horizontal scrolling in certain views |
| 1.4.11 Non-Text Contrast | Supports | Essential icons, controls, and graphical indicators maintain sufficient contrast against adjacent colors |
| 1.4.12 Text Spacing | Not Applicable | This criterion is not relevant to the product. |
| 1.4.13 Content on Hover or Focus | Supports | Tooltips, dropdowns, and hover/focus content remain visible until dismissed and are accessible by keyboard |
| 2.4.5 Multiple Ways | Partially Supports | Multiple navigation mechanisms (menu, search) are provided to locate content |
| 2.4.6 Headings and Labels | Supports | Headings and form labels are descriptive and help users understand structure and purpose |
| 2.4.7 Focus Visible | Supports | Focus indicators are consistently visible when navigating via keyboard with assistive technology such as Narrator/NVDA . |
| 3.1.2 Language of Parts | Supports | The platform allows users to translate incoming messages into their preferred language |
| 3.2.3 Consistent Navigation | Supports | Navigation mechanisms (menu items, placement, labels) are presented consistently across pages |
| 3.2.4 Consistent Identification | Supports | Interactive components with the same function are identified consistently throughout the platform |
| 3.3.3 Error Suggestion | Supports | When a user makes an input error, helpful text suggestions are provided to assist in correction |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Partially Supports | This criterion is not relevant to the product. |
| 4.1.3 Status Messages | Supports | Status messages are announced without moving focus. |
| 2.4.11 Focus Not Obscured (Minimum) (New in 2.2) | Supports | When navigating with a keyboard, focused elements remain at least partially visible on the screen and are not completely hidden by headers, footers, or other fixed content |
| 2.5.7 Dragging Movements (New in 2.2) | Not Applicable | This criterion is not relevant to the product. |
| 2.5.8 Target Size (Minimum) (New in 2.2) | Partially Supports | Most controls meet the minimum target size, but a few smaller elements do not. |
| 3.3.8 Accessible Authentication (Minimum) (New in 2.2) | Supports | The platform’s authentication process allows copy/paste in login fields and supports simple alternatives such as one-time passcodes, ensuring users are not required to memorize or solve cognitive tasks |
App Report
Product Information
Product: Your SaaS Product – Mobile App
Product Description: Native mobile experience aligned with the web platform to improve enrollment marketing outcomes.
Date: September 2025
Contact: support@truleague.com
Evaluation Methods
Manual testing with VoiceOver on iOS (Safari/native) and TalkBack on Android (Chrome/native), including keyboard alternatives where applicable, screen reader gestures, and system font/contrast settings.
Adapt this section if the native app evaluation scope differs from web.
WCAG 2.2 – Level A
| Criteria | Conformance Level | Remarks / Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | All Frames and images have an accessible name. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | This criterion is not relevant to the product. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | This criterion is not relevant to the product. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | This criterion is not relevant to the product. |
| 1.3.1 Info and Relationships | Supports | All structural elements such as headings, lists, and form fields are programmatically defined, ensuring that screen reader users can perceive the correct relationships |
| 1.3.2 Meaningful Sequence | Supports | Content is structured with proper HTML semantics and ARIA markup so that assistive technologies convey information in the correct order. |
| 1.3.3 Sensory Characteristics | Supports | Instructions should not rely solely on sensory cues such as shape, color, size, visual location, or sound to be understood. |
| 1.4.1 Use of Color | Supports | Content is structured with proper HTML semantics and ARIA markup so that assistive technologies convey information in the correct order. |
| 1.4.2 Audio Control | Not Applicable | This criterion is not relevant to the product. |
| 2.1.1 Keyboard | Partially Supports | Most interactive elements are operable using only the keyboard; however, some components require pointer input or have inconsistent focus behavior, limiting full keyboard accessibility. |
| 2.1.2 No Keyboard Trap | Does Not Support | Some interactive components trap keyboard focus, preventing users from moving away without using a pointing device. |
| 2.5.1 Pointer Gestures | Not Applicable | This criterion is not relevant to the product. |
| 2.5.2 Pointer Cancellation | Supports | Most pointer interactions (like clicks and taps) are triggered on release, allowing users to cancel actions by moving away before lifting |
| 2.5.3 Label in Name | Supports | The accessible name for components matches or contains the visible label for voice-control compatibility |
| 2.5.4 Motion Actuation | Not Applicable | This criterion is not relevant to the product. |
| 2.2.1 Timing Adjustable | Not Applicable | This criterion is not relevant to the product. |
| 2.2.2 Pause, Stop, Hide | Not Applicable | This criterion is not relevant to the product. |
| 2.3.1 Three Flashes or Below Threshold | Not Applicable | This criterion is not relevant to the product. |
| 2.4.1 Bypass Blocks | Partially Supports | The application has minimal repeated navigation, allowing users to reach the main content efficiently with screen reader navigation or touch. While a dedicated skip feature is not provided, the impact on usability remains low. |
| 2.4.2 Page Titled | Supports | Each page includes a descriptive and unique title that identifies its purpose |
| 2.4.3 Focus Order | Supports | Interactive components receive focus in a logical and predictable order that preserves meaning and operability. |
| 2.4.4 Link Purpose (In Context) | Supports | Links clearly describe their purpose. |
| 3.1.1 Language of Page | Supports | The default language of each page is correctly identified in the HTML lang attribute. |
| 3.2.1 On Focus | Supports | No unexpected context changes on focus. |
| 3.2.2 On Input | Supports | User input does not automatically trigger context changes without warning. |
| 3.3.1 Error Identification | Supports | When input errors are detected, they are clearly indicated with accessible text |
| 4.1.2 Name, Role, Value | Supports | All interactive components expose appropriate name, role, state, and value information programmatically. |
| 3.2.6 Consistent Help | Supports | A consistent “Tech Support” option is available on every page of the platform, ensuring users can easily access assistance whenever needed |
| 3.3.7 Redundant Entry | Supports | The platform prevents users from having to re-enter information that has already been provided, ensuring they do not need to input the same data multiple times |
WCAG 2.2 – Level AA
| Criteria | Conformance Level | Remarks / Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | This criterion is not relevant to the product. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | This criterion is not relevant to the product. |
| 1.3.4 Orientation | Not Applicable | This criterion is not relevant to the product. |
| 1.3.5 Identify Input Purpose | Supports | Input fields use semantic HTML and programmatic labels so their purpose can be determined by assistive technologies. |
| 1.4.3 Contrast (Minimum) | Supports | All text meets or exceeds the 4.5:1 contrast ratio; large text meets 3:1 contrast |
| 1.4.4 Resize Text | Not Applicable | This criterion is not relevant to the product. |
| 1.4.5 Images of Text | Supports | No images of text are used in the platform, except for essential branding or logos |
| 1.4.10 Reflow | Does Not Support | The application maintains a consistent layout across devices. However, it does not adapt to system text or display scaling settings, which may limit flexibility for users who prefer larger text sizes.. |
| 1.4.11 Non-Text Contrast | Supports | Essential icons, controls, and graphical indicators maintain sufficient contrast against adjacent colors. |
| 1.4.12 Text Spacing | Not Applicable | This criterion is not relevant to the product. |
| 1.4.13 Content on Hover or Focus | Supports | Tooltips, dropdowns, and hover/focus content remain visible until dismissed. |
| 2.4.5 Multiple Ways | Partially Supports | The application provides navigation through a menu bar and search option. However, alternative navigation methods are limited, which may reduce flexibility for some users. |
| 2.4.6 Headings and Labels | Supports | Headings and form labels are descriptive and help users understand structure and purpose. |
| 2.4.7 Focus Visible | Supports | Interactive elements in the application display a visible focus indicator, helping users identify their current position while navigating. |
| 3.1.2 Language of Parts | Supports | The platform allows users to translate incoming messages into their preferred language. |
| 3.2.3 Consistent Navigation | Supports | Navigation mechanisms (menu items, placement, labels) are presented consistently across pages. |
| 3.2.4 Consistent Identification | Supports | Interactive components with the same function are identified consistently throughout the platform. |
| 3.3.3 Error Suggestion | Supports | When a user makes an input error, helpful text suggestions are provided to assist in correction. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Partially Supports | The application includes confirmation dialogs and validation for certain modifications (such as profile updates). For other actions, like chat history deletion, reversibility is not currently available. We are enhancing consistency by extending confirmation and error-prevention measures to all user-controlled data in future releases. (Need to revisit). |
| 4.1.3 Status Messages | Supports | Status messages are announced by screen readers without moving focus. |
| 2.4.11 Focus Not Obscured (Minimum) (New in 2.2) | Supports | When navigating, Focused elements remain visible on the screen and are not completely hidden by headers, footers, or other fixed content. |
| 2.5.7 Dragging Movements (New in 2.2) | Not Applicable | This criterion is not relevant to the product. |
| 2.5.8 Target Size (Minimum) (New in 2.2) | Partially Supports | Most controls meet the minimum target size, but a few smaller elements do not. |
| 3.3.8 Accessible Authentication (Minimum) (New in 2.2) | Supports | The platform’s authentication process allows copy/paste in login fields and supports simple alternatives such as one-time passcodes, ensuring users are not required to memorize or solve cognitive tasks. |