This section outlines the guidelines for submitting media files to PBS LearningMedia via the CMS tool. Please adhere to these guidelines to ensure the content submission process goes smoothly.
Key: = supported = not supported
Web Delivery/COVE Spec
|Audio Stream BitRate||192 Kbps||48 Kbps|
Audio Stream BitRate Mode
Number of Audio Channels
|2 (Stereo)||1 (Mono)|
|Audio Channel's Positions||L, R||C|
|Sampling Rate||48 KHz||44.1 KHz|
|Bit Depth||16 bits||16 bits|
** Preferred format.
|Acceptable caption formats|
|File Type||Supported for ingest||Output format|
** Preferred format.
When a user mouses over your video, a bar appears at the bottom of the video. Within the bar, a CC icon indicates that your video contains closed captions. If the CC icon does not appear in the bar, closed captioning is not available for your video.
Click image to expand
The following document formats are supported for import:
|Supported document formats|
|Import File Type||Supported|
DOC (Microsoft Word) / DOCX
|PDF (Adobe's Portable Document Format)|
|XLS (Excel File) / XLSX|
Because documents need to be downloaded for use, they will not be converted and will maintain their original format. If you do not want your document to be editable submit it in a PDF format.
- Images intended to be used as assets can be any aspect ratio, and ideally should not be less than 1024 pixels wide.
- Images greater than 1200 pixels wide or greater than 900 pixels high may force most users to scroll to see the entire image. Unless this is intentional and supportive of the learning goal of the asset, it should be avoided.
|Acceptable image formats|
|Type of Image||Requirements|
|Poster Images (and thumbnails)|
|Station website banner|
- HTML may be written according to the HTML 4.01 Transitional, XHTML 1.0, or HTML5 doctype.
- All HTML files must declare a valid doctype. (HTML will be validated against W3C guidelines. It is suggested that all files are validated before submitting to PBS. There are free utilities available to achieve this.)
- HTML must be Section 508 compliant.
- When targeting a version of Flash, it is suggested that interactive developers target the lowest version number that supports the technology needed to produce the interactive.
The following is a list of target browsers:
- Internet Explorer 7.0+
- Firefox 3.5+
- Safari 5.0+
Interactive Package Construction
- Interactives that contain multiple files should be delivered in ZIP archives containing all required files and directory structures needed to experience the object.
- At the root of the ZIP archive should be a manifest file called manifest.txt. The manifest should contain the following information, and nothing else:
- Title: Title of interactive
- Creator: Creator of interactive Creator
- Email: Email of interactive Creator
- Description: Short description of interactive
- Date Created: Date interactive was created
- The ZIP archive should also contain an index.html file at the root of the archive
- Only the index.html and the manifest.txt files should be located in the root of the archive. All other files should be contained in a subdirectory called content.
- Within the content directory, interactive creators may use whatever directory structure they choose, as long the guidelines outlined below are followed:
- Do not include spaces or special characters in file or directory names. No spaces or special characters are allowed in file or directory names. The only special characters that are permitted are: dash ( - ), underscore (_), and period (.). So this-file_name.txt is valid, but this file~name.txt is not valid.
- All linkage in any interactive should be self-contained and relative to the pathing within the zip archives. For example, the index.html file may embed the object content/swf/main.swf as a valid path and file. However, /content/swf/main.swf will not be a valid path or file on the production system.
All interactives will be loaded via the index.html file in the root directory. This file should bootstrap the interactive to run for the user.
The structure of the content directory may take on a much wider variety of appearances. Figure 1 demonstrates a sample content directory.
It is imperative to realize that the interactives will be experienced through many different platforms and devices. In addition to designing the interactive for the appropriate audience, it is helpful to keep in mind some tips to make the interactive accessible for a variety of platforms and interfaces.
|Variable display resolutions||The interactives may be viewed on a wide variety of displays with varying resolutions so, where possible, use vector graphics. Vector graphics are especially friendly for developers when using Flash, although features such as SVG and the canvas tag enable HTML-based interactives to leverage scalable graphics. It is recommended that wherever possible, HTML-based interactives utilize a fluid layout in order to make the best use of available display resolution.|
|Provide user -friendly interface||Although mouse pointers and other interface devices provide a high level of accuracy, it is recommended that interactive developers try not to position linked objects too closely together. Give some room to linked elements of your interactive, and allow hot zones to be as large as possible. This will make the interactive more accessible to differently abled users, will ease interaction with the interactive on touch-based devices, and will expand the audience to a wider age range (younger children tend not to be as precise with the mouse as adults and older children).|
|HTML links||When featuring HTML links as assets, provide the URL that takes the user closest to the media. PBS LearningMedia intentionally tries to avoid cataloging entire websites since we aim to feature discrete resources, so please avoid URLs to home pages, especially if the websites are large.|
*.mov files are acceptable, however, .mp4 is the preferred format.
|Total Stream BitRate||5 Mbps|
|Frame Rate||30 fps|
|Video Stream BitRate||4808 Kbps|
|Video Stream BitRate Mode||VBR|
FCC Online Captioning Regulations
Full-length video programming shown with closed captions on TV must now have captions when distributed online. Chapterized content is included within this requirement. Captions of online video programming must be at least the same quality as the captions shown on TV. The FCC requires the copyright holder of the content to notify the distributor as to whether captions are needed for a particular program and to provide the digital captioning file if needed.
Full text of the online closed captioning regulations can be found here: FCC regulations