VPAT 508 Our Partners GSA Info Contact Us

15 min read

QuickSeries Accessibility Conformance Report

Revised Section 508 Edition

Name of Product/Version: QuickConnect App for Android

Product Description: Content Management System

Report Date: July 28, 2022

Contact Information:

Notes: QuickConnect App for Android is a companion app that allows end-users to consume the content created by our clients using the QuickConnect App client portal.

A separate accessibility conformance report is available for the Android version of the app. You can contact us to request the QuickConnect App for Android accessibility conformance report.

Evaluation Methods Used: Our development process includes an accessibility testing phase performed by our trained quality assurance team, and is guided by WCAG 2.1 AA standards. We design, build and maintain a design style guide and components library with accessibility and consistency in mind. Our developers' definition of done is a fully functional, accessible feature, no excuse. Accessibility testing is currently done manually using assistive technologies such as screen readers.

The following Android build-in accessibility features were used to evaluate this product:

  • VoiceOver
  • Display and text size settings (such as increased contrast, bold text, large text)
  • Physical keyboards

The following accessibility testing tools were used to evaluate this product:

  • Stark, a tool that allows designer to test the contrast of their design and simulate color blindness as per WCAG 2.1 AA standards.

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/Guideline Included In Report
Web Content Accessibility Guidelines 2.0 Level A (Yes)
Level AA (Yes)
Level AAA (No)
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 (Yes)

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.
  • Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.

WCAG 2.0 Report

Tables 1 and 2 also document conformance with:

  • Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing
  • Chapter 6 – 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.0 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 (Level A)Also applies to:

 

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Partially Supports
  • Text alternatives are provided for all icons.
  • Text instructions are provided to describe button functionality.
  • Textual context is provided for some more complex user interfaces.
  • Controls and input fields have descriptions or contextual labels to describe their intent.

Exceptions:

  • All images that are uploaded do not currently have any alternative text associated to them. The images are skipped when a screen reader is used.

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:Revised Section 508

 

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • Content is created by the user.
  • The platform currently supports videos from YouTube and Vimeo though other content can be embedded within the rich text editors throughout the app.
  • YouTube and Vimeo both provide a video player that is A and AA compliant.
  • YouTube can auto generate a closed caption file, but this feature is controlled by the user.
  • Vimeo allows users to upload their own closed caption file.
  • Refer to Vimeo's official article detailing their AA accessibility compliance: https://vimeo.com/blog/post/introducing-the-new-vimeo-player/
  • No such article is officially provided by YouTube.

It is up to the portal administrator to validate that content embedded from unknown sources complies with accessibility best practices.

1.2.2 Captions (Prerecorded) (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • Content is created by the user.
  • The platform currently supports videos from YouTube and Vimeo though other content can be embedded within the rich text editors throughout the app.
  • YouTube and Vimeo both provide a video player that is A and AA compliant.
  • YouTube can auto generate a closed caption file, but this feature is controlled by the user.
  • Vimeo allows users to upload their own closed caption file.
  • Refer to Vimeo's official article detailing their AA accessibility compliance: https://vimeo.com/blog/post/introducing-the-new-vimeo-player/
  • No such article is officially provided by YouTube.
  • It is up to the portal administrator to validate that content embedded from unknown sources complies with accessibility best practices.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • Content is created by the user.
  • The platform currently supports videos from YouTube and Vimeo though other content can be embedded within the rich text editors throughout the app.
  • YouTube and Vimeo both provide a video player that is A and AA compliant.
  • YouTube can auto generate a closed caption file, but this feature is controlled by the user.
  • Vimeo allows users to upload their own closed caption file.
  • Refer to Vimeo's official article detailing their AA accessibility compliance: https://vimeo.com/blog/post/introducing-the-new-vimeo-player/
  • No such article is officially provided by YouTube.

It is up to the portal administrator to validate that content embedded from unknown sources complies with accessibility best practices.

1.3.1 Info and Relationships (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • App pages are built using Google's Android Human Interface best practices and web content is generated to HTML5 specifications.

1.3.2 Meaningful Sequence (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • App pages are built using Google's Android Human Interface best practices and web content is generated to HTML5 specifications.
  • Pages are linear and read clearly from top to bottom.

1.3.3 Sensory Characteristics  (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Partially Supports
  • Any concepts suggested through shape, size, visual location, orientation or sound are also communicated through language via textual equivalents – visible or invisible (alternate text, ARIA, etc.).

Exceptions:

  • Any checklists with a child-level (or sub-level) checklist currently do not textually identify them as such.

Note:

  • Some resource items may be available on a map depicted by pins. The app uses the native Google Maps API and falls back on that API's accessibility features. In other words, they are not controlled by us.

1.4.1 Use of Color (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • All elements communicating importance, meaning or intent through colors are also communicated through language (i.e.: highlighted item indicating current location, disabled form element or action buttons, errors in forms, selected items, etc.).
  • Our application design language uses clear, large fonts where possible.

During an app's onboarding, the user is able to select between a default and high-contrast theme that is applied to the entire application UI.

A high-contrast color scheme is available when the “increase contrast” setting is turned on by the user via the device's accessibility settings.

Note:

  • All of our applications are white labeled. This means that a color resulting in lower contrast ratAndroid might be selected by the client against our advice, resulting in less than ideal results for this criterion. That being said, these colors are often used for actionable elements which are mostly large in size resulting in a lowered impact to visually impaired users.

1.4.2 Audio Control (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Not Applicable
  • No videos or audio recordings launch automatically when a page is loaded.

2.1.1 Keyboard (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • A physical keyboard can be used with the app to type content and to navigate with Google's VoiceOver functionality.

2.1.2 No Keyboard Trap (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • A physical keyboard can be used with the app to type content and to navigate with Google's VoiceOver functionality.

2.2.1 Timing Adjustable (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Not Applicable
  • The app does not require a time-based response.

2.2.2 Pause, Stop, Hide (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Partially Supports
  • Our library of eGuides allows users to download content in a book-like format. The user can begin and stop the download process but no textual feedback is provided when the state of an item changes from download to downloading or downloaded. It also does not inform the user of the download progress.
  • App content is downloaded as users navigate through the app. This is an automatic process.

Exceptions:

  • The PDF library does not allow users to stop a download and download progress is not provided for assistive technologies. Furthermore, when a download is complete, the download button label changes its label to ‘view' and it does not inform assistive technologies of that change.

2.3.1 Three Flashes or Below Threshold (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • Flashing or blinking does not occur in the prohibited range.

Content is created by the user. Videos that violate this criterion may be embedded in the app.

2.4.1 Bypass Blocks (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs
Supports
  • App content is generated in a linear template without any repeating or redundant blocks of information.

2.4.2 Page Titled (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • Every page of the app contains the page title in either the navigation bar or as one of the first elements of a page.

2.4.3 Focus Order (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • The app is designed in a linear fashion enforcing a linear focus order.

2.4.4 Link Purpose (In Context) (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • The purpose of each link can be determined from the link text together with context.

Notes:

Links and link labels are created by the app administrator. When done wrong, that particular link may fail this criteria.

3.1.1 Language of Page (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • Android devices will use the language selected in the VoiceOver Accessibility settings by default.

3.2.1 On Focus (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • When any component receives focus, it does not initiate a change of context.

3.2.2 On Input (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports Changing the setting of user interface components does not automatically result in a change of context.

3.3.1 Error Identification (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • The user is notified of field validation errors in text if there is an input error.

3.3.2 Labels or Instructions (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • The application provides name, role, state and value information to assistive technologies.

4.1.1 Parsing (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports All app pages are built using Google's Android Human Interface best practices and web content is generated to HTML5 specifications.

4.1.2 Name, Role, Value (Level A)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • The application provides name, role, state and value information to assistive technologies.

Table 2: Success Criteria, Level AA

Criteria Conformance Level Remarks and Explanations

1.2.4 Captions (Live) (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Not Applicable There are currently no live events that are part of our app.

1.2.5 Audio Description (Prerecorded) (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports Content is created by the user. It is up to them to create secondary versions of their video content with added audio description.

1.4.3 Contrast (Minimum) (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • Foreground to background contrast adheres to standards.
  • Users control their own content.

During an app's onboarding, the user is able to select between a default and high-contrast theme that is applied to the entire application UI.

  • A high-contrast color scheme is available when the “increase contrast” setting is turned on by the user via the device's accessibility settings.

1.4.4 Resize text (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports The app functions with text enlarged to 200%.

1.4.5 Images of Text (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • Users control their own content.
  • Images of text are not used.

2.4.5 Multiple Ways (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs
Supports
  • Users of the app can navigate from one module to the next using the side menu available in all modules from the navigation bar.
  • Users can use the search functionality to search for categories or module content in all modules.
  • A breadcrumb navigation component is available to users who navigate deeply within linked resources.
  • The eDoc reader allows users to navigate to a specific page by swiping the eDoc like a book page, by using the table of contents or by using the glossaries as links to specific content.

2.4.6 Headings and Labels (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • All pages have descriptive headings and labels. Labels are unique and contextual.

2.4.7 Focus Visible (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • When text fields receive focus, a vertical bar is displayed in the field, indicating that the user can insert text.

Google's Voice Assistant technology automatically applies a focus rectangle on interactive or text elements.

3.1.2 Language of Parts (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports
  • Users create their own content.

3.2.3 Consistent Navigation (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs
Supports
  • The navigation is consistent throughout the app.
  • Interactive items such as search buttons and more options buttons are in a consistent position on each page and maintain a consistent order.

3.2.4 Consistent Identification (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs
Supports
  • All interactive items are identified consistently throughout the application.

3.3.3 Error Suggestion (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Supports Error messages are communicated using a combination of labels and alert popups. Error messages describe each error and link to the appropriate field for resolving the error.

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

 

Also applies to:

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
Not Applicable  

Table 3: Success Criteria, Level AAA

Notes: Deleted; Not applicable.

Revised Section 508 Report

Chapter 3: Functional Performance Criteria(FPC)

Criteria Conformance Level Remarks and Explanations
302.1 Without Vision Partially Supports
  • Supports when combined with compatible assistive technology.
  • All app pages are built using Google's Android Human Interface best practices and web content is generated to HTML5 specifications.
  • Text alternatives are provided for all icons.
  • Text instructions are provided to describe button functionality.
  • Textual context is provided for some more complex user interfaces.
  • Controls and input fields have descriptions or contextual labels to describe their intent.
  • A physical keyboard can be used with the app to type content and to navigate with Google's VoiceOver functionality.

Exceptions:

  • All images that are uploaded do not currently have any alternative text associated with them. Images are skipped when a screen reader is used.
302.2 With Limited Vision Supports
  • Supports when combined with compatible assistive technology.
  • Foreground to background contrast adheres to standards.
  • Users control their own content.
  • All elements communicating importance, meaning or intent through colors is also communicated through language (i.e.: highlighted item indicating current location, disabled form element or action buttons, errors in forms, selected items, etc.).
  • Our application design language uses clear, large fonts where possible.

During an app's onboarding, the user is able to select between a default and high-contrast theme that is applied to the entire application UI.

A high-contrast color scheme is available when the “increase contrast” setting is turned on by the user via the device's accessibility settings.

Note:

  • All of our applications are white labeled. This means that a color resulting in lower contrast ratAndroid might be selected by the client against our advice, resulting in less than ideal results for this criterion. That being said, these colors are often used for actionable elements which are mostly large in size resulting in a lowered impact to visually impaired users.
302.3 Without Perception of Color Supports
  • Color alone is not used to convey information
  • Foreground to background contrast adheres to standards.
  • Users control their own content.
  • All elements communicating importance, meaning or intent through colors are also communicated through language (i.e.: highlighted item indicating current location, disabled form element or action buttons, errors in forms, selected items, etc.).

During an app's onboarding, the user is able to select between a default and high-contrast theme that is applied to the entire application UI.

A high-contrast color scheme is available when the “increase contrast” setting is turned on by the user via the device's accessibility settings.

302.4 Without Hearing Supports
  • No auditory alerts are used.
302.5 With Limited Hearing Supports
  • No auditory alerts are used.
302.6 Without Speech Supports Speech input is not required.
302.7 With Limited Manipulation Supports
  • Supports when combined with compatible assistive technology
  • Touch targets are at a minimum within the minimum recommended size or larger, with enough spacing between interactive elements.
  • Keyboard access is supported
  • No physical device manipulations are required to use the apps.
302.8 With Limited Reach and Strength Supports
  • Touch targets are within the minimum recommended size or larger, with enough spacing between interactive elements.
  • Keyboard access is supported.
  • No physical device manipulations are required to use the apps
  • Error-tolerant functionalities help reduce unintended or incomplete interactions.
302.9 With Limited Language, Cognitive, and Learning Abilities Supports
  • Users control their own content.
  • Simple language is used for text content.
  • Interface navigation is made simple through consistent hierarchical flows that never go deeper than 3 levels.

Chapter 4: Hardware

Notes: This product is not hardware and therefore this section is not applicable to the product.

Chapter 5: Software

Criteria Conformance Level Remarks and Explanations
501.1 Scope – Incorporation of WCAG 2.0 AA See WCAG 2.0 section See information in WCAG 2.0 section
502
Interoperability with Assistive Technology 		Heading cell – no response required Heading cell – no response required
502.2.1 User Control of Accessibility Features Supports
  • Accessibility features native to the Operating System (OS) can be used in our app.
  • When major features are released, our app is tested with the OS accessibility features.
502.2.2 No Disruption of Accessibility Features Supports Our app does not disrupt any OS accessibility features.
502.3 Accessibility Services Heading cell – no response required Heading cell – no response required
502.3.1 Object Information Not Applicable
  • Our app does not disrupt any OS accessibility features.
502.3.2 Modification of Object Information Not Applicable Not a platform software or tool
502.3.3 Row, Column, and Headers Not Applicable Not a platform software or tool
502.3.4 Values Not Applicable Not a platform software or tool
502.3.5 Modification of Values Not Applicable Not a platform software or tool
502.3.6 Label Relationships Not Applicable Not a platform software or tool
502.3.7 Hierarchical Relationships Not Applicable Not a platform software or tool
502.3.8 Text Not Applicable Not a platform software or tool
502.3.9 Modification of Text Not Applicable Not a platform software or tool
502.3.10 List of Actions Not Applicable Not a platform software or tool
502.3.11 Actions on Objects Not Applicable Not a platform software or tool
502.3.12 Focus Cursor Not Applicable Not a platform software or tool
502.3.13 Modification of Focus Cursor Not Applicable Not a platform software or tool
502.3.14 Event Notification Not Applicable Not a platform software or tool
502.4 Platform Accessibility Features Not Applicable Not a platform software or tool
503 Applications Heading cell – no response required Heading cell – no response required
503.2 User Preferences  Supports
  • The app responds well to OS-based accessibility preferences (such as contrast, color filters, focus cursor).
503.3 Alternative User Interfaces Not Applicable Alternative user interfaces are not provided.
503.4 User Controls for Captions and Audio Description Heading cell – no response required Heading cell – no response required
503.4.1 Caption Controls Supports
  • The platform currently supports videos from YouTube and Vimeo which have accessible video players.
  • YouTube and Vimeo both provide a video player that is A and AA compliant.
  • YouTube can auto generate a closed caption file, but this feature is controlled by the user.
  • Vimeo allows users to upload their own closed caption file.
  • Users have access to closed caption controls within the video player's controls.
503.4.2 Audio Description Controls Supports
  • The platform currently supports videos from YouTube and Vimeo which have accessible video players.
  • Both of those platforms do not currently support audio description videos.
  • We recommend the admin of the app to generate a secondary version of their video with audio description built-in.
504 Authoring Tools Heading cell – no response required Heading cell – no response required
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) See WCAG 2.0 section See information in WCAG 2.0 section
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion Not Applicable The app is not an authoring tool.
504.2.2 PDF Export Not Applicable The app is not an authoring tool.
504.3 Prompts Not Applicable The app is not an authoring tool.
504.4 Templates Not Applicable The app is not an authoring tool.

Chapter 6: Support Documentation and Services

Criteria Conformance Level Remarks and Explanations
601.1 Scope Heading cell – no response required Heading cell – no response required
602 Support Documentation Heading cell – no response required Heading cell – no response required
602.2 Accessibility and Compatibility Features Not Applicable
  • Apps are white labeled and delivered to the client through their own developer account. End-user support documentation should be provided by them.
602.3 Electronic Support Documentation Not Applicable
  • Apps are white labeled and delivered to the client through their own developer account. End-user support documentation should be provided by them.
602.4 Alternate Formats for Non-Electronic Support Documentation Not Applicable
  • Apps are white labeled and delivered to the client through their own developer account. End-user support documentation should be provided by them.
603 Support Services Heading cell – no response required Heading cell – no response required
603.2 Information on Accessibility and Compatibility Features Not Applicable
  • Apps are white labeled and delivered to the client through their own developer account. End-user support documentation should be provided by them.
603.3 Accommodation of Communication Needs Not Applicable
  • Apps are white labeled and delivered to the client through their own developer account. End-user support documentation should be provided by them.

Legal Disclaimer (Company)

©2022 QuickSeries Publishing inc.

This Accessibility Conformance Report represents the status of the QuickSeries QuickConnect App for Android content management system on the Report Date listed in VPAT® Version 2.3 (Revised) – April 2019 template. QuickSeries cannot guarantee that any information in this Accessibility Conformance Report will remain accurate after the Report Date, but QuickSeries works continuously to monitor the accessibility of its products and provides updates from time to time. Any modification or customization to the product may render some or all of this Accessibility Conformance Report inapplicable. This Accessibility Conformance Report is provided “as is” and is for informational purposes only. QuickSeries specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document.