QuickSeries Accessibility Conformance Report

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)

• 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.

Improvements coming soon:

• We will soon be using artificial intelligence to automatically generate alternative text on images uploaded to the apps.

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)

• 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)

• 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)

• 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)

• App pages are built using Apple's iOS 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)

• App pages are built using Apple's iOS 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)

• 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 Apple 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)

• 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 ratiOS 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)

2.1.1 Keyboard (Level A)

Also applies to:

Revised Section 508

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

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)

• A physical keyboard can be used with the app to type content and to navigate with Apple'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)

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)

• 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)

• 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

• 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)

• 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)

• 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)

• 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 created incorrectly, 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)

• iOS 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)

• 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)

3.3.1 Error Identification (Level A)

Also applies to:

Revised Section 508

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

• 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)

• 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)

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)

• The application provides name, role, state and value information to assistive technologies.

1.2.4 Captions (Live) (Level AA)

Also applies to:

Revised Section 508

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

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)

1.4.3 Contrast (Minimum) (Level AA)

Also applies to:

Revised Section 508

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

• 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)

App modules have been updated to use Apple's SwiftUI API which supports text resizing.

Side menu

Access codes

User profile

Settings

Assessment & quiz personal data collection page

Side menu eGuide details page

FAQ

Checklist

Video Library

PDF Library

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)

• 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

• 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)

• 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)

• When text fields receive focus, a vertical bar is displayed in the field, indicating that the user can insert text.
• iOS VoiceOver 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)

• 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

• 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

• 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)

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)

• Supports when combined with compatible assistive technology.
• All app pages are built using Apple's iOS 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 Apple'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.

• 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 ratiOS 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• Our app does not disrupt any OS accessibility features.

• The app mostly responds well to OS-based accessibility preferences (such as contrast, color filters, focus cursor)

Exceptions:

Not all modules have been updated to take advantage of Apple's SwiftUI API's built-in accessibility features, such as text resizing.

Notes:

App modules that have been updated to use Apple's SwiftUI API supports text resizing.

Side menu

Access codes

User profile

Settings

Assessment & quiz personal data collection page

Side menu eGuide details page

FAQ

Checklist

• Video Library

PDF Library

• 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.

• 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.