Accessibility Statement and Documentation
Created 12/18/22
Last Updated 12/19/22
Overview
Navengage is committed to providing accessible user interfaces across all products and services to ensure equal access for all users. Navengage agrees to use commercially reasonable efforts to promptly respond to and resolve complaints regarding accessibility of its products or services. Navengage continues to evaluate accessibility of their products and conducts regular tests using both manual QA and third party tools such as AssistivLabs, Lightbox, and Wave. If you would like to provide feedback, or have any questions pertaining to accessibility, please email our CTO at dan@navengage.com.
Product Usage Information for Users with Disabilities:
-
Use of a screen reader on the web may be appropriate for users with disabilities. Elements within web pages are titled and respect readability, keyboard operation, and focus order.
-
The main accessibility gaps concerning mobile devices have to do with native assistance technologies. While the majority of native assistance technologies are tested and supported (i.e. dynamic text sizing, VoiceOver, etc.) at the highest level, there may be issues with component specific resizing or text to speech. These minor component gaps are targeted for remediation in Q2 and Q3 of 2023. Below are the feature descriptions as well as interim workarounds until the gaps are resolved.
-
It is not possible to pinch to zoom or change the font sizes within the application.
-
Note, until this issue is resolved, please use the native iOS and Android Accessibility functionality, which is supported. If further support is needed, please use the web version.
-
-
Android - High Contrast Text, an experimental accessibility feature, is partially supported but may lead to color issues (not fully tested).
-
Android - Color Inversion is not currently supported. Please use the web application if inversion is required.
-
Scope
The scope of this report represents the web, iOS, and Android apps for the Engagement App (collectively, the “Product”). This report does not cover the Organization Management System, which is addressed in a separate Accessibility Statement, available upon request.
Navengage Accessibility Conformance Report WCAG Edition
(Based on VPAT® Version 2.4)
Name of Product/Version: The Navengage Engagement Application (Web; iOS, and Android mobile applications)
Report Date: 12/18/22
Product Description: The Navengage Engagement Application is a platform that services students, faculty, and staff at Colleges and Universities, providing a central location to find and participate in events, organizations, and resources, as well as find connections within campus communities.
Contact Information: Dan Lordan - 610-955-4360 - dan@navengage.com
Notes: The WCAG framework was created for web accessibility, but covers mobile accessibility as well. As is noted in https://www.w3.org/WAI/standards-guidelines/mobile/, there are no separate guidelines for mobile. Comments in “Remarks and Explanations” refer to both web, iOS, and Android unless specifically noted.
Evaluation Methods Used: The Navengage Engagement Application (web) was evaluated using Firefox on a Macbook Pro. Assistive technologies used in this evaluation included Lightbox and Wave for accessibility testing and reading. Mobile applications were tested on both simulators and real devices, with multiple devices and operating systems.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Web Content Accessibility Guidelines 2.1 |
Level A (Yes) Level AA (Yes, Partially) 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.
- Not Applicable: The criterion is not relevant to the product.
Note: When reporting on conformance with the WCAG 2.1 Success Criteria, the criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.
WCAG 2.1 Report
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1. Perceivable |
||
|
1.1.1 Non-text Content (Level A) |
Supports |
The product provides sufficient text alternatives for most instances of non-text content. |
|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) |
Not Applicable |
The product does not contain prerecorded audio-only or video-only media. |
|
1.2.2 Captions (Prerecorded) (Level A) |
Not Applicable |
The product does not contain prerecorded synchronized media. |
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) |
Not Applicable |
The product does not contain prerecorded video content that would require audio description or a media alternative. |
|
1.2.4 - 1.2.9 - Multiple Time-Based Media Criteria (Level A) |
Not Applicable |
The product does not contain any pre-recorded audio or video media. |
|
1.3.1 Info and Relationships (Level A) |
Partially Supports |
Most visual structure and relationship information is provided through object information, or available in text. Some header tags still need to be rewritten to handle relationship management. |
|
1.3.2 Meaningful Sequence (Level A) |
Supports |
The product is presented in a meaningful sequence. |
|
1.3.3 Sensory Characteristics (Level A) |
Supports |
Instructions do not rely solely on sensory characteristics. |
|
1.3.4 Orientation (Level AA) |
Supports |
Content does not restrict its view and operation to a single display orientation, such as portrait or landscape. |
|
1.3.4 Identify Input Purpose (Level AA) |
Supports |
Form input data can be both programmatically and visually identified.1 |
|
1.4.1 Use of Color (Level A) |
Supports |
Product content and functionality does not convey information through color alone. |
|
1.4.2 Audio Control (Level A) |
Not Applicable |
The product does not contain any pre-recorded audio or media. |
|
1.4.3 Contrast - Minimum (Level AA) |
Partially Supports |
Contrast is supported across the product, although using a clients’ color palette has resulted in breaking accessibility WCAG standards. These are being remediated in conjunction with the client. |
|
1.4.4 Resize Text (Level AA) |
Supports |
Supports text resizing, without loss of functionality. Also supports native accessibility resizing via iOS (Larger Text Dynamic Typing) and Android (Font Size) |
|
1.4.5 Images of Text (Level AA) |
Partially Supports |
Supports text fallback for images on web, Android and iOS are a work in progress. |
|
1.4.6 Contrast - Enhanced (Level AAA) |
Partially Supports |
Contrast is supported across the product, although using a clients’ color palette has resulted in breaking accessibility WCAG standards. These are being remediated in conjunction with the client. |
|
1.4.7 Low or No Background Audio (Level AA) |
Not Applicable |
No pre-recorded audio. |
|
1.4.11 Non-text Contrast (Level AA) |
Partially Supports |
Contrast is supported across the product, although using a clients’ color palette has resulted in breaking accessibility WCAG standards. These are being remediated in conjunction with the client. |
|
1.4.12 Text Spacing (Level AA) |
Supports |
Text is spaced according to guidelines. |
|
1.4.13 Content on Hover or Focus (Level AA) |
Partially Supports |
Hoverable elements exist on the web, to provide tooltips. They are not dismissable as defined in 1.4.13 |
|
2. Operable |
||
|
2.1.1 Keyboard (Level A) |
Partially Supports |
Most site functionality can be accessed and operated using a keyboard.1 |
|
2.1.2 No Keyboard Trap (Level A) |
Supports |
The website does not include keyboard traps.1 |
|
2.1.4 Character Key Shortcuts (Level A) |
Not Applicable |
No keyboard shortcuts enabled, including content using only letter, punctuation, number, or symbol characters.1 |
|
2.2. Enough Time (Level A - AAA) |
Not Applicable |
No time based events in the application. |
|
2.3.1 Three Flashes or Below Threshold (Level A) |
Not Applicable |
No flashing elements on the site. |
|
2.3.2 Three Flashes (Level AAA) |
Not Applicable |
No flashing elements on the site. |
|
2.4.1. Bypass Blocks (Level A) |
Partially Supports |
The only element that proceeds content is the main site header, otherwise all other content is easily navigable.1 |
|
2.4.2. Page Titles (Level A) |
Supports |
All pages have titles. |
|
2.4.3. Focus Order (Level A) |
Supports |
The products’ components receive focus in a meaningful order - navigation first and then page content.1 |
|
2.4.4. Link Purpose (Level A) |
Supports |
The purpose of each link is clear in the text of the link. |
|
2.4.5. Multiple Ways (Level AA) |
Supports |
Navigation to web pages via multiple navigation bars, and in-page links, is available. |
|
2.4.6 Headings and Labels (Level A) |
Supports |
Pages have headings, subheadings, and further information about the page. |
|
2.4.7 Focus Visible (Level AA) |
Supports |
Focusing on an element is visible via an opaque background, to inform the user on the focused element.1 |
|
2.4.8 Location (Level AAA) |
Supports |
The location of the user within the site is easily identified by highlighting on the navigation. |
|
2.5.1. Pointer Gestures (Level A) |
Not Applicable |
No path based gestures required. |
|
2.5.2. Pointer Cancellation (Level A) |
Supports |
Drag and drop elements in document upload allow for both No Down-Event and Essential completion. |
|
2.5.3. Label in Name (Level A) |
Supports |
Elements with text or images of text also include visual labels. |
|
2.5.4. Motion Actuation (Level A) |
Not Applicable |
No motion activated elements present in the application. |
|
3. Understandable |
||
|
3.1.1 Language of Page (Level A) |
Supports |
The default language of the site’s web page is identified using the lang attribute in the html element.1 |
|
3.1.2 Language of Parts (Level AA) |
Not Applicable |
The only language used in the application is English, and is specified in the lang attribute in the html element.1 |
|
3.2.1 On Focus (Level A) |
Supports |
The site’s components do not initiate a change of context when focused. |
|
3.2.2 On Input (Level A) |
Supports |
Changes of context do not occur automatically on user input. |
|
3.2.3. Consistent Navigation (Level AA) |
Supports |
Navigation elements do not change order or area on the page. |
|
3.2.4 Consistent Identification (Level AA) |
Supports |
Components that share functionality (i.e. Add Event), are consistent in their presentation and identification. |
|
3.3.1 Error Identification (Level A) |
Supports |
Validation errors are shown to the user underneath text boxes, to ensure user remediation. Additionally, in-app notifications with error messages are present, and iOS and Android in-app notifications with error messages are in development. |
|
3.3.2 Labels or Instructions (Level A) |
Supports |
All user input comes with both instructions (above) and placeholder text to inform users on proper input. |
|
3.3.3 Error Suggestion (Level AA) |
Supports |
Validation errors are shown to the user underneath text boxes, with proper explanation on how to remediate, to ensure user remediation. Additionally, in-app notifications with error messages are present, and iOS and Android in-app notifications with error messages are in development. |
|
3.4.4 Error Prevention (Legal, Financial, Data) (Level AA) |
Partially Supports / Not Applicable |
While the system does not deal with sensitive legal and financial data, confirmation boxes are present throughout the application to assist in unnecessary mistakes. For example, if you begin a form, then click a navigation element, you are presented with “Are you sure you want to leave? Changes will be lost.” |
|
4. Robust |
||
|
4.1.1 Parsing (Level A) |
Supports |
All web pages support parsing for assistive technologies, with complete start and end tags.1 |
|
4.1.2 Name, Role, Value (Level A) |
Partially Supports |
Elements can be programmatically determined within <div> tags, however, elements within the javascript are not renamed after compilation.1 |
|
4.1.3 Status Messages (Level AA) |
Partially Supports |
Elements can be programmatically determined within <div> tags, however, elements within the javascript are not renamed after compilation.1 |
- Tested on web only, criteria applies only to web elements