LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (February 2012)Back to main WAG pageJoin or leave WAG (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 2 Feb 2012 16:09:01 +0000
Reply-To:     UGA Web Accessibility Group <WAG@LISTSERV.UGA.EDU>
Sender:       UGA Web Accessibility Group <WAG@LISTSERV.UGA.EDU>
From:         Janet Sylvia <jsylvia@UGA.EDU>
Subject:      WCAG 2.0 and YouTube Meeting Notes
Content-Type: multipart/alternative;

Dear WAG,

As requested, below are notes and resource links from yesterday's meeting on "WCAG 2.0 Audio/Video Requirements and YouTube Captioning Compliance".

Please feel free to share your YouTube experiences, comments, questions, etc. via the listserv. This is a great opportunity for us to learn from each other's experience with making YouTube content 508 compliant.

Thanks, Janet

***********

Background: The Section 508 Refresh (2nd draft) was released December 2011 and is open for public comment through March 7, 2012. This version of the Refresh directs us to comply with WCAG 2.0 Levels A and AA as part of Section 508 compliance. The WCAG 2.0 requirements for "time based media" were discussed today; a link to WebAIM's WCAG 2.0 checklist is provided below. Sample Workflow and Resources for creating Text Transcripts, Synchronized Captions and Video Descriptions are also provided below.

These guidelines should be followed as part of the existing Section 508 Standards, as well. They were discussed today in terms of the WCAG 2.0 checklist and terminology.

WebAIM’s WCAG 2.0 Checklist

http://webaim.org/standards/wcag/checklist

W3C Multimedia FAQs (examples) http://www.w3.org/2008/06/video-notes

Sample Workflow for Audio/Video Productions:

1. Produce time-based media project; if possible incorporate descriptions of video content in spoken word, which may eliminate the need for a Video Description file, more on this topic below.

2. Create a descriptive Text Transcript: manually transcribe or outsource

For manual transcription try: Universal Subtitles (transcribe+caption for YouTube), MAGPie (transcribe+caption), Express Scribe (transcribe only), etc.

To outsource, may want to consider vendors like: Casting Words, Automatic Sync Technologies, Tech Synergy, etc.

Guidelines for creating text transcripts are available at:

Transcripts on the Web

http://www.uiaccess.com/transcripts/transcripts_on_the_web.html

3. Synchronize transcript with time-based media; edit resulting caption file, as needed

Based on our YouTube experience (your experience may vary):

YouTube has a *transcript* Beta upload option which can synchronize .txt transcription file with your uploaded video, thus creating your caption file. Captions can be very accurate (not to be confused with YouTube auto-transcribe feature which can be highly inaccurate). After YouTube creates the synchronized caption file, the captions "should" play when selecting the CC button on the YouTube video interface; if not it could be your browser version/type so try in another browser -- see below for more info on this. To edit: the YouTube caption file can be downloaded as .srt file, opened in text editor such as Notepad, edited as needed, saved as .srt and uploaded back to YouTube with corrections.

You can also manually create the caption file (ex: using Universal Subtitles) or outsource to 3rd party vendors (ex: Automatic Sync Technologies); always edit captions for accuracy.

YouTube requires SBV or SRT caption file format; Universal Subtitles allows you to create SRT format; online conversion tools are also available in you have existing captions in other formats, or if you need to convert the YouTube SRT captions to another format (Ohio State has a free online converter, Subtitle Edit, etc.)

Note: The YouTube system allows you to upload other types of caption files; however, the CC functionality will only work if the file you uploaded is SBV or SRT.

Best practices for creating caption files are available at:

Captioning Key

http://www.dcmp.org/captioningkey/text.html •WGBH Captioning FAQ http://main.wgbh.org/wgbh/pages/mag/services/captioning/faq/sugg-styles-conv-faq.html

4. Create Video Description file: not needed for talking heads, not needed if description of video elements including slide text, graphs, charts, etc. are provided as part of the audio narration (i.e. spoken word); otherwise you are required to describe key visual elements needed for comprehension of your video content such as: on-screen text or dialogue, sounds, settings, background, actions, expressions, graphics, and more. You can also combine the descriptive Text Transcript (text of the spoken word) with your Video Description (what is taking place in video) as a single HTML file. Sample of combined document is available at:

W3C WAI WCAG Curriculum

http://www.w3.org/WAI/wcag-curric/catch.htm

5. Create Audio Description (TBD: on hold until final release of Section 508 Refresh in 2013)

6. Publish content together, HTML is the preferred format for text files.

Examples:

Audio-only file with descriptive Text Transcript in HTML format;

Video-only file with Video Description in HTML format;

Captioned Audio/Video file with Text Transcript in HTML format and Video Description in HTML format (can be combined as one HTML file). Note: for audio+video content, the transcribed audio serves two purposes: it is used to create the synchronized caption file, and it is used to create the descriptive Text Transcript in HTML format.

YouTube and 508 Compliance

YouTube: allows options for delivery of 508 compliant content including captioned video, Text Transcript, Video Description and built-in Interactive Text Transcript; however, end-user experience (i.e. ability to access your compliant content) may vary widely depending on browser/version, lack of keyboard accessibility, difficulty locating certain icons for some screen readers. Important to be aware of this.

In general, it is possible to deliver captioned Audio/Video files via YouTube, where YouTube (in some cases) will also auto-generate an Interactive Text Transcript, and you can also upload a Video Description (in YouTube "description" field); however, it isn't guaranteed that your audience will be able to locate or access each of these elements within the YouTube interface. For example: last week several of us tried to access the same 508-compliant video on YouTube; some couldn't get the CC (closed captions) to work and others couldn't get the "Interactive Transcripts" to work. It's important to be aware this may happen to your audience, as well. Evenso, we should still provide 508-compliant features for our YouTube content; it not only allows us to be 508-compliant, but it also has proven to be very beneficial for those who can access the captions, transcripts and descriptions.

There is a very good resource available from Ohio State University called:

Captioning YouTube Video and Providing Accessible Controls

http://wac.osu.edu/examples/youtube-player-controls/

************************

Janet Sylvia Web Accessibility Group, Co-Leader Digital Media Professional OCTS-CAES 107 Hoke Smith Annex University of Georgia Athens, GA 30602 706-542-3936


[text/html]


Back to: Top of message | Previous page | Main WAG page