Platform Accessibility

YuJa Enterprise Video Platform WCAG 2.0 Checklist

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.

Web Content Accessibility Guidelines (WCAG) are part of a set of guidelines established by the W3C, a group of individuals and organizations from around the world who develop resources to help make the Web more accessible to people with disabilities.

This document assesses the YuJa Enterprise Video Platform against the WCAG 2.0 conformance levels. including detailed assessment on each of the requirements of WCAG 2.0.

Success Criteria Comments

Guideline 1.1 – Text Alternatives – Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

1.1.1 Non-text Content (Level A)

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.

Yes.

Non-text elements use a text alternative.

Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.)

Yes.

Controls and inputs contain descriptive or labels describing the context.

Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)

Not Applicable.

All time-based media is user generated content which is exempt and governed by a different set of guidelines.

Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.

Not Applicable

Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.

Not Applicable.

CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.

Not Applicable.

Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.

Yes.

Custom style sheets can be disabled by assistive technologies.


Success Criteria Comments

Guideline 1.2 – Time-based Media – Provide alternatives for time-based media.

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:

  • Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
  • Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.

Not applicable.

All prerecorded audio-only and prerecorded video-only media is user generated content which is exempt and governed by a different set of guidelines.

1.2.2 Captions (Prerecorded) (Level A)

Synchronized captions are provided for non‐live, web‐based video (YouTube videos,

etc.)

Yes.

The Platform offers capabilities to pre-generate and upload synchronized captions for prerecorded videos. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

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

A descriptive text transcript OR audio description audio track is provided for non‐live, web‐based video

Yes.

The Platform offers capabilities to upload an Audio Description track for prerecorded videos. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

1.2.4 Captions (Live) (Level AA)

Synchronized captions are provided for all live multimedia that contains audio (audio-only broadcasts, web casts, video conferences, Flash animations, etc.)

Yes.

The Platform offers capabilities to integrate with live captioning products. Note: All live media is user generated content which is exempt and governed by a different set of guidelines.

1.2.5 Audio Description (Prerecorded) (Level AA)

Audio descriptions are provided for all video content

Note: Only required if the video conveys content visually that is not available in the default audio track.

Yes. The Platform offers capabilities to upload an Audio Description track for prerecorded videos. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

1.2.6 Sign Language (Prerecorded) (Level AAA)

A sign language video is provided for all media content that contains audio.

Yes.

The Platform offers capabilities to upload and link a secondary video file that can contain a sign language video. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

1.2.7 Extended Audio Description (Prerecorded) (Level AAA)

When an audio description track cannot be added to video due to audio timing (e.g., no pauses in the audio), an alternative version of the video with pauses that allow audio descriptions is provided.

Yes.

The Platform offers capabilities to upload and link a secondary video file that contains an alternative video with pauses that can be used with Audio Description content. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

1.2.8 Media Alternative (Prerecorded) (Level AAA)

A descriptive text transcript is provided for all pre‐recorded media that has a video track.

Yes.

The Platform offers capabilities to upload an associated descriptive text transcript for prerecorded videos. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

1.2.9 Audio‐only (Live) (Level AAA)

A descriptive text transcript (e.g., the script of the live audio) is provided for all live

content that has audio.

Yes.

The Platform offers capabilities to integrate with live captioning products. Note: All live media is user generated content which is exempt and governed by a different set of guidelines.


Success Criteria Comments

Guideline 1.3 – Adaptable – Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

1.3.1 Information and Relationships (Level A)

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Yes.

  • Headings are used to convey structural meaning of presented content.
  • Tables use headings and appropriate summaries.
  • Pages are structured to be linear in nature and do not require a style sheet to be read by accessibility tools.

1.3.2 Meaningful Sequence (Level A)

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

Yes.

Entity relationships within YuJa are defined hierarchically and appropriate linear navigation elements are provided. Navigation elements are text-based and can be utilized in a mouse-free manner alongside screen-readers. Headings are used to convey relationships between content including reading sequence. Pages are designed to be linear in nature.

1.3.3 Sensory Characteristics (Level A)

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.

Yes.

Any concept that uses shapes, sizes, or visual locations, orientation or sound has equivalent hidden (alt-text) or visible text.


Success Criteria Comments

Guideline 1.4 – Distinguishable – Make it easier for users to see and hear content including separating foreground from background,

1.4.1 Use of Color (Level A)

  • Color is not used as the sole method of conveying content or distinguishing visual elements.
  • Color alone is not used to distinguish links from surrounding text unless the luminance contrast between the link and the surrounding text is at least 3:1 and an additional differentiation (e.g., it becomes underlined) is provided when the link is hovered over or receives focus.

Yes.

Color and font styles that are used to convey information are always also communicated through language. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

1.4.2 Audio Control (Level A)

A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays on a page for more than 3 seconds.

Yes.

No specific media plays automatically within the Platform. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

1.4.3 Contrast (Minimum) (Level AA)

  • Text and images of text have a contrast ratio of at least 4.5:1.
  • Large text (over 18 point or 14 point bold) has a contrast ratio of at least 3:1

Yes.

All content and presentation of visual material meets these criteria. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

1.4.4 Resize text (Level AA)

The page is readable and functional when the text size is doubled.

Yes.

Text can be resized by web browser (or other assistive technologies) zoom and scaling tools. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

1.4.5 Images of Text (Level AA)

If the same visual presentation can be made using text alone, an image is not used to

present that text.

Yes.

The Platform does not use images to convey meaning. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

1.4.6 Contrast (Enhanced) (Level AAA)

  • Text and images of text have a contrast ratio of at least 7:1.
  • Large text (over 18 point or 14 point bold) has a contrast ratio of at least 4.5:1

Yes.

All content and presentation of visual material meets these criteria. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

1.4.7 Low or No Background Audio (Level AAA)

Audio of speech has no or very low background noise so the speech is easily distinguished

Yes.

No such media is pre-loaded within the Platform. Note: All media is user generated content which is exempt and governed by a different set of guidelines.

1.4.8 Visual Presentation (Level AAA)

Blocks of text over one sentence in length:

  • Are no more than 80 characters wide.
  • Are NOT fully justified (aligned to both the left and the right margins).
  • Have adequate line spacing (at least 1/2 the height of the text) and paragraph spacing (1.5 times line spacing).
  • Have a specified foreground and background color. These can be applied to specific elements or to the page as a whole using CSS.
  • Do NOT require horizontal scrolling when the text size is doubled.

Yes.

All style sheets that govern the presentation meet these criteria. Additionally:

  • The Platform allows custom foreground and background colors to be applied
  • Platform text does no use fully justified formatting

1.4.9 Images of Text (No Exception) (Level AAA)

Text is used within an image only for decoration (image does not convey content) OR when

the information cannot be presented with text alone.

Yes.

The Platform does not use images to convey meaning. Note: All media is user generated content which is exempt and governed by a different set of guidelines.


Success Criteria Comments

Guideline 2.1 – Keyboard Accessible – Make all functionality available from a keyboard

2.1.1 Keyboard (Level A)

  • All page functionality is available using the keyboard, unless the functionality cannot be
  • accomplished in any known way using a keyboard (e.g., free hand drawing).
  • Page‐specified shortcut keys and accesskeys (accesskey should typically be avoided) do not conflict with existing browser and screen reader shortcuts.

Yes.

Keyboard controls can be used exclusively through the implementation of tab order and dedicated one-click prerecorded video player controls.

2.1.2 No Keyboard Trap (Level A)

Keyboard focus is never locked or trapped at one particular page element. The user can navigate to and from all navigable page elements using only a keyboard.

Yes. The Platform does not have any keyboard focus traps.

2.1.3 Keyboard (No Exception) (Level AAA)

All page functionality is available using the keyboard.

Yes. Keyboard controls can be used exclusively through the implementation of tab order and dedicated one-click prerecorded video player controls.


Success Criteria Comments

Guideline 2.2 – Enough Time – Provide users enough time to read and use content.

2.2.1 Timing Adjustable (Level A)

If a page or application has a time limit, the user is given options to turn off, adjust, or extend that time limit. This is not a requirement for real‐time events (e.g., an auction), where the time limit is absolutely required, or if the time limit is longer than 20 hours.

Yes. Page expiry is the only time limit in the application which is done for security purposes.

2.2.2 Pause, Stop, Hide (Level A)

  • Automatically moving, blinking, or scrolling content that lasts longer than 3 seconds can be paused, stopped, or hidden by the user. Moving, blinking, or scrolling can be used to draw attention to or highlight content as long as it lasts less than 3 seconds.
  • Automatically updating content (e.g., automatically redirecting or refreshing a page, a news ticker, AJAX updated field, a notification alert, etc.) can be paused, stopped, or hidden by the user or the user can manually control the timing of the updates.

Yes. Any animation is used to provide the status of an operation where without it, users might be unaware of the status if not provided.

2.2.3 No Timing (Level AAA)

The content and functionality has no time limits or constraints.

Yes.

Page expiry is the only time limit in the application which is done for security purposes.

2.2.4 Interruptions (Level AAA)

Interruptions (alerts, page updates, etc.) can be postponed or suppressed by the user.

Yes.

Browser alerts can be disabled through account settings. No other interruptions are present.

2.2.5 Re‐authenticating (Level AAA)

If an authentication session expires, the user can re‐authenticate and continue the activity without losing any data from the current page.

Yes. Expiration is automatically disabled when an activity is in progress.


Success Criteria Comments

Guideline 2.3 – Seizures Do not design content in a way that is known to cause seizures.

2.3.1 Three Flashes or Below Threshold (Level A)

No page content flashes more than 3 times per second unless that flashing content is sufficiently small and the flashes are of low contrast and do not contain too much red.

Yes.

All Platform design elements meet this requirement.

2.3.2 Three Flashes (Level AAA)

No page content flashes more than 3 times per second.

Yes.

All Platform design elements meet this requirement.


Success Criteria Comments

Guideline 2.4 – Navigable – Provide ways to help users navigate, find content, and determine where they are,

2.4.1 Bypass Blocks (Level A)

  • A link is provided to skip navigation and other page elements that are repeated across web pages.
  • If a page has a proper heading structure, this may be considered a sufficient technique instead of a “Skip to main content” link. Note that navigating by headings is not yet supported in all browsers.
  • If a page uses frames and the frames are appropriately titled, this is a sufficient technique for bypassing individual frames.

Yes. Page design incorporates visual tab stops

2.4.2 Page Titled (Level A)

The web page has a descriptive and informative page title.

Yes. Each page uses title and appropriate header tags.

2.4.3 Focus Order (Level A)

The navigation order of links, form elements, etc. is logical and intuitive.

Yes. Pages are laid out with a logical tab order.

2.4.4 Link Purpose (In Context) (Level A)

  • The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone, or from the link text and it’s context (e.g., surrounding paragraph, list item, table cell, or table headers).
  • Links (or form image buttons) with the same text that go to different locations are readily distinguishable.

Yes. Hyperlinks are contextual in nature with a relevant description associated with them.

2.4.5 Multiple Ways (Level AA)

Multiple ways are available to find other web pages on the site ‐ at least two of: a list of related pages, table of contents, site map, site search, or list of all available web pages.

Yes. Pages use a consistent, hierarchical navigation mechanism that can be operated alongside browser search-and-find, as well as assistive technologies.

2.4.6 Headings and Labels (Level AA)

Page headings and labels for form and interactive controls are informative. Avoid duplicating heading (e.g., “More Details”) or label text (e.g., “First Name”) unless the structure provides adequate differentiation between them.

Yes.

Pages are designed to have relevant descriptions, headers, and labels. Duplication is avoided to prevent effective use with assistive technologies.

2.4.7 Focus Visible (Level AA)

It is visually apparent which page element has the current keyboard focus (i.e., as you tab through the page, you can see where you are).

Yes.

Pages are laid out with a logical tab order.

2.4.8 Location (Level AAA)

If a web page is part of a sequence of pages or within a complex site structure, an indication of the current page location is provided, for example, through breadcrumbs or specifying the current step in a sequence (e.g., “Step 2 of 5 ‐ Shipping Address”).

Yes.

Page titles, headings and navigation elements indicate locations across the site structure. This includes the use of consistent breadcrumbs to indicate current location.

2.4.9 Link Purpose (Link Only) (Level AAA)

  • The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone.
  • There are no links (or form image buttons) with the same text that go to different locations.

Yes.

Hyperlinks are contextual in nature with a relevant description associated with them.

2.4.10 Section Headings (Level AAA)

Beyond providing an overall document structure, individual sections of content are designated using headings, where appropriate.

Yes.

Both titles and headings are used for the purposes of organizing overall site structure.


Success Criteria Comments

Guideline 3.1 – Readable – Make text content readable and understandable

3.1.1 Language of Page (Level A)

The language of the page is identified using the HTML lang attribute (<html lang=”en”>, for example).

Yes.

The HTML Language tag is used to establish the page’s language.

3.1.2 Language of Parts (Level AA)

When appropriate, the language of sections of content that are a different language are identified, for example, by using the lang attribute (<blockquote lang=”es”)>

Yes. If applicable, when alternate languages are used, appropriate HTML tags are applied.

3.1.3 Unusual Words (Level AAA) Words that may be ambiguous, unknown, or used in a very specific way are defined through adjacent text, a definition list, a glossary, or other suitable method.

Yes. Additional help documentation is provided as needed.

3.1.4 Abbreviations (Level AAA)

Expansions for abbreviations are provided by expanding or explaining the definition the first time it is used, using the <abbr> element, or linking to a definition or glossary. NOTE: WCAG 2.0 gives no exception for regularly understood abbreviations (e.g., “HTML” on a web design site must always be expanded).

Yes.

The design methodology of the Platform discourages abbreviations. When used, additional help documentation is provided as needed.

3.1.5 Reading Level (Level AAA)

A more understandable alternative is provided for content that is more advanced than can be reasonably read by a person with roughly 9 years of primary education.

Yes.

Language level used is of a lower-level high school student. This criterion is currently not evaluated extensively.

3.1.6 Pronunciation (Level AAA)

If the pronunciation of a word is vital to understanding that word, its pronunciation is provided immediately following the word or via a link or glossary.

Yes. When necessary to support a word’s understanding, the supporting help documentation provides additional clarity and context.


Success Criteria Comments

Guideline 3.2 – Predictable – Make Web pages appear and operate in predictable ways

3.2.1 On Focus (Level A)

When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop‐up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user.

Yes.

3.2.2 On Input (Level A)

When a user inputs information or interacts with a control, it does not result in a substantial change to the page, the spawning of a pop‐up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user unless the user is informed of the change ahead of time.

Yes.

The only exception is:

  • The default browser behavior for drop-down tabs is to not initiate changes when tabbed into.

3.2.3 Consistent Navigation (Level AA)

Navigation links that are repeated on web pages do not change order when navigating through the site.

Yes.

Page navigation elements are consistent across the Platform.

3.2.4 Consistent Identification (Level AA)

Elements that have the same functionality across multiple web pages are consistently identified. For example, a search box at the top of the site should always be labeled the same way.

Yes.

Components – including icons, labels, and links – use a consistent labeling throughout the Platform.

3.2.5 Change on Request (Level AAA)

Substantial changes to the page, the spawning of pop‐up windows, uncontrolled changes of keyboard focus, or any other change that could confuse or disorient the user must be initiated by the user. Alternatively, the user is provided an option to disable such changes.

Yes.

In situations that meet this requirement, an alternate mechanism to disable is provided.


Success Criteria Comments

Guideline 3.3 – Input Assistance – Help users avoid and correct mistakes

3.3.1 Error Identification (Level A)

If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.

Yes.

Input errors are communicated via error messages with appropriate dialog headers and resolution steps.

3.3.2 Labels or Instructions (Level A)

Labels or instructions are provided when content requires user input.

Yes.

Input forms have clear headings, labels and buttons.

3.3.3 Error Suggestion (Level AA)

If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.

Yes.

Input errors are communicated via error messages with appropriate dialog headers and resolution steps.

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

If the user can change or delete legal, financial, or test data, the changes/deletions are reversible, verified, or confirmed.

Not Applicable.

3.3.5 Help (Level AAA)

Provide instructions and cues in context to help in form completion and submission.

Yes.

Additional help documentation is provided as needed.

3.3.6 Error Prevention (All) (Level AAA)

If the user can submit information, the submission is reversible, verified, or confirmed.

Yes.

Form submissions are validated for correctness and any errors are identified and communicated to the user. Appropriate mechanisms to correct and re-submit are provided.


Success Criteria Comments

Guideline 4.1 – Compatible – Maximize compatibility with current and future user agents, including assistive technologies

4.1.1 Parsing (Level A)

Significant HTML/XHTML validation/parsing errors are avoided. Check at

https://validator.w3.org

Yes.

Platform pages are validated against and conform to XHTML 1.0 transitional specifications.

4.1.2 Name, Role, Value (Level A)

Markup is used in a way that facilitates accessibility. This includes following the HTML/XHTML

specifications and using forms, form labels, frame titles, etc. appropriately.

Yes.

Form controls and visual elements are developed in a manner that is consistent with HTML specifications.

Schedule a Demo






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