TSA OLC Content Developer Integration Guide v 4 0.pdf

Transportation Security Administration

Online Learning Center

Content Developer Integration Guide Version 4.0

01/01/2008

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

Table of Contents

1.0 INTRODUCTION

1.1 Purpose

1.2 Audience

2.0 ENVIRONMENTAL CONSIDERATIONS

2.1 Server Platform

2.2 Network Bandwidth

2.3 Network Security

2.4 Cross-Domain Scripting Issues

3.0 ENVIRONMENTS

3.1 Production and Test Platform Environment

3.2 Integrated Test Environment (ITE)

3.3 ‘Sandbox’ Test Environment

3.4 OLC Plateau Vendor Environment

3.5 End-User Environment

4.0 APPLICATIONS

4.1 Plateau Learning Management System

4.2 Content Management System

5.0 OTHER SYSTEM AND APPLICATION CONSIDERATIONS

6.0 COURSEWARE EXPECTATIONS

6.1 Performance

6.2 Features

6.3 Testing and Evaluation

6.4 Deliverables

7.0 SECTION 508 COMPLIANCE

7.1 Evaluating Courseware for Accessibility

7.2 Tools for Assessment and Correction of Accessibility

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

APPENDIX A: LIST OF ACRONYMS AND DEFINITIONS

APPENDIX B: HOST SERVER SPECIFICATIONS

1.0 Production and Training Platform

2.0 Integrated Test Environment (ITE)

3.0 “Sandbox” Test Environment

APPENDIX C: END-USER PLATFORM SPECIFICATIONS

1.0 Hardware

2.0 Software

APPENDIX D: SCORM V1.2 CONFORMANCE

1.0 Data Elements

2.0 Methods

3.0 Manifest

4.0 Meta-Data

5.0 Tools Recommended for the Creation of SCORM Content

6.0 Tools Required for the Testing of SCORM Content

APPENDIX E: ADDITIONAL INFORMATION FROM THE PLATEAU CONTENT

INTEGRATION GUIDE ON SCORM

1.0 API Communications Overview

2.0 SCORM Import

APPENDIX F: TSA OLC SUPPORTED AICC DETAILS

1.0 AICC

2.0 Using AICC [Core_Lesson]

3.0 AICC [Objectives_Status] Group

4.0 Using AICC [Core_Vendor]

APPENDIX G: SECTION 508 PROVISIONS

APPENDIX H: QUICK REFERENCE DEVELOPER CHECKLIST

1.0 Environmental Considerations

2.0 SCORM Version 1.2 Conformance

3.0 Courseware Expectations

4.0 Section 508 Compliance

APPENDIX I: REFERENCE WEBSITES

1.0 SCORM v1.2 and Cross-Domain Scripting

2.0 Section 508

3.0 Plateau LMS

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 1

1.0 Introduction

1.1 Purpose

The Transportation Security Administration (TSA) Online Learning Center (OLC) Content Developer Integration Guide contains the technical specifications, application standards and requirements for content developers. Based on industry standards and best practices this information provides a reference for designers and developers in the creation of content for the TSA OLC. This document is not a substitute to any appropriate documentation regarding the specific technologies referenced. Definitions to acronyms and terms used in this document are in Appendix A. A ‘Quick Reference’ Developer Checklist is available in Appendix H.

Content developers should also note that the TSA Information Technology (IT) environment is constantly evolving, as are industry standard technologies and best practices. The TSA’s Online Learning Center team is the point of contact for questions regarding the compatibility of content or practices with the TSA OLC and IT infrastructure.

1.2 Audience

It is assumed that content developers have knowledge of and/or experience with:

o Multiple delivery environments including UNIX web servers and CD- ROM/DVD-ROMs o Industry standard web technologies including HTML, DHTML, XML, CSS, Flash and JavaScript o Information architecture and file management best practices including directory structures and the use of file naming conventions o Techniques for creating accessible content meeting the requirements for Section 508 compliancy o Requirements for creating Shareable Content Object Reference Model (SCORM) v1.2 conformant content o Learning Management System (LMS) and Learning Content Management System (LCMS) integration.

o Standard testing procedures

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 2

2.0 Environmental Considerations

Content developers must consider how content will be delivered, managed, and potentially reused or repurposed. All content designed and developed for distribution within the TSA must allow for a variety of environmental conditions without negatively impacting the user’s viewing experience. Delivery conditions include the TSA OLC Intranet connection, the TSA OLC Extranet/Internet connection, TSA streaming media servers or physical digital media such as CD-ROM or DVD-ROM. Some of the factors to consider when assessing the delivery environment include:

2.1 Server Platform

All TSA OLC servers used in testing and production are UNIX based servers and content will be developed with the UNIX platform in mind. UNIX is a case-sensitive platform. All directories, files and documents submitted for inclusion in the OLC must conform to these standards and conventions.

2.2 Network Bandwidth

When delivering courses across a network, identify the expected bandwidth and how it will affect any multimedia elements contained in the course. As a general best practice, it is recommended that all content be developed assuming delivery across a low bandwidth 56kbps connection. This will allow the same content to be delivered both to users with higher bandwidth connections, and to those without network connections via a CD-ROM based delivery.

2.3 Network Security

The threat of virus or malware infection to a user’s PC is a serious concern. All content required in a course must be included in the developed content package to limit this possibility. No external links will be included in content on the TSA OLC.

Documents or other information linked in the course must be located in the content package.

Content submitted to the TSA OLC will not contain links, keyboard shortcuts or any other backdoor access. Links used during development must be removed prior to delivery. Discovery of this type of access by the TSA OLC team will result in immediate removal from the TSA OLC application and return of the content to the developer or originating organization.

2.4 Cross-Domain Scripting Issues

SCORM v1.2 restricts the use of course content located within a domain different from the LMS. A domain is a web URL, not an IP address. For example, “www.abc.com” is not the same as “www.xyz.com”. The source of this restriction is the JavaScript used to implement and support SCORM functionality. Security concerns also do not permit cross domain content. It is necessary to fully understand this issue if the courseware is intended to be delivered or distributed across multiple domains. The document “Cross-Domain Scripting Issue, Version 1.0” from the ADL contains a complete description of this issue and possible solutions. This is not currently an issue for the TSA IT infrastructure as both the content and application reside within the same web domain, but the platform is susceptible to change.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 3

3.0 Environments

3.1 Production and Test Platform Environment

There are two instances of the TSA OLC application in the production environment.

One is the live production instance and the other is a training instance available for limited vendor testing or more extensive field-testing by the TSA. The production host facility is a secure facility in which changes to software, hardware, and configuration, etc. can take many weeks. Appendix B contains the specifications for the Production and Test Platform Environment server.

3.2 Integrated Test Environment (ITE)

The ITE is a replication of the TSA OLC production environment. All application regression/integration testing takes place in ITE. This environment is located at Unisys in Reston, VA. This environment is accessible only by Unisys personnel.

Appendix B contains the specifications for the ITE.

3.3 ‘Sandbox’ Test Environment The ‘sandbox’ environment is accessible to vendors for testing, only with direct involvement by TSA representatives. A TSA OLC representative will receive the content for upload into the ‘sandbox’ environment via the content and storage management application. All ‘sandbox’ testing is performed either onsite at Unisys in Reston, VA, or with a TSA OLC representative at TSA Headquarters The ‘sandbox’ is behind the Unisys firewall. Due to these restrictions, a vendor requiring ‘sandbox’ testing must coordinate a visit for this purpose in advance. Appendix B contains the specifications for the TSA OLC ‘sandbox.

3.4 OLC Plateau Vendor Environment

The Content Compatibility Testing Program provided by the OLC application vendor Plateau Systems, is intended for content vendors who wish to test their content prior to delivering to a Plateau customer. All vendors that are shown to work with Plateau are added to the Plateau web site, and their content is used, where appropriate, in their sales demos. A request for additional information is available at http://content.plateausystems.com/ContentIntegration/content_compat_info.html. All TSA Vendors will be permitted accounts.

3.5 End-User Environment

TSA OLC End-Users, with the exception of those accessing the OLC via the extranet, use standardized hardware and software. Specifications are located in Appendix C.

TSA PC systems are “locked down” and end-users do not have access to certain administrative configuration rights or locations on the user’s hard drive. Known issues include but are not limited to:

o Users cannot write to the C:\Program Files directory o Users cannot write to and/or do not have access to the %systemroot%\Temp directory o Users cannot access the Downloaded Program Files directory o Users cannot clear Internet Explorer cookies and/or temporary internet files

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 4 o Users cannot modify Internet Options including those associated with ActiveX objects or Java Virtual Machine settings

This “locked down” environment requires courseware developers not to include any custom programs that require installation on a user’s computer as the user lacks the necessary administrative rights to complete this installation. The end user cannot successfully utilize the features or functionality of executable files or self-extracting files. They do not have the necessary administrative rights on the computer.

Contact a TSA OLC team member on any questions regarding user rights and/or permissions prior to development. Testing of the content prior to content completion and delivery can occur.

Another common setting that end-users do not have control over is the position and functionality of the Windows Taskbar. The taskbar, by default, is locked and set so that it does not auto-hide and it remains on top of other windows.

The maximum resolution for courseware content is 775 pixels wide by 525 pixels high which should allow the entire content interface to be visible on screen under these conditions. Contractors must provide a sample of any new Graphical User Interfaces (GUIs) to be used prior to development so that it may be tested for proper display.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 5

4.0 Applications

All content designed and developed for distribution on the TSA OLC must fully integrate with the applications TSA uses for web-enabled training. Industry standards and best practices will allow most content to integrate successfully; however, some additional specifications must be taken into consideration.

4.1 Plateau Learning Management System

The TSA OLC incorporates an implementation of the Plateau Learning Management System (LMS). The LMS is based on a J2EE compliant architecture, supports the SCORM v1.2 standards and is AICC certified. Tracking support in the LMS includes SCORM level 1; AICC level 2 and Plateau customized tracking features and functionality. Additional application specifications including the SCORM v1.2 Conformance are located in Appendix D.

4.2 Content Management System

The TSA OLC team currently uses Documentum as the content and storage management application to upload content to the TSA production and test environments. Both production instances of the TSA OLC operate off the same Documentum docbase. To make this process more efficient, the standard routine for uploading files provided by a content vendor includes creating one zip file of all supplied files and uploading this zip file. Documentum then automates the unzipping of the files once uploaded to the host environment. This process does have its limitations however, most notably that the TSA OLC team is only able to upload compressed files smaller than 30MB in size. It is possible to upload content larger than 30MB, but intervention by Unisys (who maintains the TSA’s infrastructure) is required under such circumstances. This process may be accomplished within half a day; however, it may take longer depending on competing priorities. As a result, all content will be delivered in such a way that when compressed (zipped), the file does not exceed 20MB in size. The TSA OLC team may reject entirely any files larger than 400MB compressed.

The TSA OLC team is in the process of replacing the Documentum system but as of the release of this document, no final decision has been made. This document will be updated when the selection has been finalized.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 6

5.0 Other System and Application Considerations

The TSA OLC system environments and applications are part of a continuing evolution of improvement in addition to adherence to industry standards and best practices. The TSA OLC team will make every effort to keep the TSA Program and Project managers aware of any changes that may affect content functionality with the TSA OLC systems and applications. New versions of the TSA OLC Content Integration Guide will be available once they are updated.

Any changes outside of those involved in the normal enabling of content, including changes in architecture, operating system, hardware, software, players, etc, must be made by Unisys, who act as the single point of contact for all TSA computer and network related issues. Unisys must go through a review, testing, approval, and implementation process prior to any changes. The time involved in this process may be a prohibitive factor in the introduction of new technologies into the TSA OLC.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 7

6.0 Courseware Expectations

6.1 Performance

The ability of the TSA OLC audience to easily access and utilize the courseware content is of utmost importance. Navigating the content (the actual interface controls for navigation) should be easily understood and include adequate instructions, hints and/or help. The content will contain accessibility features both as mandated by Section 508 and generally accepted in industry best practice. Any other aspect of the courseware that affects the user experience such as utilization of appropriate SCORM features will also be incorporated into the content.

While the intent of the TSA OLC is to deliver web-based training, lack of connectivity in some locations or the inaccessibility of a training room to a user requires that all content be deliverable as Web Based Training (WBT) and Computer Based Training (CBT). Some considerations of the dual purposing of content include limited scripting language support, file size optimization, and file type limitations.

Avoid server-side scripting languages such as .php and .asp in favor of JavaScript, which allows the delivery of the same content on both a CD-ROM/DVD-ROM or over a web environment without any significant changes to the code. Content must not require Internet access to any remote files (such as those residing on a vendor’s host server) for security considerations and external Internet access may not be available in some locations. These files should be included in the course content and the pointers directed to the internal location. Content should load quickly over a range of bandwidths and network speeds including dial-up connections and LANs.

Only include the files necessary for the proper function and delivery of the content.

Remove any test logs, previous versions or the like. Best practices for achieving this include the optimization of file types and sizes using the following techniques:

6.1.1 Standardization of content format

All content developed for inclusion in the TSA OLC must be developed to be SCORM v1.2 conformant.

Prior to delivery to the TSA OLC team, all SCORM v 1.2 content is required to pass conformance testing as referenced in Appendix D. The developer is required to include the printed output results of the tests with the course deliverable.

6.1.2 Web Native content

For standard web-native content, which may include HTML, graphical elements, JavaScript scripting, etc, the total load not including any cached items (such as common graphical elements and shared JavaScript libraries) will not exceed 80KB in size. This will keep load times over a worst-case scenario of a 56k dial-up connection to approximately 10 seconds or less. If either load time or file size cannot be achieved contact the TSA OLC team.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 8

6.1.3 GIFs, JPGs, and PNGs for graphical purposes

Any images used as part of course content will be in the .gif, .jpg, or .png format.

Ideally, the .png format is reserved only for use when the alpha transparency feature of a .png is necessary, as some older web browsers are not capable of displaying this file format. When using any of these file types for graphical purposes, their file size will not exceed 60KB in size and ideally remains smaller than 40KB in size. If the file size cannot be achieved, contact the TSA OLC team.

6.1.4 SWFs for content/animation/interactive graphics

A benefit to using Flash for courseware content includes the ability to break down an animation or interaction into multiple files that load individually to a user’s computer. This speeds the initial appearance of the content and allows a developer to manipulate the efficiency of the animation’s loading by dictating which externally loaded .swf files loads and when. When using the .swf file format for graphical animation purposes, each individual file will be a maximum of 70KB to 100KB in size. If the file size cannot be achieved, contact the TSA OLC team.

6.1.5 SWFs for audio/video

Multimedia content including audio and video will be optimized for delivery over low bandwidth connections. Macromedia Flash is the format for multimedia type content delivered over the TSA IT infrastructure. A benefit to using Flash is the ability to break down content into multiple files that load individually to a user’s computer. No single .swf used for audio/video multimedia file will be larger than 25MB in size, and all .swf files larger than 40MB will be rejected all together. If the file size cannot be achieved, contact the TSA OLC team.

6.1.6 Other graphical/audio/video formats

Bandwidth intensive formats including .avi, .mpeg, or other audio/video formats that may significantly negatively impact the performance of the TSA network are not permitted for use in courseware content. If a new technique or format outside of those required by the TSA OLC is desired, the developer should deliver content to act as a “preliminary technical test” for compatibility testing with the TSA infrastructure prior to the start of development work.

Please Note** Requests for deviation from these recommendations and requirements will be reviewed on a case by case basis. The content in question will be delivered to the TSA OLC team for adequate testing early enough in the development process so as not to create any delay to delivery commitments.

6.2 Features

Courseware content developed for delivery via the TSA OLC will utilize the inherent functionality provided by the TSA OLC’s implementation of the Plateau LMS. This functionality can be easily implemented in courses by taking advantage of the features provided by SCORM V1.2. Additional information on Plateau’s integration of the SCORM v1.2 features are provided in Appendix E. AICC implementation is provided in Appendix F as an additional reference.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 9

6.2.1 Course completion certificates

Courseware is required to utilize the certificate functionality built into Plateau.

The alternative for CD-ROM/DVD-ROM based course formats can include embedded written tests and/or printable certificates.

6.2.2 Course content tracking

All content designed for delivery via the OLC will incorporate the tracking of a user’s status with regards to lesson completion. The SCORM provides the cmi.core.lesson_status data element for this purpose and is the required means of reporting a user’s completion of a content object to the LMS.

Plateau only grants credit for a lesson_status value of “P” or “passed” under SCORM. Refer to the Appendix E for additional information.

6.2.3 Course Bookmarking

TSA also requires that all online courseware content incorporates some level of bookmarking capabilities. Often TSA employees are required to fulfill educational requirements over the course of multiple small lengths of time that may not be sufficient to complete an entire learning object. Bookmarking allows a user’s progress to be stored so that the user may return to a point of learning later. Courses should utilize the cmi.core.lesson_location SCORM Data Element to record bookmarks which will be set either at relevant points in the course content or at consistent intervals within the content. Bookmarks can also give the user the option of returning to the beginning of the course SCO or remaining at the bookmark.

6.2.3.1 Bookmarking at relevant points in the course content:

Bookmarks can be placed at relevant points in the course content allowing a user to re-enter a content object at a sound restarting point, such as a topic introduction screen rather than in the middle of a topic. Over long lapses of time between viewing the content, returning a user to the middle of a topic may be confusing to a user or may not provide the necessary review of important content from screens earlier in a topic. For this reason, this bookmarking practice is favored over bookmarking at intervals.

6.2.3.2 Bookmarking at consistent intervals throughout course content:

In the event that a SCO does not contain a secondary structure (such as topics) or obvious relevant points conducive to bookmarking, bookmarks can also be set at consistent intervals throughout the course content. This can be based on an approximate length of time or the number of screens passed since the last bookmark was set. By bookmarking at consistent intervals such as every 3 to 5 screens, a user’s progress through potentially long content can be stored so that the user may continue where they left off when last visiting the content.

6.2.3.3 Bookmarking at the user’s point of exit:

Bookmarking only the screen that a user exits from is not a sufficient approach to achieve this persistence of progress and will not be used as catastrophic failure (such as loss of communication with the LMS) may prevent the successful storage of this information.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 10

6.2.4 Recording elapsed time

Finally, for the purposes of reporting the effectiveness of the content provided by the OLC, the SCORM cmi.core.session_time data element to record the elapsed time during which a user has spent in the course material must be utilized.

6.3 Testing and Evaluation

All courseware will be thoroughly tested and reviewed on all available platforms/client configurations. Content in any format other than WBT (including content delivered on CD-ROM, DVD-ROM, VHS, etc.) should also be delivered to the Project or Program Manager for coordination of testing for compatibility with the TSA IT infrastructure. Testing of content in WBT format can be performed on any of the following environments.

6.3.1 Vendor Testing on the Plateau Test Environment

Vendors may be given an account on the content integration website for the purposes of testing and debugging content communication with the LMS. While this is not a formal part of the vendor/TSA testing process, this step is highly recommended and is the preferred means of testing and debugging communications with the Plateau LMS.

NOTE: Plateau will assist with providing vendors access and accounts to the Plateau Test Environment, but will not be responsible for debugging vendor content. This is not a secure website; therefore no SSI content will be hosted or transferred to Plateau personnel. Additionally the Plateau Test Environment is configured differently than the TSA environment so additional testing in one of the environments listed below will be required.

The point of contact for Plateau is Ravi Chivukula (ravi.chivukula@plateau.com).

6.3.2 Vendor Testing on the Unisys ‘Sandbox’ Environment

The ‘Sandbox’ environment mimics the production environment. The TSA OLC team will receive the content for testing and upload it in the training instance.

Due to IT security policy restrictions, testing can only be performed at Unisys in Reston, VA, or the TSA OLC Headquarters Lab. Either Unisys or the OLC team will grant the vendor access to either site as requested and/or required.

6.3.3 Vendor Testing on the Production Environment

In some instances, TSA may arrange for a vendor to view their content in the TSA OLC via a temporary account. This is not a preferred method and requests will be handled on a case-by-case basis.

6.4 Deliverables

The TSA OLC team will receive the WBT/CBT courseware via CD-ROM or DVD- ROM with all SSI content labeled as required from the Program/Project Managers.

The TSA Program/Project Manager will also verify the labeling of SSI content. The TSA Program/Project Manager will determine any other security requirements, such as an access password, after consultation with the TSA OLC team.

Online content should also be available via offline CBT for those sites with limited or no online access. This will be coordinated with the Program/Project Manager.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 11

External vendors in coordination with the Program/Project Manager and the TSA OLC team may deliver WBT/CBT courseware via a vendor hosted FTP site for purposes of quick turn-around, although a CD-ROM or DVD-ROM is eventually required of all finalized content. The content should be in a SCORM v1.2 conformant zip package complete with a SCORM Manifest. The SCORM Manifest must be no more than 1MB. Meta data can be moved to another file if size is an issue.

The content delivered for placement online must include only the required files for the display of the content. Files such as digital certificates, autorun.inf files, setup.exe files, installers, Photoshop and Flash graphics source files, or any other files not required for online delivery of the content must not be included in order to prevent the unnecessary migration of these files to the servers via the content and storage management application.

Files must not be Read-Only, but rather should allow for Full Control by the TSA OLC team for successful uploading via the content and storage management application.

NOTE Do not save full paths when compressing files using compression programs such as WinZip as these paths will not work when these zip files are extracted to the OLC host servers by the content and storage management application.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 12

7.0 Section 508 Compliance

In 1998, Congress amended Section 508 of the Rehabilitation Act to require Federal agencies to make their electronic and information technology accessible to people with disabilities. In general, all electronic media developed by or for the US government is required to adhere to Section 508 guidelines. However, there are certain areas where an exemption from Section 508 compliance is allowed. According to the memo titled “Guidance for Implementation of Congressionally Mandated Requirements Concerning Access to Federal Information Technology by Members of the Public and Federal Employees with Disabilities (Section 508 of the Rehabilitation Act)”, dated March 6, 2001:

“Exemption from Section 508 compliance exists for several areas. This includes EIT used for telecommunications or information systems, the function, operation, or use of which involves intelligence activities, cryptologic activities related to national security, command and control of military forces, equipment that is an integral part of a weapon or weapons system, and systems which are critical to the direct fulfillment of military or intelligence missions. However, it is possible that some classified websites may still require compliance for the benefit of employees with disabilities. Also exempt is the installed base of EIT prior to 21 June 2001, i.e., Section 508 is not retroactive, only forward looking.”

Due to the nature of the SSI content developed for the TSA OLC, some content may be exempt from Section 508 compliance requirements. This determination is not to be taken lightly or made arbitrarily. Consult with your TSA Project Manager to determine whether content created must adhere to Section 508 guidelines.

Section 508 Provisions under the “Web-based Intranet and Internet Information and Applications (1194.22)” section of the “Section 508 Standards for Electronic and Information Technology” is located in Appendix G. A brief interpretation of each item is provided followed by suggested best practices for implementing the provision. Practical recommendations are also included for providing alternative access to web-based and multimedia content as applicable.

7.1 Evaluating Courseware for Accessibility

The following sections outline a process for evaluating content for conformance to Section 508 accessibility provisions.

7.1.1 Evaluation During Development

Developers should use the best practices recommendations outlined in Section

2.1 Section 508 Provisions to ensure that programmed content is accessible.

Periodically during development, developers should test various pages containing different types of content using tools. As of this writing, JAWS version

7.0 screen reading software is used to test the content. Identifying accessibility issues early reduces and avoids time spent later to correct content that users with disabilities or alternate browser software cannot access.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 13

7.1.2 Evaluation After Development

Once content development is complete, a preliminary conformance evaluation should be conducted using semi-automatic and manual checking methods. The following five-step process is excerpted from the World Wide Web Consortium Web Accessibility Initiative document, “Evaluating Web Sites for Accessibility.”1

Select a representative sampling of different kinds of pages from the Web content to be reviewed; it must include all pages on which people are more likely to enter your content.

Use a graphical user interface (GUI) browser (such as Internet Explorer, Netscape Navigator, or Opera) and examine the selection of pages to be assessed. Some of these manual checks can be performed by changing settings or preferences in the browser, some may require changes to operating system settings, and some may require additional software.

Turn off images, and check whether appropriate alternative text is available.

Turn off the sound, and make sure audio content is still available through text equivalents.

Use browser controls to vary font-size: verify that the font size changes on the screen accordingly; and that the page is still usable at larger font sizes.

Test with different screen resolution, and/or by resizing the application window to less than maximum, to verify that horizontal scrolling is not required (caution: test with different browsers, or examine code for absolute sizing, to ensure that it is a content problem not a browser problem)

Change the display color to gray scale (or print out page in gray scale or black and white) and observe whether the color contrast is adequate.

Without using the mouse tab through the links and form controls on a page, making sure that you can access all links and form controls, and that the links clearly indicate what they lead to. When using a screen reader such as JAWS 7.0, navigate through the course using the keyboard tab, arrow, and enter keys.

Use a voice browser (such as JAWS) or a text browser (such as Lynx) and examine the Web site while answering these questions:

Is equivalent information available through the voice or text browser as is available through the GUI browser?

Is the information presented in a meaningful order if read serially?

Use two general accessibility evaluation tools and note any problems indicated by the tools.

1 Copyright © 2001-2002 W3C (MIT, INRIA, Keio), All Rights Reserved.

http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 14

Summarize results

Summarize the types of problems encountered

Indicate the method by which problems were identified

Recommend follow-up steps and ways to address any identified problems.

7.1.3 Final Verification

Once all identified accessibility problems have been addressed and corrected, the web content is ready to be tested and verified before being published to a live production environment such as the TSA OLC.

7.2 Tools for Assessment and Correction of Accessibility

The following section of this document provides information about some of the available tools and processes more commonly used among web developers for evaluating and modifying web-based content to meet accessibility requirements.

o JAWS® for Windows

JAWS version 7.0 is the most commonly used tool for evaluating accessibility for Department of Homeland Security courseware and websites. With its internal software speech synthesizer and the computer’s sound card, information from the screen is read aloud, providing technology to access a wide variety of information, education and job related applications. JAWS also outputs to refreshable Braille displays, providing unmatched Braille support of any screen reader on the market. A training tutorial is included.

o ACCVerify

ACCVerify is used to validate that courseware contains appropriate HTML tags for accessibility. The tool is highly customizable to offer the developer the option of Section 508 as well as W3C WCAG compliance. The results of an ACCVerify check is a printable report that can be shared with clients and compliance officers.

o Macromedia Dreamweaver MX

Dreamweaver MX includes an accessibility reports feature to check that you have implemented the guidelines in your site. You can run an accessibility report on a current document, selected files, a folder, or an entire site.

o Bobby

Bobby is a comprehensive web accessibility software tool designed to help expose and repair barriers to accessibility and encourage compliance with existing accessibility guidelines. Bobby tests for compliance with government standards, including the U.S. Government's Section 508. It offers prioritized suggestions based on the Web Content Accessibility Guidelines provided by the World Wide Web Consortium's (W3C) Web Access Initiative. Bobby allows developers to test web pages and generate summary reports highlighting critical accessibility issues before posting content to live servers.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 15 o Lift for Dreamweaver

Lift for Dreamweaver is an extension for the Macromedia Dreamweaver authoring tool. Lift allows customization of accessibility tests (WCAG Priority 1, US government section 508), and provides continuously updated test results during editing as well as a wizard-based repair tool that can be run in a context-sensitive mode while editing. It generates reports in HTML format or as an XML file that can be used for further processing. It incorporates heuristics for distinguishing different types of tables and images to provide appropriate suggestions for repair. LIFT is now fully integrated within Dreamweaver MX.

o AccMonitor

With AccMonitor, you can monitor the status of an entire Web site or a subdirectory of the site. Using the AccMonitor console, you can include or exclude directories or file types. You can send “email alerts” to any number of recipients. And when you monitor Web files, you can use Accessibility (Section 508 standards or W3C guidelines) report modes for the accessibility rules you choose, Search ability Rules, Privacy Rules, or any Test Suite that you develop or is shipped with AccMonitor.

o Site Valet

Site Valet is a comprehensive Quality Assurance product for Web and Intranet sites. An online toolkit is complemented by a site maintenance program, both of which are available to the public at the website. Site Valet can be extensively customized for corporate users. Accessibility Valet is a core Site Valet tool, designed to help ensure accessibility by analyzing markup for conformance to web accessibility guidelines: specifically the WCAG and Section 508.

o Window-Eyes

Window-Eyes is a leading software application for the blind and visually impaired, which converts components of the Windows operating system into to synthesized speech allowing for complete and total access to Windows based computer systems. Window-Eyes integration into Windows is seamless, providing you with instant access to the operating system without having to learn a complicated set of keystrokes.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 16

Appendix A: List of Acronyms and Definitions

BACK

ADL – Advanced Distributed Learning Initiative:

The ADL Initiative was formed as a developer and implementer of learning technologies across the Department of Defense (DoD) of the United States of America. It was created through the sponsorship of the Office of the Under Secretary of Defense for Personnel and Readiness (OUSD P&R) to harness the power of information technologies to modernize structured learning.

API – Application Program Interface:

A source code interface that an operating system or library provides to support requests for services to be made of it by computer programs.

CBT – Computer Based Training:

A type of education in which the student learns by executing special training programs on a computer.

COTS – Commercial Off the Shelf:

A term for software or hardware, generally technology or computer products, that are ready-made and available for sale, lease, or license to the public. They are often used as alternatives to in-house developments or one-off government-funded developments.

General Training

Any training that does not involve technical transportation security content.

GUI – Graphical User Interface:

A type of user interface which allows people to interact with a computer and computer-controlled devices.

IT or ITD – Information Technology Division:

The Information Technology Division delivers IT products and services that support the mission and business IT requirements throughout TSA.

LCMS – Learning Content Management System:

An LCMS manages the process of creating, editing, storing and delivering e-learning content.

LMS – Learning Management System:

An LMS is a high-level, strategic solution for planning, delivering, and managing most learning events within an organization, including online, virtual classroom, and instructor-led courses.

OLC Team – Online Learning Center Team:

Members of the Human Capital Information Systems group that is responsible for the operation and maintenance of the TSA OLC.

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 17

OTT – Operational and Technical Training:

Develops and delivers technical training that helps enable the TSA workforce, and others involved in transportation security, to perform their duties in protecting the nation's transportation systems.

RTE – Run Time Environment:

A runtime environment is a virtual machine state which provides software services for processes or programs while a computer is running.

SCORM – Shareable Content Object Reference Model:

SCORM is a collection of standards and specifications for web-based e-learning.

SCO – Shareable Content Object:

A SCO is the designation for the content in a web-based courseware SCORM package.

TSA – Transportation Security Administration:

The agency established in 2001 to safeguard United States transportation systems and insure safe air travel

TSA OLC – TSA Online Learning Center:

A web-based LMS provided by Plateau Systems used by TSA.

WBT – Web Based Training:

A generic term for training and/or instruction delivered over the Internet or an intranet using a Web browser.

BACK

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 18

Appendix B: Host Server Specifications

BACK

1.0 Production and Training Platform

1.1 Application Server (8)

Sun Fire V880 Server

Solaris 8

Oracle DB 10gAS version 10.1.2

1.2 Web Server

Sun Fire V480 Server

Solaris 8

Apache HTTP Server version 1.3.22

1.3 Database Server

Sun Fire V880

Solaris 8

Oracle DB 10g version 10.2.0.2

1.4 OLC Crystal Reports Server

UNISYS ES3020

Windows Server 2000 SP4

Crystal Reports Enterprise Version 10

2.0 Integrated Test Environment (ITE)

2.1 Application Server (2)

Sun Fire V880 Server

Solaris 8

Oracle DB 10gAS version 10.1.2

2.2 Web Server

Sun Fire V480 Server

Solaris 8

Apache HTTP Server version 1.3.22

2.3 Database Server

Sun Fire V880

Solaris 8

Oracle DB 10g version 10.2.0.2

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 19

2.4 OLC Crystal Reports Server

UNISYS ES3020

Windows Server 2000 SP4

Crystal Reports Enterprise Version 10

3.0 “Sandbox” Test Environment

3.1 Application Server (1)

Sun Fire V880 Server

Solaris 8

Oracle DB 10gAS version 10.1.2

3.2 Web Server

Sun Fire V480 Server

Solaris 8

Apache HTTP Server version 1.3.22

3.3 Database Server

Sun Fire V880

Solaris 8

Oracle DB 10g version 10.2.0.2

3.4 OLC Crystal Reports Server

Sun Fire V880 Server

Solaris 8

Oracle DB 10gAS version 10.1.2

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 20

Appendix C: End-User Platform Specifications

BACK

TSA OLC End-Users, with the exception of those accessing the TSA OLC via the extranet, will be using the following hardware, software, and operating system to access TSA OLC content.

1.0 Hardware

TSA supports one desktop and three laptop personal computer configurations:

1.1 Dell OptiPlex GX620/745Desktop

Windows XP Professional, SP2

Pentium D 945/3.40GHz

NTFS File System

80 GB Hard Drive

1.0GB, Non-ECC, 533MHz DDR2

1.2 Dell Precision Workstation 490

Windows XP Professional, SP2

NTFS File System

1.3 Dell Latitude C610/620/630 Laptop

Windows XP Professional, SP2

Intel Core Duo T2500, 2.00GHz 667Mhz, 2M L2 Cache, Dual Core

NTFS File System

80 GB Hard Drive

1.0GB, DDR2-667 SDRAM

1.4 Dell Latitude D410/420/430 Laptop

Windows XP Professional, SP2

Intel CoreSolo U1300, 1.06GHz ULV 533Mhz, 2M L2 Cache

NTFS File System

60 GB Hard Drive

1.0GB, DDR2- 533 SDRAM

1.5 Dell Latitude D820 Laptop

Windows XP Professional, SP2

Intel Core Duo T2600, 2.16GHz, 667Mhz, 2M L2 Cache, Dual Core

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 21

NTFS File System

80 GB Hard Drive

1.0GB, DDR2-667 SDRAM

2.0 Software

TSA computers conform to an ‘Image’ of standard software applications. Additional software is vetted by the ITD to insure the proper integration to the TSA Image. The TSA Image software is listed below:

Microsoft Windows XP SP2

Microsoft Internet Explorer v 6.0.2900.2180

Microsoft Office Professional 2007 v 12.0 or

Microsoft Office Professional 2003 v 11.0.7969.0, SP2

Symantec Client Security v 104.0.8.3

Symantec Client Security Live Update v 3.0.0.160

Symantec AntiVirus v 10.1.4.4010

Symantec AntiVirus Virus Definition Update v 2007.9.19

Symantec Firewall v 6.6.00.6501

Symantec Client Firewall Rules v 6.6.00.6501

Altiris Software Delivery Solution Agent v 6.1

Altiris Application Metering Agent v 6.1

Altiris Inventory Rule Agent v 6.2

Altiris NS Console ActiveX v 1.0

Altiris State Management Agent v 6.1

Altiris Task Synchronization Agent v 6.2

ACS Certificates updated patches v 3.3

Adobe Acrobat Reader v 7.08 to be updated to 8.0.0

Authorware Player 2004.0.0.73 v 1.0.0 (To be added mid 2008)

Compatibility Pack for Office 2007 v 12.0.4518.1014

DWF Viewer v 7.2.0

Easy CD Creator v 2.4.32b

FirePass VPN Web Components

Flash Player v 9.0.28.0

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 22

J2SE Runtime Environment 5.0 Update 5 v 1.5.0.50

J2SE Runtime Environment 5.0 Update 6 v 1.5.0.60

J2SE Runtime Environment 5.0 Update 8 v 1.5.0.80

Java 2 Runtime Environment Standard Edition v 1.3.102

Jet SP8 v 4.0.8015.0

MapGuide Viewer Version v 6.5

Metadata Removal Add-In v 12.0

Microsoft File Transfer Manager v 5.0.29

Microsoft .Net Framework v 2.0 w/Hot Fixes

Microsoft Compression Client Pack v 1.0

Microsoft Java Virtual Machine v 5.0.3810

Microsoft MediaPlayer v 10

Microsoft Office 2003 Web Components v 11.2

Microsoft Office Live Meeting 2005 v 7.9.2205.0

Microsoft Office OneNote 2003 v 11.0.7969.0

Microsoft Office OneNote 2007 v 12.0.4518.1014

Microsoft Office PowerPoint Viewer 2007 v 12.0.4518.1014

Microsoft Office Tools v 11.6550.8107 SP2

Microsoft Office Visio Viewer 2003 v 11.0

Microsoft Office Visio Viewer 2007 v 11.0

Microsoft Reader v 2.1.1.3143

Mobile Guardian Gatekeeper v 5.1.5.3015

MSXML 6.0 Parser v 6.10

NetSwitch v 2.5

Office Communicator 2005 v 1.0.559.183

Office Visio IFilter 2003 v 11.0.3401.5614

Office Word 2003 Redaction AddIn v 1.2.0

Oracle JInitiator v 1.1.8.16

Oracle JInitiator v 1.1.8.19

Project Web Access Components 2003 v 11.2.2006.1117

Shockwave v 10.1.4.020

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 23

Steelray Project Viewer v 3.1.6.0

Sun JRE v 1.3.102

Sun JRE v 1.5.0.50

Sun JRE v 1.5.0.60

Sun JRE v 1.5.0.80

Webroot SpySweeper Client (to be removed)

Windows Media Format Runtime v 11

Windows Messenger v 8.1.0178

WinDVD v 4.0.0

WinZip v 11.1

XO Communications Access Finder v 3.3.1.1

Windows XP Hot Fixes various versions

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 24

Appendix D: SCORM V1.2 Conformance

BACK

The Shareable Content Object Reference Model (SCORM) has been developed as part of the Advanced Distributed Learning (ADL) Initiative and is designed to be a standard to promote the reusability and interoperability of learning content. Initially designed for use in the Department of Defense, SCORM has been adopted by the majority of LMS vendors as a supported standard, which has influenced its adoption among most other government agencies as well. The TSA OLC is no exception to this trend as the TSA OLC’s instance of the Plateau LMS supports SCORM v1.2 conformant content. As a result, all content developed for inclusion in the TSA OLC must be developed to be SCORM v1.2 conformant.

While documentation on SCORM and its implementation is readily available, the guidance provided in the following sections is designed to be used as a brief reference of standards and best practices in the use of the SCORM in content developed for the

TSA OLC.

1.0 Data Elements

The SCORM provides 14 mandatory data elements that must be supported by all SCORM v1.2 conformant LMSs. While there are also a number of optional data elements that may be supported by an LMS, TSA requires that only the following mandatory elements be utilized to ensure interoperability of the developed content among future SCORM 1.2 LMS instances that may or may not support any of the optional elements. The following table provides a brief reference to these mandatory elements and their intended use. Additional information can be found within ADL documentation.

SCORM Mandatory Data Elements cmi.core._children

Read Only

Contains a comma-delimited string of all of the elements in the core category that are supported by the LMS. An empty string is returned if an element is not supported or an element is supported and has no children cmi.core.student_id

Read Only

Contains a unique case-insensitive alphanumeric identifier used by the LMS to identify the learner. The value may be up to 255 alpha-numeric characters in length with no spaces (hyphens and underscores are allowed, periods are not allowed) cmi.core.student_name

Read Only

Contains the students official name as listed on the course roster, usually as a full name in the format: LastName, FirstName MiddleInitial

Transportation Security Administration Online Learning Center Content Developer Integration Guide v 4.0

January 1, 2008 Page 25

SCORM Mandatory Data Elements cmi.core.lesson_location

Read / Write

Intended to act as a location in which a SCO can store a “bookmark” in order to allow a student to return to a point in a SCO…