Platform Accessibility

YuJa Enterprise Video Platform Voluntary Product Accessibility Template (VPAT)

Download PDF

Introduction

YuJa Inc strives to create an equal and consistent media experience for all individuals. We believe that accessibility is not simply a rulebook; it is a deep commitment to creating meaningful experiences and enabling users to attain their goals.

The Voluntary Product Accessibility Template (VPAT) is a document which evaluates how accessible a particular product is according to the Section 508 Standards. To recognize and evaluate our accessibility compatibility, we use the Section 508 of the Rehabilitation Act issued in the United States federal government.

This document assesses the YuJa Enterprise Video Platform against the VPAT. including detailed assessment on each of the requirements of VPAT.


Scope of VPAT

The scope of the VPAT evaluation is focused on the core sections of the platform that are used by students and instructors, namely:

  1. YuJa Student Login
  2. YuJa Media Channel List
  3. YuJa Media Library (My Media)
  4. YuJa Media Player

Explanation of VPAT Certification

The United States Federal Government provides an Evaluation Template that sub-divides the compliance into a set of tables designated Section 1194.xx Tables. We have provided a summary of which tables are applicable to the YuJa Enterprise Video Platform and our compliance with these requirements.


Compliance Summary Tables

Section Support Level

Section 1194.21 – Software Application and Operating Systems

Supports with Exceptions

Section 1194.22 – Web-based Internet Information and Applications

Supports with Exceptions

Section 1194.23 – Telecommunications Products

Not Applicable

Section 1194.24 – Video and Multimedia 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

Not Applicable

Section 1194.41 – Information, Documentation, Support

Supports


Section 1194.21 Software Applications and Operating Systems – Detail
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.

 Supports with Exceptions

All actions can be performed with a keyboard as it pertains to user accessing the tools with the exception of re-positioning or resizing the window size or location on the desktop.

(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

No tested features within scope pertaining to accessibility are modified or disabled as a result of using the application.

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

 Support

All tested features within scope preserve a well-defined on-screen indication of the current focus and supports assistive technology.

(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 with Exceptions

In all tested features within scope show action elements as text with the exception of the following buttons: maximize window, minimize window

(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 used to denote controls are consistently used throughout the 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.

 Not applicable

The functions provided by the operating system for displaying text are not used by features within scope. 

(g) Applications shall not override user selected contrast and color selections and other individual display attributes.

Support

No user-selected features related to contrast or color selections are overridden.

(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.

 Supports

Any instances of animation within the tested features within scope also provide the same information in a non-animated manner.

(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

 All tested features within scope preserve a well-defined on-screen indication of the current focus and supports assistive technology.

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

 Supports

No user-selected features related to contrast or color selections are overridden.

(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

 No user-selected features related to flashing or blinking are utilized within the application.

(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

All electronics forms are assessable using Assistive Technologies through the use of HTML-based title and label tags.

Section 1194.22 Web-based Internet information and applications – Detail
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

All images that are used to convey meaning to a user have appropriate ALT tags 

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

 Supports

Automatic captions are provided that are synchronized with the playback of 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 is not exclusively used to convey meaning. 

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

 Supports

HTML remains in the correct order when a given CSS is disabled.

(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 within the application.

(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 within the application.

(g) Row and column headers shall be identified for data tables.

 Supports

Table headers have appropriate row and column headers.

(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

This type of table is not utilized within the application.

(i) Frames shall be titled with text that facilitates frame identification and navigation

 Supports

Frames and iFrames have appropriate titles.

(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

No pages within the site have elements that cause flicker.

(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 existing web application and site meets compliance and hence an equivalent text-only page is not required.

(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 with Exceptions

In all tested features within scope show action elements as text with the exception of the following buttons: maximize window, minimize window.

(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).

 Supports

No pages within the site rely on applets or plug-ins as their exclusive means of performing the tasks. For example, all components support HTML5 for user tasks.

(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

For electronic forms, HTML tags for ALT and TITLE are used to convey meaning.

(o) A method shall be provided that permits users to skip repetitive navigation links.

 Not Applicable

In the tested features in scope, not repetitive navigation links were identified. 

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Not Applicable

No timed response elements are used within the application.

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

Product documentation is provided in HTML formats at no additional cost.

(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

Product documentation is provided in HTML formats at no additional cost.

(c) Support services for products shall accommodate the communication needs of end-users with disabilities.

 Supports

Support services are available through both toll-free and support tickets.

Contact Sales

A YuJa representative will be in touch as soon as possible.






Send us an email or message






Send us an email or message












Industry Solutions

YuJa serves enterprise clients across industry verticals including higher-ed, K-12, state and local government, non-profit, healthcare, and corporations.

Questions? Give Us a Call

Toll-Free (United States and Canada)

1-888-257-2278

Toll Free (United Kingdom)

+44 (800) 368-8712

International

+1 (408) 508-6796