Voluntary Product Accessibility Template (VPAT) - Feedback Studio LTI Interface



Date Created: July 2016
Product Name: Turnitin LTI Interface
Version: STULTI2016Q3
Contact for more Information: Sun Oh soh@turnitin.com




Supporting Features (second column on VPAT)



Supports Use this language when you determine the product fully meets the letter and intent of the Criteria.
Supports with exceptions Use this language when you determine the product does not fully meet the letter and intent of the Criteria, but provides some level of access relative to the Criteria.
Supports through equivalent facilitation Use this language when you have identified an alternate way to meet the intent of the Criteria or when the product does not fully meet the intent of the Criteria.
Supports when combined with compatible AT Use this language when you determine the product fully meets the letter and intent of the Criteria when used in combination with Compatible AT. For example, many software programs can provide speech output when combined with a compatible screen reader (commonly used assistive technology for people who are blind).
Does not Support Use this language when you determine the product does not meet the letter or intent of the Criteria.
Not Applicable Use this language when you determine that the Criteria do not apply to the specific product.
Not Applicable - Fundamental alteration exception applies Use this language when you determine a Fundamental Alteration of the product would be required to meet the Criteria (see the access board standards for the definition of "fundamental alteration").




Summary Table



Criteria Supporting Features Remarks and explanations
Section 1194.21 Software Applications and Operating Systems Supports with exceptions See details in Section 1194.21.
Section 1194.22 Web-based internet information and applications Supports with exceptions See details in Section 1194.22.
Section 1194.23 Telecommunications Products Not applicable  
Section 1194.24 Video and Multi-media Products Not applicable  
Section 1194.25 Self-Contained, Closed Products Not applicable  
Section 1194.26 Desktop and Portable Computers Not applicable  
Section 1194.31 Functional Performance Criteria Supports with exceptions See details in Section 1194.31.
Section 1194.41 Information, documentation, and support. Supports with exceptions See details in Section 1194.41.




Section 1194.21: Software Applications and Operating Systems



Criteria Supporting Features 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. Supported

Functionality can be performed using the keyboard-alone.

(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 The LTI workflow does not disrupt or disable activated accessibility features.
(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. Supported Focus programmatically changes on keystroke commands.
(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 Text elements are screen reader optimized. Images are not applicable for Turnitin Accessibility.
(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. Not Applicable Bitmap images are not used to identify programmatic elements.
(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 Screen reader optimized.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Supported No override of end user settings.
(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. Not applicable Animation is not used in the application.
(i) 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 Color coding is not the only means of conveying information.
(j) 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 The product does not permit users to adjust color and contrast settings.
(k) 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 The product does not use flashing or blinking elements.
(l) 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

Form controls include programmatically associated labels and are operable using assistive technologies.




Section 1194.22: Web-Based Internet Information and Applications



Criteria Supporting Features 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 have a text equivalent.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Not applicable Product does not contain 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 Color coding is not used as the only means of conveying information.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Supports Pages are readable without CSS.
(e) Redundant text links shall be provided for each active region of a server-side image map. Not applicable Server-side image maps are not used.
(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 Client-side image maps are not used.
(g) Row and column headers shall be identified for data tables. Supports Row and column headers are appropriately labeled.
(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. Supports Appropriate markup is used for data tables.
(i) Frames shall be titled with text that facilitates frame identification and navigation Supports All pages with Titles & Headers are screen reader optimized.
(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 The product does not use flickering elements.
(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 The content can be made accessible using currently available open web technologies.
(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

All page items are screen reader optimized. Interface elements are announced and keystroke operable.

(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 The product does not require applets.
(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 Form controls include programmatically associated labels and are operable using assistive technologies.
(o) A method shall be provided that permits users to skip repetitive navigation links. Supports Standard keystrokes allow users to skip sections.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Supports with exceptions Screen Reader optimized depending on browser.




Section 1194.31: Functional Performance Criteria Voluntary Product Accessibility Template



Criteria Supporting Features Remarks and explanations
(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided. Supports

Interface elements are operable using assistive technologies

The text-only view supports assistive technologies. Refer to 1194.21(d), 1194.21(l), and 1194.22(n) for details.

(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided. Supports Screen reader optimized and keystroke navigation functionality.
(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided Not applicable User hearing is not required.
(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. Not applicable Audio information is not used.
(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided. Supports User speech is not required.
(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. Supports Product is functional using keyboard alone




Section 1194.41: Information, Documentation and Support



Criteria Supporting Features Remarks and explanations
(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge Supports with exceptions Please send specific inquiries to accessibility@turnitin.com
(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge. Supports with exceptions Please send specific inquiries to accessibility@turnitin.com
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. Supports with exceptions Please send specific inquiries to accessibility@turnitin.com