VPAT – ADA compliant certificate

myLIBRO Accessibility Conformance Report

Revised Section 508 Edition VPAT®

Version 2.3 (Revised) – April 2019
Name of Product/Version: myLIBRO
Alexa Skill Version: LIBRO 1.6.6.2
Mobile Application Version: myLIBRO 2.0.6
Product Description: Report
Date: July 12, 2019
Contact Information: support@conversight.ai

Notes:

This report covers accessibility conformance for myLIBRO available to end users of published mobile applications via play store(android), application store(ios) and Alexa skills via Amazon skill store.
 
Check this link [myLIBRO] http://www.conversight.ai/LIBRO/ for more details about the product.
 

Evaluation Methods Used:

Conformance to the listed accessibility standards has been evaluated by ConverSight.ai using a combination of static analysis tools and manual testing.
 

Applicable Standards/Guidelines

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

Standard/Guideline Included in report
Section1 194.21 Software Applications and Operating Systems(Yes)Section 1194.22 Web-based internet information and applications (Yes)
(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, Software Applications and Operating Systems

Notes:

Criteria Conformance Level Remarks and Explanations
(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. Supports LIBROAndroid application is designed to work only with touch-enabled devices and the on-screen keyboard and not use hardware keyboards by default. However, user can connect a hardware keyboard to an Android device for text input
(b) Applications shall not disrupt or disable activated features of other
products that are identified as accessibility features, where those
features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.
Supports LIBRO Android application user interface and controls do not disrupt, deactivate, or interfere with Android
operating system accessibility features such as High Contrast, system fonts, white on black inverse colors, zoom and Talkback.
(c) A well-defined on-screen indication of the current focus shall be provided, that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes. Supports LIBRO Android application provide a well-defined onscreen
indication of the current focus.
(d) Sufficient information about a user interface element including the
identity, operation and state of the element shall be available to assistive
technology. When an image represents a program element, the
information conveyed by the image must also be available in text.
Supports WAI-ARIA role, state and value information for LIBRO Android application user interface controls and elements are programmatically available to assistive technology. Functional images within the Android
application have descriptive alternative text.
(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application’s performance. Supports Images that convey information have proper alternative text, and the meaning of such images is consistent throughout LIBRO Android application.
(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes. Supports Textual information is programmatically available to assistive technology in LIBRO Android application.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Supports LIBRO Android application respects the Android operating system inverse color settings and does not override any default contrast settings.
(h) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Supports LIBRO Android application does not rely on color coding as the only means of conveying information.
(i) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels
shall be provided.
Not Applicable LIBRO Android application does not permit a user to adjust color and contrast settings in the user interface.
(j) Software shall not use flashing or blinking text, objects, or other
elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.
Supports LIBRO Android application has no flashing or blinking text, objects or other elements greater than 2Hz and
lower than 55Hz.
(k) When electronic forms are used, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Supports All electronic form controls in LIBRO Android application are accessible with the use of assistive technology such as Talkback.

Table 2: Success Criteria, Section 1194.22 Web-based Internet information and applications

Notes:

Criteria Conformance Level Remarks and Explanations
(a) A text equivalent for every non-text element shall be provided (e.g., via “alt”, “longdesc”, or in element content). Supports Images used in LIBRO Android application have meaningful alternative (alt) text descriptions. Nonrelevant or decorative images have null alt attributes or are inserted as a CSS background image. Images inserted as a CSS background image contain meaningful text alternatives.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Not Applicable LIBRO Android application does not provide any multimedia presentations.
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Supports LIBRO Android application does not use color or fontstyles alone to distinguish the importance of a visual element.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Not Applicable LIBRO Android application is a mobile-based application (not a document). To work correctly, the mobile app user interface requires the use of associated style sheets. The operating systems for Android phone devices do not provide any option to disable or read screen elements without associated style sheets.
(e) Redundant text links shall be provided for each active region of a server-side image map. Not Applicable LIBRO Android application does not use server-side image maps.
(f) Client side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. Not Applicable LIBRO Android application does not use client-side image maps.
(g) Row and column headers shall be identified for data tables. Not Applicable In LIBRO Android application, data tables are not used.
(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. Not Applicable LIBRO Android application does not use data tables.
(i) Frames shall be titled with text that facilitates frame identification and navigation Not Applicable No frames are currently used for interaction within LIBRO Android app.
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Supports LIBRO Android application does not cause the screen to flicker with a frequency greater than 2Hz and lower than 55Hz.
(k) A text only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. Not Applicable Text–only pages are not required because LIBRO Android application user interface has been coded to meet applicable standards, to the extent specified.
(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology. Supports LIBRO Android application uses JavaScript, WAI-ARIA and the most modern HTML5 techniques to provide interaction within the app. This allows assistive technology such as Talkback to read and transmit information back to the user.
(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l). Not Applicable LIBRO Android application does not require any applet or plug-in to work with its default functionality.
(n) When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Supports All the electronic form controls in LIBRO Android application are accessible with the use of assistive technology such as Talkback.
(o) A method shall be provided, that permits users to skip repetitive navigation links. Supports LIBRO Android application uses various document landmarks such as, and to help assistive technology users navigate to different sections within the app when the Talkback features are being used.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not Applicable LIBRO Android application does not require any time response as it keeps the user logged in to the app within that session.

Revised Section 508 Report

Notes:

Chapter 3: Functional Performance Criteria (FPC)

Notes:

Criteria Conformance Level Remarks and Explanations
302.1 Without Vision Supports LIBRO provides voice output and does not require vision to be used.
302.2 With Limited Vision Supports LIBRO provides voice output and does not require vision to be used.
302.3 Without Perception of Color Supports LIBRO provides voice output and does not
require vision to be used.
302.4 Without Hearing Not Applicable LIBRO include audio-only features that require hearing to be used.
302.5 With Limited Hearing Not Applicable LIBRO include audio-only features that
require hearing to be used.
302.6 Without Speech Not Applicable LIBRO requires speech input.
302.7 With Limited Manipulation Not Applicable Usage of LIBRO does not require fine
motor controls or simultaneous actions.
302.8 With Limited Reach and Strength Not Applicable No hardware is produced.
302.9 With Limited Language, Cognitive, and Learning Abilities Supports LIBRO provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

Chapter 4: Hardware

Notes: The product is a mobile software application and is not subject to the requirements of this section.

Chapter 5: Software

Notes:

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 Not Applicable LIBRO provide user control over platform features that are defined in the platform documentation as accessibility features.
502.2.2 No Disruption of Accessibility Features Supports LIBRO shall not disrupt platform features that are defined in the platform documentation as accessibility features.
502.3 Accessibility Services Heading cell – no response required Heading cell – no response required
502.3.1 Object Information Supports  
502.3.2 Modification of Object Information Supports  
502.3.3 Row, Column, and Headers Not Applicable LIBRO does not contain data table.
502.3.4 Values Supports  
502.3.5 Modification of Values Supports LIBRO supports values that can be set by
the user shall be capable of being set
programmatically, including through
assistive technology.
502.3.6 Label Relationships Supports  
502.3.7 Hierarchical Relationships Supports  
502.3.8 Text Supports  
502.3.9 Modification of Text Supports  
502.3.10 List of Actions Supports  
502.3.11 Actions on Objects Supports  
502.3.12 Focus Cursor Supports  
502.3.13 Modification of Focus Cursor Supports  
502.3.14 Event Notification Supports  
502.4 Platform Accessibility Features Not Applicable  
503 Applications Heading cell – no response required Heading cell – no response required
503.2 User Preferences Supports LIBRO respects user preferences from platform or OS settings.
503.3 Alternative User Interfaces Not Applicable LIBRO does not provide any alternative user interfaces that function as assistive technology.
503.4 User Controls for Captions and Audio Description Heading cell – no response required Heading cell – no response required
503.4.1 Caption Controls Not Applicable LIBRO does not include video content.
503.4.2 Audio Description Controls Not Applicable LIBRO does not include video content.
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 LIBRO does not support authoring tools when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format.
504.2.2 PDF Export Not Applicable LIBRO does not contain features capable of exporting PDF files.
504.3 Prompts Not Applicable LIBRO does not provide a mode of operation that prompts authors to create content.
504.4 Templates Not Applicable LIBRO does not support range of template uses for supported features and, as applicable, to file formats supported by the authoring tool.

Chapter 6: Support Documentation and Services

Notes:

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 Does Not Support LIBRO does not provide documentation with list and explaining how to use the accessibility and compatibility features.
602.3 Electronic Support Documentation Supports LIBRO document in electronic format, includes Web-based self-service support and explains how to use the features.
602.4 Alternate Formats for Non-Electronic Support Documentation Does not supports Non-electronic formats, alternate formats usable by individuals with disabilities is not provided now and shall be provided upon request by LIBRO.
603 Support Services Heading cell – no response required Heading cell – no response required
603.2 Information on Accessibility and Compatibility Features Supports LIBRO support services includes information on the accessibility and compatibility features.
603.3 Accommodation of Communication Needs Not Applicable LIBRO support services shall be provided directly to the user or through a referral to a point of contact and shall accommodate the communication needs of individuals with disabilities.

Legal Disclaimer (ConverSight.ai)

Content and information provided through our Services are provided for informational purposes on an “as is” basis at your sole risk. ConverSight.ai makes no guarantee as to the accurateness, completeness or quality of the information. ConverSight.ai shall not be liable or responsible for any errors, omissions or inaccuracies in the information or your reliance on the information. You are solely responsible for verifying the information as being appropriate for your personal use.

We have the right to take any of the following actions in our sole discretion at any time and for any reason without giving you any prior notice:

a) Restrict, suspect or terminate your access to all or any part of our Services;

b) Change, suspend or discontinue all or any part of our Services;

c) Refuse, move or remove any material that you submit to our sites for any reason;

d) Refuse, move, or remove any content that is available on our sites;

e) Establish general practices and limits concerning use of our sites.

You agree that we will not be liable to you or any third party for taking any of these actions. You understand and agree that our Services may include communications such as service announcements and administrative messages from us or from our partners and that these communications are considered part of the Services. You will not be able to opt out of receiving these messages. You also understand that our Services may include advertisements.