Accessibility Conformance Report
VPAT® Version 2.5 Rev — WCAG 2.2 Edition · August 2026
Name of Product
TalkCampus
Report Date
August 2026
VPAT® Version
2.5 Rev — WCAG Edition
Contact
Product description: TalkCampus is a peer support platform for student wellbeing, offering a way to get instant peer support 24/7 through native iOS and Android applications.
Notes: This document has been completed based on the current tested and specified functionality of the named native Android and iOS Apps; web properties are excluded. It updates the September 2025 report to the WCAG 2.2 success criteria set using the ITI VPAT 2.5 Rev WCAG Edition structure.
Evaluation methods used: Evaluation is based on an external accessibility assessment (September 2025), general product knowledge, review of product documentation, and testing with assistive technologies.
Applicable Standards & Guidelines
This report covers the degree of conformance for the following accessibility standards and guidelines.
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 Used in This Report
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
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 | Supports | Text alternatives are available for the images in a post. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | There is no audio-only or video-only content available in the App. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | There are no pre-recorded videos in the App. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | There are no pre-recorded audio-described videos in the App. |
| 1.3.1 Info and Relationships | Supports | App uses a logical structure where information and relationships can be programmatically determined across all functionalities. |
| 1.3.2 Meaningful Sequence | Partially Supports | App presents content in a meaningful order except for the following: after completing Search, a number of historical searches are not announced to the user. |
| 1.3.3 Sensory Characteristics | Supports | App does not rely on sensory information alone to convey meaning. |
| 1.4.1 Use of Color | Supports | App does not rely only on color coding to convey information. |
| 1.4.2 Audio Control | Supports | App does not play audio or any multimedia automatically. |
| 2.1.1 Keyboard | Supports | All core system functionality in the App (i.e., login screens, user menus, navigation controls) can be accessed using touch, with VoiceOver and TalkBack support including Wellness Centre articles. |
| 2.1.2 No Keyboard Trap | Supports | There are no keyboard traps in the App. |
| 2.1.4 Character Key Shortcuts | Not Applicable | App does not implement character-key shortcuts. |
| 2.2.1 Timing Adjustable | Not Applicable | App does not impose a user timeout. |
| 2.2.2 Pause, Stop, Hide | Supports | The App does not use moving or blinking content. |
| 2.3.1 Three Flashes or Below Threshold | Supports | The App does not use flashing content. |
| 2.4.1 Bypass Blocks | Supports | Screen reader users can navigate directly to the footer of the main page, which includes the “home” icon. |
| 2.4.2 Page Titled | Supports | App uses helpful and clear page titles. |
| 2.4.3 Focus Order | Supports | Components receive focus in an order that preserves meaning. |
| 2.4.4 Link Purpose (In Context) | Supports | App supports contextual link purpose. |
| 2.5.1 Pointer Gestures | Supports | App does not require users to make path-based or multipoint gestures to operate core functionality. |
| 2.5.2 Pointer Cancellation | Supports | App does not activate functions on the down-click or down-tap. |
| 2.5.3 Label in Name | Supports | Programmatic labels for elements match the label the user sees. |
| 2.5.4 Motion Actuation | Supports | App does not utilize any motion interactions. |
| 3.1.1 Language of Page | Supports | The App’s default language is English, exposed through the standard iOS and Android platform locale mechanisms. The App also provides the ability to translate both interface elements and user-generated content into multiple languages. |
| 3.2.1 On Focus | Supports | Elements do not change when they receive focus. |
| 3.2.2 On Input | Supports | Elements do not change when they receive input. |
| 3.2.6 Consistent Help | Supports | Help and support entry points appear in a consistent relative location across the App, consistent with the App’s consistent navigation and consistent identification of components. |
| 3.3.1 Error Identification | Supports | App clearly identifies input errors. |
| 3.3.2 Labels or Instructions | Supports | All input fields are clearly labelled, and clear instructions are given for user input. |
| 3.3.7 Redundant Entry | Supports | Registration and sign-in are single-pass processes (email address, password, and email-based verification); users are not required to re-enter information previously provided within the same process. |
| 4.1.1 Parsing | Not Applicable | This criterion was removed in WCAG 2.2 (obsolete). Per the ITI VPAT 2.5 guidance it no longer applies; for WCAG 2.0/2.1 reporting it is always Supports per the September 2023 errata. |
| 4.1.2 Name, Role, Value | Supports | Buttons in the App have discernible text, and controls expose names, roles and values to assistive technologies. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The App does not use synchronized media. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | There are no pre-recorded videos in the App. |
| 1.3.4 Orientation | Partially Supports | Content on phones is restricted to portrait display orientation. Web and tablet versions are accessible in landscape. |
| 1.3.5 Identify Input Purpose | Not Applicable | App does not require this capability. |
| 1.4.3 Contrast (Minimum) | Supports | All primary functions, menus and content meet the 4.5:1 color contrast requirement. |
| 1.4.4 Resize Text | Supports | Text can be resized to at least 200 percent without loss of content or functionality in the App. |
| 1.4.5 Images of Text | Supports | The App does not use images of text. |
| 1.4.10 Reflow | Supports | Content in the App can be presented without loss of information or functionality and without requiring scrolling in two dimensions. |
| 1.4.11 Non-text Contrast | Partially Supports | Core system functionality (i.e., login screens, user menus, navigation controls) visual content has a contrast ratio of at least 3:1, except for the gray close button used on some Settings pages. |
| 1.4.12 Text Spacing | Supports | App has adequate text spacing throughout. |
| 1.4.13 Content on Hover or Focus | Supports | App provides a mechanism for dismissible and hoverable content. |
| 2.4.5 Multiple Ways | Supports | The App offers several ways to find pages. |
| 2.4.6 Headings and Labels | Supports | The App uses a meaningful heading structure. |
| 2.4.7 Focus Visible | Supports | Keyboard focus is visible in the App. |
| 2.4.11 Focus Not Obscured (Minimum) | Supports | Focused components are not hidden by author-created content; focus is visible when navigating the App (see 2.4.7) and the App does not use overlaying or moving content (see 2.2.2). |
| 2.5.7 Dragging Movements | Supports | App functionality does not rely on dragging movements; the App does not require users to make specific finger or cursor gestures to operate functionality (see 2.5.1). |
| 2.5.8 Target Size (Minimum) | Supports | Interactive targets follow the standard iOS and Android platform touch-target sizing conventions, which meet or exceed the 24 by 24 CSS pixel minimum; targets within lines of text are excepted per the criterion. |
| 3.1.2 Language of Parts | Supports | User-generated content may appear in multiple languages. The App provides on-demand translation of user-generated content and interface elements into the user’s preferred language, meeting this criterion with equivalent facilitation. |
| 3.2.3 Consistent Navigation | Supports | The App uses consistent navigation across the application. |
| 3.2.4 Consistent Identification | Supports | The App uses icons and buttons consistently across the application. |
| 3.3.3 Error Suggestion | Supports | App suggests fixes when users make errors. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | App reduces the risk of input errors for sensitive data and validates the data before submission. |
| 3.3.8 Accessible Authentication (Minimum) | Supports | Authentication uses an email address and password, with email-based verification links and support for SSO (SAML 2.0). No cognitive function test such as a puzzle, CAPTCHA or transcription challenge is used in the sign-in or account-recovery flows. |
| 4.1.3 Status Messages | Supports | App status changes are promptly conveyed to the user. |
Legal Disclaimer
We have made every attempt to ensure the accuracy and reliability of the information provided in this report as of the date of the report. We cannot guarantee that the iOS and Android Apps are free from accessibility defects. The contents of this document are subject to change without notice. No contractual obligations are formed either directly or indirectly by this document, and this document shall not be interpreted to be included in any contract between the parties.
“Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information Technology Industry Council (ITI).
Questions about accessibility?
If you have questions about this report or would like to share feedback about the accessibility of TalkCampus, we’d love to hear from you.