- Accessibility Summary
- PeopleGrove Completed VPAT
- Providing Accessibility Feedback
This document is intended for any PeopleGrove client, potential client, or end user who wants to learn
more about how PeopleGrove handles compliance with accessibility guidelines.
PeopleGrove is committed to accessibility. For PeopleGrove, accessibility goes beyond just compliance. Our company's mission is to help connect every student and alumni to the people and resources they need to achieve career and personal success. We cannot deliver on that mission without providing equitable access to our services to people of all backgrounds.
This document provides an overview of our commitment to making PeopleGrove accessible to every user. We take the following steps to continuously improve the Platform’s accessibility:
- Developer training on accessibility best practices
- Use of third party applications to test the accessibility of the PeopleGrove platform
- Testing for accessibility during the PeopleGrove QA process
- Training of the PeopleGrove support team on how to provide support to users with disabilities
PeopleGrove is constantly improving our level of accessibility. Our QA team uses Totally
(http://khan.github.io/tota11y/) to test releases.
We strive to make all of our software fully Section 508 compliant. PeopleGrove believes that
our platform is currently compliant. Please see the completed
VPAT form for details.
PeopleGrove Accessibility Conformance Report
VPAT® Version 2.3 – June 2020
Name of Product: PeopleGrove Platform
Product Description: PeopleGrove is an online software platform for mentoring, networking, and community engagement. The software platform is built for students, alumni, and staff at universities and other institutions.
Questions? Please click the turquoise question mark icon in the bottom right corner of your platform to reach our Support team.
Since PeopleGrove supports branding customization and admin-generated content (from our clients), we require cooperation in ensuring that modifications or additional content is accessible. It is noted below where we need client cooperation in ensuring we meet accessibility standards. This document currently covers only user facing (student, alumni) sections of the website. While we strive for compliance with every admin tool we provide, some tools are complex.
If some part of our application is not accessible, we are here to help. We handle accessible issues with admin tools on a case by case basis and provide support to any admins with disabilities via email or phone. Our Support center answers accessibility issues within 1 business day.
Evaluation Methods Used: PeopleGrove evaluates during our development and deployment process using various tools including ChromeVox and Tota11y. All new development must pass accessibility review before deployment.
Standards / Guidelines
This report covers the degree of conformance for the following accessibility standard/guideline:
|Standard / Guideline||Included in Report|
|Web Content Accessibility Guidelines 2.1 at https://www.w3.org/TR/WCAG21/||Level A☑ Level AA ☑ Level AAA|
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 be used only in WCAG 2.0 Level AAA.
WCAG 2.x Report
Table 1: Success Criteria, Level A
|Criteria||Conformance Level||Remarks and Explanations|
|1.1.1 Non-text Content (Level A)||Supports||Alt tags on images, aria tags when applicable. We test all pages with screen reader.|
|1.2.1 Audio-only and Video-only (Prerecorded) (Level A)||Supports||No pre-recorded audio and video by default. If Admins upload video or audio, need to ensure captions are provided.|
|1.2.2 Captions (Prerecorded) (Level A)||Supports||No pre-recorded audio and video by default. If Admins upload video or audio, need to ensure captions are provided.|
|1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)||Supports||No pre-recorded audio and video by default. If Admins upload video or audio, need to ensure captions are provided.|
|1.3.1 Info and Relationships (Level A)||Supports||Use standard HTML markup or accessible libraries. When possible, use standard headers. There are some pages where header structure may be out of order, but screen reader operation seems to work.|
|1.3.2 Meaningful Sequence (Level A)||Supports||Content and tab order is kept in meaningful sequence. Skip to main content is provided.|
|1.3.3 Sensory Characteristics (Level A)||Supports||Sensory characteristics are not used to convey information.|
|1.4.1 Use of Color (Level A)||Supports||Color is not used as the only way to convey information.|
|1.4.2 Audio Control (Level A)||Supports||When audio is used, there is a way to turn off the audio from the application (such as a mute button in video chat).|
|2.1.1 Keyboard (Level A)||Supports||Application can be fully navigated without a mouse.|
|2.1.2 No Keyboard Trap (Level A)||Supports||There are no known keyboard traps.|
|2.1.4 Character Key Shortcuts (Level A 2.1 only)||Not Applicable||No non-standard keyboard shortcuts are provided.|
|2.2.1 Timing Adjustable (Level A)||Supports||Session timeout cannot be adjusted, but it can be dismissed. Otherwise, timing is not used.|
|2.2.2 Pause, Stop, Hide (Level A)||Supports||No such content.|
|2.3.1 Three Flashes or Below Threshold (Level A)||Supports||No such flashes.|
|2.4.1 Bypass Blocks (Level A)||Supports||Skip to Main Content is provided via the keyboard.|
|2.4.2 Page Titled (Level A)||Supports||Application page is titled. Individual pages have headers.|
|2.4.3 Focus Order (Level A)||Supports||Focus order is handled throughout the application.|
|2.4.4 Link Purpose (In Context) (Level A)||Supports||Most links have their purpose in context, or an appropriate label.|
|2.5.1 Pointer Gestures (Level A 2.1 only)||Not Applicable||No such gestures.|
|2.5.2 Pointer Cancellation (Level A 2.1 only)||Supports||All click events allow for cancellation.|
|2.5.3 Label in Name (Level A 2.1 only)||Supports||The name contains the visual text.|
|2.5.4 Motion Actuation (Level A 2.1 only)||Not Applicable||No such motion.|
|3.1.1 Language of Page (Level A)||Supports||Pages have specified language.|
|3.2.1 On Focus (Level A)||Supports||Focus does not initiate change of context.|
|3.2.2 On Input (Level A)||Supports||Changing UI component settings does not change context.|
|3.3.1 Error Identification (Level A)||Supports||Errors are provided in text, not color.|
|3.3.2 Labels or Instructions (Level A)||Supports||Labels are provided.|
|4.1.1 Parsing (Level A)||Supports||Standard HTML conventions are followed on all pages.|
|4.1.2 Name, Role, Value (Level A)||Supports||Names and roles can be determined.|
Table 2: Success Criteria, Level AA
|Criteria||Conformance Level||Remarks and Explanations|
|1.2.4 Captions (Live) (Level AA)||Not Applicable||There is no live video on the platform.|
|1.2.5 Audio Description (Prerecorded) (Level AA)||Supports||No pre-recorded audio and video by default. If Admins upload video or audio, need to ensure audio descriptions are provided.|
|1.3.4 Orientation (Level AA 2.1 only)||Supports||Pages are specifically designed to be responsive to all screen sizes.|
|1.3.5 Identify Input Purpose (Level AA 2.1 only)||Supports||Input fields collecting information are correctly identified.|
|1.4.3 Contrast (Minimum) (Level AA)||Supports||Most areas of the site do not have any contrast issue. There are some areas which may be slightly below minimum ratios. Since Admins can customize branding, contrast ratio should be considered when customizing.|
|1.4.4 Resize text (Level AA)||Supports||Text can be resized up to 200% and site is functional.|
|1.4.5 Images of Text (Level AA)||Supports||No known images of text other than logos with appropriate alt text.|
|1.4.10 Reflow (Level AA 2.1 only)||Supports||At 400% zoom, site is still functional, but some pages may be harder to navigate.|
|1.4.11 Non-text Contrast (Level AA 2.1 only)||Supports||Since Admins can customize branding, contrast ratio should be considered when customizing.|
|1.4.12 Text Spacing (Level AA 2.1 only)||Supports||No functionality is lost by changing text settings.|
|1.4.13 Content on Hover or Focus (Level AA 2.1 only)||Supports||Hover-based content like tooltips can be opened or closed with the keyboard. It is persistent and can be dismissed.|
|2.4.5 Multiple Ways (Level AA)||Supports||There are multiple ways to navigate the system, and various links to get to different areas of the site.|
|2.4.6 Headings and Labels (Level AA)||Supports||Headings and labels are used to describe topic or purpose. There may be some pages where headings are vague.|
|2.4.7 Focus Visible (Level AA)||Supports||Elements are surrounded by a border during keyboard only operation.|
|3.1.2 Language of Parts (Level AA)||Supports||Standard English language is used throughout the site. It is not always labeled.|
|3.2.3 Consistent Navigation (Level AA)||Supports||Navigation is consistent across all pages on the site.|
|3.2.4 Consistent Identification (Level AA)||Supports||Our code uses the same components for the same functions. There may be some examples where labels are provided, but they are slightly different.|
|3.3.3 Error Suggestion (Level AA)||Supports||Not many inputs have known data to correct against. Inputs with auto-fill such as location provide corrected suggestions.|
|3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)||Supports||No Legal or Financial commitments. Users can update profile data, which is validated. Users can edit the data as many times as desired.|
|4.1.3 Status Messages (Level AA 2.1 only)||Supports||Status messages use standard elements which contain a role.|
Legal Disclaimer (PeopleGrove)
PeopleGrove strives to make our website as accessible as possible for everyone and believes that the above assessment has been completed accurately, but we cannot guarantee 100% accuracy given the scope of this evaluation. The results have not been audited by a 3rd party. While we strive for AAA standard, as a large application with many views, there may be some areas requiring improvement.
We cannot guarantee that accessible navigation will be available with no issues, but we do commit to answering any accessibility concerns promptly submitted by clicking the green question mark icon in the bottom right corner of any page on your PeopleGrove site. PeopleGrove also cannot be responsible for branding modifications and content uploaded by platform administrators at our clients. We require cooperation in ensuring accessibility standards are followed (i.e. if an admin uploads a video, it needs to have captions).
PeopleGrove welcomes feedback from students, alumni, and administrators on accessibility matters, and we are committed to improvement. Please submit a ticket to our support team by clicking the green question mark icon in the bottom right corner of any page on your PeopleGrove site if you need any assistance.
If you are performing an audit of PeopleGrove's accessibility, we appreciate your structured feedback so that we can continue to improve our software.
In order to make your feedback actionable, please provide the following information if you are able. Often, a spreadsheet/document with these columns can be very helpful!
- Current URL where you experienced an issue
- Description of the issue
- Screenshot of the issue, if applicable
- Applicable WCAG sections
- Severity (Low, Medium, High)
- Proposed Solution
|Current URL||Description||Screenshot||WCAG||Severity||Proposed Solution|
|https://school.peoplegrove.com/home||All images missing alt text||1.1.1||High||Add alt-text to all the images on this page|