EPLC DoS Section 508 Compliance Test Plan Template 1 .doc

Section 508 compliance Test Plan

Section 508 Compliance Test Plan

Food and Drug Administration

<PROJECT NAME & RELEASE VERSION #>

OFFICE OF INFORMATION MANAGEMENT (OIM)

SECTION 508 COMPLIANCE

TEST PLAN

Document Version Number: <#.#> Document Version Date: <mm/dd/yyyy> Notes to the Author

[This document is a template of a Section 508 Compliance Test Plan for a project. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project.

· Blue italicized text enclosed in square brackets ([text]) provides instructions to the document author, or describes the intent, assumptions and context for content included in this document.

· Blue italicized text enclosed in angle brackets (<text>) indicates a field that should be replaced with information specific to a particular project.

· Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to a specific project. These are offered only as suggestions to assist in developing project documents; they are not mandatory formats.

When using this template, the following steps are recommended:

1. Replace all text enclosed in angle brackets (e.g., <Project Name>) with the correct field document values. These angle brackets appear in both the body of the document and in headers and footers. To customize fields in Microsoft Word (which display a gray background when selected) select File->Properties->Summary and fill in the appropriate fields within the Summary and Custom tabs.

After clicking OK to close the dialog box, update all fields throughout the document selecting Edit>Select All (or Ctrl-A) and pressing F9. Or you can update each field individually by clicking on it and pressing F9.

These actions must be done separately for any fields contained with the document’s Header and Footer.

2. Modify boilerplate text as appropriate for the specific project.

3. To add any new sections to the document, ensure that the appropriate header and body text styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and Heading 3. Style used for boilerplate text is Body Text.

4. To update the Table of Contents, right-click on it and select “Update field” and choose the option - “Update entire table”.

5. Before submission of the first draft of this document, delete this instruction section “Notes to the Author” and all instructions to the author throughout the entire document.]

VERSION HISTORY

[Provide information on how the development and distribution of the Section 508 Compliance Test Plan Document will be controlled and tracked. Use the table below to provide the version number, the author implementing the version, the date of the version, the name of the person approving the version, the date that particular version was approved, and a brief description of the reason for creating the revised version.] Version Number Implemented

By Revision

Date Approved

By Approval

Date Description of and Reason for Change

APPROVALS

This Section 508 Compliance Test Plan has been presented and approved by:

Business Sponsor

(Name)

Date

Project Officer / Manager / Coordinator

(Name)

Date

Table of Contents iRecord of Changes iiTable of Contents ivTemplate Instructions

11.

PURPOSE AND SCOPE

11.1.

Purpose

11.2.

Background

11.3.

Scope

22.

GLOSSARY

33.

STAKEHOLDERS

34.

RESOURCE REQUIREMENTS

34.1.

Testing Environment

34.2.

Test Roles and Skills

54.3.

Staff Training

55.

Assumptions, constraints, DEPENDENCIES, and Risks

55.1.

Testing Assumptions

65.2.

Testing Constraints

65.3.

Testing Dependencies

65.4.

Testing Risks

76.

Testing PROCESS

76.1.

Methodology

86.1.1.

Concept Phase

86.1.2.

Requirements Analysis Phase

86.1.3.

Design Phase

86.1.4.

Development Phase

96.1.5.

Integration and Test Phase

96.1.6.

Implementation Phase

96.1.7.

Operations and Maintenance Phase

96.2.

Test Milestones

96.3.

Test Data

106.4.

Recording Results

11Table 6.4.0

11Table 6.4.1

12Table 6.4.2

126.5.

Analyzing Results

136.6.

Defect Resolution

137.

Test execution

137.1.

Test Identification

137.2.

Entry, Execution, and Exit Criteria

137.2.1.

Entry Criteria

147.2.2.

Execution Criteria

147.2.3.

Exit Criteria

1APPENDIX A. Section 508 Product Assessment Form

1Section 1194.21 Software Applications and Operating Systems

3Section 1194.22 Web-Based Internet Information and Applications

5Section 1194.23 Telecommunications Products

9Section 1194.24 Video and Multimedia Products

10Section 1194.25 Self-Contained, Closed Products

13Section 1194.26 Desktop and Portable Computers

13Section 1194.31 Functional Performance Criteria

15Section 1194.41 Information, Documentation, and Support

Template Instructions:

The Office of Information Management (OIM), Division of Systems (DS), Testing and Quality Assurance Team requires each system to have a Section 508 Compliance Test Plan that describes the Section 508 Compliance testing approach for all project releases. This effort must be developed by the Project Management team and approved by the PATT.

In support of the Project Management team this template has been completed to identify the Section 508 Compliance testing tasks and activities so that all Section 508 Compliance aspects of the system are adequately tested and can be successfully implemented. Each project must provide minor edits to select sections where text may simply be replaced with appropriate data that are marked in the following manner: <text>. Each project must also provide more significant edits to project element unique sections of the template. Authors must follow the template outline and add/modify the information specific to their project in the applicable area of the template. Test processes in accordance with the Software Testing Policy cannot be removed from the template without approval.

1. PURPOSE AND SCOPE

1.1. Purpose

< This section of the Section 508 Compliance Test Plan outlines what items, functions, and/or aspects of the system are being covered within this test plan. Identify the name of the system and the release or iteration number.>

This document establishes the procedure by the Testing and Quality Assurance Team designated testing resource to determine compliance of electronic and information technology (EIT) with Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. § 794 (d)), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7, 1998.

The objective of the test plan is to provide a test strategy to establish the framework so that the activities most effectively provide:

· Validation that the Section 508 Compliance requirements have been implemented appropriately

· Identification of Section 508 Compliance defects

· Documents the Section 508 Compliance status

1.2. Background

<The project provides in this section of the Section 508 Compliance Test Plan a brief description of the history and other general information about to the system.>

1.3. Scope

< This section of the Section 508 Compliance Test Plan describes the projected boundaries of the planned tests. Provide a brief description of what is going to be tested under this plan as well as what is going to be excluded.>

This section describes the standard Section 508 Compliance testing process for all < Project Name > releases. This test plan applies to all project FDA employees, contractors, and partners developing, procuring, maintaining, or using < Project Name > EIT products or services on behalf of FDA.

Within the FAR 2.101, EIT has the same meaning as "information technology," except EIT also includes any equipment or interconnected system or subsystem of equipment that is used in the creation, conversion, or duplication of data or information. The term EIT, includes, but is not limited to, telecommunication products (such as telephones), information kiosks and transaction machines, worldwide websites, multimedia, and office equipment (such as copiers and fax machines).

According to OMB Circular A-130, “information technology” is equipment or interconnected systems that are used in the automatic acquisitions, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information. The term includes computers, ancillary equipment, software, firmware and similar procedures, services (including support services), and related resources.

To further clarify the FAR definition, EIT includes any product used to acquire, store, manipulate, or transmit information. This includes software applications and operating systems; web-based intranet and internet information and applications such as distance learning; telephones and other telecommunications products; information kiosks and transaction machines; video equipment and multimedia products that may be distributed on videotapes, CDs, DVDs, or the World Wide Web; office products such as photocopiers and fax machines; calculators; and computer hardware.

According to the Access Board, EIT does not include any equipment that contains embedded information technology that is used as an integral part of the product, but the principal function of which is not the acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information. Examples of non-EIT include heating, ventilation, and air conditioning.

The scope of the testing for the project will comply with the testing standards in the Software Testing Policy. These tests will verify Section 508 Compliance functionality and usability defined by the supplementary requirements documented in the project System Requirements Specification.

Testing is conducted during system testing following the completion of regression testing. The test team will execute representative test scripts ensuring testing of all project web pages and their corresponding links throughout the application. The test cases and scripts used for the testing of the Section 508 Compliance must be traceable to section 508 compliance requirements.

Automated testing tools and manual testing techniques will be utilized to test for Section 508 Compliance. Web based features of the application will be tested using the approved FDA 508 test tool. Non-web based features of the application will be tested using the approved FDA manual test procedures.

The success or failure of each test will be documented along with all supporting data needed to repeat the test. Functional Regression Testing will be conducted following any Section 508 Compliance corrective maintenance.

2. GLOSSARY

<The project provides in this section of the Section 508 Compliance Test Plan a list of all terms and abbreviations used in this document. If the list is several pages in length, it may be placed as an appendix. If terms and acronyms are listed in a separate document, reference the document and its location.>

3. STAKEHOLDERS

< The project provides in this section of the Section 508 Compliance Test Plan the names and contact information of the key project stakeholders for the project.>

Project Manager

Project Manager Business

Lead Design

Lead Developer

Project Test Lead

Configuration Manager

Table 1 Main Points of Contacts

4. RESOURCE REQUIREMENTS

<This section of the Section 508 Compliance Test Plan identifies the equipment and personnel resources required to perform the testing identified within the scope of this document.>

4.1. Testing Environment

<This subsection of the Section 508 Compliance Test Plan describes the testing environment needed to adequately test the components identified in this document.> Testing will be performed in stand alone test environments that will closely resemble the Target Production environment (live system). This means that the system will be running in as complete a manner as possible during all testing activities. There will be distinct environments used for testing. The test environments will have primarily the same hardware types, software versions and operating system versions.

4.2. Test Roles and Skills

<This subsection of the Section 508 Compliance Test Plan lists the test roles and skill requirements needed to support testing that are not part of the system being tested. Clear and complete roles and responsibilities are defined, documented, and practiced for all project members (including contractors). This will include all of the personnel that have any interaction with the testing efforts, testing programs/devices and programming aids as well as systems which must operate with the new system to achieve functionality.>

(Experience, Tool Sets, Etc.)

Test Responsibilities

FDA

Project Manager

· Reviews Section 508 Product Assessment

Contractor

Project Manager

· Review status of with Section 508 Compliance test efforts

· Familiarity with EPLC

· Expert with FDA approved Section 508 Compliance test tools

· Create and manage Section 508 Compliance Test Plan

· Establish methodology for conducting testing

· Set testing milestones/schedules and meeting agendas

· Identify and report testing related risks and recommend risk mitigation strategies

· Management and execution of all Section 508 Compliance tests

· Provide Section 508 Product Assessment

· Expert with OIT Test Guidance

· Familiarity with EPLC

· Expert with FDA approved Section 508 Compliance test tools

· Perform process reviews and audits of the project to ensure best quality assurance practices.

· Review and approve test artifacts

· Ensure testing plans and outcomes are acceptable

· Provide connectivity to test tools

· Provide COTS product licensing and tool resolution

Table 2 Test Roles and Skills

4.3. Staff Training

< The project provides in this subsection of the Section 508 Compliance Test Plan the types of training required for the project test team members. The Software Training plan can be referenced where applicable.>

5. Assumptions, constraints, DEPENDENCIES, and Risks

5.1. Testing Assumptions

<The project creates or adds to this subsection of the Section 508 Compliance Test Plan the assumptions that are being made regarding the system being tested.>

The following listed items are standard testing assumptions. Where necessary, a risk will be identified and logged in the Risk Management Strategies and Mitigation table.

· The source code will be tested and provided within the scheduled time outlined in the Project Schedule.

· The project System Requirements Specification and the Design document will be used to create the project Test Cases.

· Discussions with the Subject Matter Experts (SMEs) from the business component will be used to create end to end test cases.

· This Plan does not cover testing of applications that interface with the system.

· All referenced documents have been reviewed and are accurate and base-lined.

· The < Project Name > team will have the knowledge and capability to administer FDA approved tools.

· All software to be tested will be performed and controlled under configuration management (CM).

5.2. Testing Constraints

<The project creates or adds to this subsection of the Section 508 Compliance Test Plan the constraints that affect the testing. This could be availability of equipment, trained staff, crunched project schedule, etc.> The following listed items are standard constraint items identified as having possible impact on the design, development, or implementation of testing. Where necessary, a risk will be identified and logged in Risk Management Strategies and Mitigation table.

· No data flow model or prototype documentation is available for reference.

· Testing will be conducted within the scheduled time outlined in the Project Schedule.

5.3. Testing Dependencies

<The project creates or adds to this subsection of the Section 508 Compliance Test Plan the dependencies that affect the testing. This could be availability of resources, project artifacts, project processes, etc.>

The following listed items are standard dependencies identified as having possible impact on the design, development, or implementation of testing. Where necessary, a risk will be identified and logged in accordance with the project Risk Management Plan.

· Separate production-like testing environments are in place.

· A configuration management process is in place.

· The delivery of the release software is on time.

· All integrated Project Plan deliverables submitted on a timely basis.

· All entrance criteria are met.

5.4. Testing Risks

<The project creates or adds to this subsection of the Section 508 Compliance Test Plan the risks associated with the testing activities. Include a work around or mitigation plan for each of the identified risks in accordance with the project Risk Management Plan.>

OR

Accept increased budget risk by staffing up in order to do sufficient testing at last minute.

OR

Accept delays to development and testing schedules.

OR

Slip the planned test phase entry and exit dates day-for-day until the environment is available.

OR

Adhere to continuation criteria and stop testing if problem becomes too bad, accepting delay of schedule.

OR

Attempt to continue testing on current schedule and budget, accepting a poor quality system release to customers.

OR

Delete some other testing and reallocate resources to the missing testing area. (May not be possible for all situations).

OR

Decide to skip the tests for which sufficient resources were not budgeted and accept the increased quality risks associated with that test coverage gap.

Table 3 Testing Risks

6. Testing PROCESS

6.1. Methodology

<This subsection of the Section 508 Compliance Test Plan describes the general methodology or testing strategy for each type of validation described in this Section 508 Compliance Test Plan. The test strategy must clearly state the type of validation or tests being implemented and the objective of the tests. The test approach must describe how the test will be implemented. This should provide a statement as to what will be tested, the major testing milestones, and how the results will be verified. The statements should provide enough information to the stakeholder to understand what will be tested.> The < Project Name > test team will perform test planning and participate in requirements analysis to ensure the development of testable requirements.

The following describes the methodology and sequence of steps that comprise the procedure for determining compliance with Section 508 of the Rehabilitation Act of 1973, as amended, of a < Project Name > EIT developed product or service. The steps are listed in the life cycle sequence in which they generally occur.

6.1.1. Concept Phase

During the Concept Phase, the Business Owner ensures that all applicable Section 508 technical provisions are documented as product requirements in the System Requirements Document.

6.1.2. Requirements Analysis Phase

During the Requirements Analysis Phase, the Business Owner and the System Developer or System Maintainer review and revalidate all of the technical provisions that were previously documented in the System Requirements Document and make any necessary adjustments before establishing the requirements baseline. The System Developer or System Maintainer includes plans for testing or validating compliance with the applicable technical provisions (Section 508 requirements) as the System Test Plan is drafted and test scenarios and success criteria are identified.

6.1.3. Design Phase

During the Design Phase, the System Developer or System Maintainer completes a Section 508 Product Assessment for the designed/modified EIT product and includes it as an attachment to the System Design Document (SDD). The System Developer or System Maintainer will modify the design as necessary to ensure that the developed EIT product will be Section 508 compliant, or the Project Manager will ensure that the appropriate Section 508 exception is documented and approved. The System Developer or System Maintainer and the Project Manager also ensure that plans for testing or verifying/validating compliance with the applicable technical provisions (Section 508 requirements) are finalized and documented in the System Test Plan and that test cases are created to test the Section 508 requirements.

6.1.4. Development Phase

During the Development Phase, the System Developer or System Maintainer ensures that the developed product is Section 508 compliant (i.e., meets the Section 508 requirements that were documented in the System Requirements Document and the initial Section 508 Product Assessment that was included in the SDD), unless an appropriate Section 508 exception has been documented and approved. The System Developer or System Maintainer and the Project Manager also ensure that the system testing includes one or more test cases that will test each of the Section 508 requirements to verify compliance.

6.1.5. Integration and Test Phase

During the Integration and Test Phase, the PATT Designated Testing Resource tests the EIT product in accordance with the documented System Test Plan and records the results from the testing in a Section 508 Product Assessment. Screen readers and other accessibility tools are available to assist in the testing process. The current FDA Section 508 Compliance tools are InFocus 4.2 and JAWS. When the System Developer or System Maintainer fixes any reported defects in the EIT product, and the PATT Designated Testing Resource retests the EIT product for Section 508 compliance, if necessary.

6.1.6. Implementation Phase

During the Implementation Phase, the System Developer or System Maintainer prepares a final Section 508 Product Assessment for the developed EIT product. If the EIT product is determined to not be Section 508 compliant and an appropriate exception has not been documented and approved, then the Project Manager must prepare a remediation plan for achieving compliance.

6.1.7. Operations and Maintenance Phase

During the Operations & Maintenance Phase, the existing Section 508 Product Assessment for the EIT product that is operating in production must be reviewed and appropriately updated by the manufacturer, vendor, or developer for each new release of the EIT product if it is modified, and the new EIT product retested by the PATT Designated Testing Resource for Section 508 compliance prior to the revised EIT product’s release into the production environment.

6.2. Test Milestones

< This subsection of the Section 508 Compliance Test Plan lists the testing milestones.>

Refer to the project schedule or Work Breakdown Structure (WBS) for detailed test milestone dates, durations, and tasks.

6.3. Test Data

< This subsection of the Section 508 Compliance Test Plan specifies the test data to be used. It describes the source, volume, and frequency of the data. This section also describes the techniques that will be used for manipulating the test data into a form suitable for evaluation.>

The FDA will provide a test environment that consists of data that mirrors the production environment. Test data migration and refresh will be conducted as per the migration and refresh schedule. When production like data is not available the Test team will create “dummy” data for testing purposes.

6.4. Recording Results

< This subsection of the Section 508 Compliance Test Plan describes how the test results will be captured, recorded, stored, and communicated to all necessary parties, for both passed and failed tests. Identify what artifacts will need to be produced as a result of the testing activities.>

The Section 508 Voluntary Product Accessibility Template (VPAT) is a simple, Web-based checklist that allows manufacturers, developers, or vendors to document how their product complies with the various Section 508 Requirements. The VPAT format will be adapted for use in recording the Section 508 Compliance test results.

Utilizing the information provided in table 6.4.0, determine which sections of the Technical Standards (Subpart B - 1194.21 through 1194.26) apply to the <Project Name version number > EIT product. Note that the Functional Performance Criteria (Subpart C – 1194.31) and the Information, Documentation, and Support (Subpart D – 1194.41) sections of the Section 508 Product Assessment must be completed for every EIT product.

1194.31 Functional Performance Criteria

1194.41 Information, Documentation, and Support

1194.31 Functional Performance Criteria

1194.41 Information, Documentation, and Support

1194.22 Web-Based Internet Information and Applications

1194.31 Functional Performance Criteria

1194.41 Information, Documentation, and Support

1194.31 Functional Performance Criteria

1194.41 Information, Documentation, and Support

1194.31 Functional Performance Criteria

1194.41 Information, Documentation, and Support

1194.31 Functional Performance Criteria

1194.41 Information, Documentation, and Support

1194.31 Functional Performance Criteria

1194.41 Information, Documentation, and Support

Table 6.4.0 Based on the test results, determine if the <Project Name version number > EIT product does or does not meet the individual Criteria elements listed in the 1st column of each applicable section of the Section 508 Product Assessment. Utilizing the guidance provided in table 6.4.1, provide the appropriate responses in the Supporting Features column (2nd column) of the Section 508 Product Assessment document for each Criteria element.

Table 6.4.1

Utilizing the guidance provided in table 6.4.2, document in the Remarks & Explanations column (3rd column) for each Criteria listed in the 1st column of the applicable sections of the Section 508 Product Assessment document, exactly how the EIT product does or does not meet the Criteria.

AND

List exactly what product aspects do not meet the Criteria and describe how they fail to support the Criteria.

Table 6.4.2 The Section 508 Product Assessment template can be found in Appendix A. All non-compliance defects should be processed as Problem/Change Reports (PCRs) in accordance with the PCR Process contained in the project Configuration Management Plan.

6.5. Analyzing Results

< This subsection of the Section 508 Compliance Test Plan describes how the test results will be analyzed. Include the pass/fail criteria and the number of times the various tests should be executed to ensure accurate results.>

All test results will be analyzed. Whenever possible, defect reports will include screenshots highlighting the steps taken and the results. The appropriate test artifacts will then be analyzed by the designated person or team. Further defect evaluation may be determined by the project manager or applicable control board. At the completion of testing a Section 508 Product Assessment will be created to present the status of system capabilities and any process deficiencies to provide a means of assessing software progression to production readiness and process improvement.

6.6. Defect Resolution

< This subsection of the Section 508 Compliance Test Plan describes how the defects and bugs identified during the test execution steps will be recorded, reviewed, and resolved. Identify the criteria for defining the severity and priority (urgency) of the defects and bugs as it relates to the project deliverables.>

All defects and change requests are recorded and processed as PCRs in accordance with the PCR Process contained in the project Configuration Management Plan. The time table for defect resolution is determined by the appropriate control board in accordance with the project Configuration Management Plan and appropriate Control Board charter.

7. Test execution

7.1. Test Identification

< This subsection of the Section 508 Compliance Test Plan describes the test items for a given release. Identify the test cases, scripts or scenarios that will be used.>

Unless otherwise stated, the PCRs for < Project Name > identifies the test items; software, hardware, and supporting elements, targeted for the testing each release. These PCRs shall also be identified in the Version Release Package for each release.

7.2. Entry, Execution, and Exit Criteria

<This subsection of the Section 508 Compliance Test Plan describes Entry, Execution and Exit Criteria. The Section 508 Compliance test team must have a clearly defined Entry, Execution and Exit criteria for Section 508 Compliance testing. These criteria allow for an application to generate a formal and clearly defined starting point and ending point of the testing phase. Entry, Execution and Exit criteria for multiple testing environments were provided.>

7.2.1. Entry Criteria

Entry criteria are the events that must occur prior to starting Section 508 Compliance testing. Exceptions maybe made at the direction of the Project Manager and the concurrence of the PATT Test Lead.

Section 508 Compliance Testing Entry Criteria Checklist:

Table 5 Test Environment Entry Criteria

7.2.2. Execution Criteria

The Section 508 Compliance testers will execute the Section 508 Compliance test cases as planned and record the results to the appropriate sections of the Technical Standards (Subpart B - 1194.21 through 1194.26) and the Functional Performance Criteria (Subpart C – 1194.31) and the Information, Documentation, and Support (Subpart D – 1194.41) sections of the Section 508 Product Assessment.

When the review indicates abnormal results are due to test artifact errors, or due to problems with the test environment, the appropriate corrective action should be taken and the testing re-executed. When all tests are completed and reviewed the Section 508 Compliance test execution is complete.

7.2.3. Exit Criteria

Exit criteria are the events that must occur to exit Section 508 Compliance testing. Exceptions maybe made at the direction of the Project Manager and the concurrence of the PATT Test Lead.

Section 508 Compliance Testing Exit Checklist:

Table 7 Test Environment Exit Criteria

APPENDIX A. Section 508 Product Assessment Form

Section 1194.21 Software Applications and Operating Systems

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

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

(c) A well-defined onscreen 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.

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

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

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

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

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

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

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

(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2Hz and lower than 55Hz.

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

Section 1194.22 Web-Based Internet Information and Applications

(a) A text equivalent for every non-text element shall be provided (for example, via “alt,” “longdesc,” or in element content).

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

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example, from context or markup.

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

(e) Redundant text links shall be provided for each active region of a server-side image map.

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

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

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

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

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2Hz and lower than 55Hz.

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

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

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

(n) When electronic forms are designed to be completed online, 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.

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

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

Section 1194.23 Telecommunications Products

(a) Telecommunications products or systems which provide a function allowing voice communication and which do not themselves provide a TTY functionality shall provide a standard non-acoustic connection point for TTYs. Microphones shall be capable of being turned on and off to allow the user to intermix speech with TTY use.

(b) Telecommunications products that include voice communication functionality shall support all commonly used cross-manufacturer non-proprietary standard TTY signal protocols.

(c) Voice mail, auto-attendant, and interactive voice response telecommunications systems shall be usable by TTY users with their TTYs.

(d) Voice mail, messaging, auto-attendant, and interactive voice response telecommunications systems that require a response from a user within a time interval shall give an alert when the time interval is about to run out, and shall provide sufficient time for the user to indicate more time is required.

(e) Where provided, caller identification and similar telecommunications functions shall also be available for users of TTYs, and for users who cannot see displays.

(f) For transmitted voice signals, telecommunications products shall provide a gain adjustable up to a minimum of 20dB. For incremental volume control, at least one intermediate step of 12dB of gain shall be provided.

(g) If the telecommunications product allows a user to adjust the receive volume, a function shall be provided to automatically reset the volume to the default level after every use.

(h) Where a telecommunications product delivers output by an audio transducer which is normally held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided.

(i) Interference to hearing technologies (including hearing aids, cochlear implants, and assistive listening devices) shall be reduced to the lowest possible level that allows a user of hearing technologies to utilize the telecommunications product.

(j) Products that transmit or conduct information or communication shall pass through cross-manufacturer, non-proprietary, industry-standard codes, translation protocols, formats, or other information necessary to provide the information or communication in a usable format. Technologies which use encoding, signal compression, format transformation, or similar techniques shall not remove information needed for access or shall restore it upon delivery.

(k)(1) Products that have mechanically operated controls or keys shall comply with the following: Controls and Keys shall be tactilely discernible without activating the controls or keys.

(k)(2) Products which have mechanically operated controls or keys shall comply with the following: Controls and Keys shall be operable with one hand and shall not require tight grasping, pinching, twisting of the wrist. The force required to activate controls and keys shall be 5 pounds (22.2N) maximum.

(k)(3) Products that have mechanically operated controls or keys shall comply with the following: If key repeat is supported, the delay before repeat shall be adjustable to at least 2 seconds. Key repeat rate shall be adjustable to 2 seconds per character.

(k)(4) Products which have mechanically operated controls or keys shall comply with the following: The status of all locking or toggle controls or keys shall be visually discernible, and discernible either through touch or sound.

Section 1194.24 Video and Multimedia Products

(a) All analog television displays 13 inches and larger, and computer equipment that includes analog television receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals.

(b) Television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry.

(c) All training and informational video and multimedia productions that support the agency’s mission, regardless of format, that contain speech or other audio information necessary for the comprehension of the content shall be open or closed captioned.

(d) All training and informational video and multimedia productions which support the agency’s mission, regardless of format, that contain visual information necessary for the comprehension of the content shall be audio described.

(e) Display or presentation of alternate text presentation or audio descriptions shall be user-selectable unless permanent.

Section 1194.25 Self-Contained, Closed Products

(a) Self-contained products shall be usable by people with disabilities without requiring an end-user to attach Assistive Technology to the product. Personal headsets for private listening are not Assistive Technology.

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

(c) Where a product utilizes touch screens or contact-sensitive controls, an input method shall be provided that complies with §1194.23 (k) (1) through (4).

(d) When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided.

(e) When products provide auditory output, the audio signal shall be provided at a standard signal level through an industry-standard connector that will allow for private listening. The product must provide the ability to interrupt, pause, and restart the audio at any time.

(f) When products deliver voice output in a public area, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. Where the ambient noise level of the environment is above 45dB, a volume gain of at least 20dB above the ambient level shall be user selectable. A function shall be provided to automatically reset the volume to the default level after every use.

(g) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

(h) When a product permits a user to adjust color and contrast settings, a range of color selections capable of producing a variety of contrast levels shall be provided.

(i) Products shall be designed to avoid causing the screen to flicker with a frequency greater than 2Hz and lower than 55Hz.

(j)(1) Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following: The position of any operable control shall be determined with respect to a vertical plane, which is 48 inches in length, centered on the operable control, and at the maximum protrusion of the product within the 48- inch length on products which are freestanding, non-portable, and intended to be used in one location and which have operable controls.

(j)(2) Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following: Where any operable control is 10 inches or less behind the reference plane, the height shall be 54 inches maximum and 15 inches minimum above the floor.

(j)(3) Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following: Where any operable control is more than 10 inches and not more than 24 inches behind the reference plane, the height shall be 46 inches maximum and 15 inches minimum above the floor.

(j)(4) Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following: Operable controls shall not be more than 24 inches behind the reference plane.

Section 1194.26 Desktop and Portable Computers

(a) All mechanically operated controls and keys shall comply with §1194.23 (k) (1) - (4).

(b) If a product utilizes touch screens or touch-operated controls, an input method shall be provided that complies with §1194.23 (k) (1) - (4).

(c) When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided.

(d) Where provided, at least one of each type of expansion slot, port, and connector shall comply with publicly available industry standards.

Section 1194.31 Functional Performance Criteria

(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided.

(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided.

(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided.

(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.

(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided.

(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.

Section 1194.41 Information, Documentation, and Support

(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge.

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

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

<Template version 0.0 (Last Modified on XX XX, XXXX)>

PAGE