EPLC Section 508 Test Results Template 1 .doc

FDA OIM-Section 508 Test Results Template

FDA OIM- Section 508 Test Results Template

Food and Drug Administration

<Project Name & Release Version #>

OFFICE OF INFORMATION MANAGEMENT (OIM)

SECTION 508 TEST RESULT TEMPLATE

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

[This document is a template of a Section 508 Test Result Template Document 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 Boundary 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

Section 508 Test Results (Web) 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 vTemplate Instructions:

Section 508 Overview

Section 508 Resources

Section 508 Findings for Web-based Applications

23.1 1194.22(a) Text Equivalent for Every Non-Text Element

23.1.1 Test Overview

23.1.2 Violations

23.1.3 Recommendations

23.2 1194.22(b) Equivalent Alternative for Multimedia

23.2.1

33.2.2

33.2.3

33.3 1194.22(c) Information is Conveyed without Color

33.3.1

33.3.2

33.3.3

43.4 1194.22(d) Readable without Style Sheets

43.4.1

43.4.2

43.4.3

43.5 1194.22(e) Redundant Links for Server-side Image Maps

43.5.1

53.5.2

53.5.3

53.6 1194.22(f) Client-side Image Maps

53.6.1

53.6.2

53.6.3

63.7 1194.22(g & h) Row and Column Headers for Data Tables

63.7.1

63.7.2

63.7.3

63.8 1194.22(i) Titles for Frames

63.8.1

73.8.2

73.8.3

73.9 1194.22(j) Flicker Test

73.9.1

73.9.2

73.9.3

83.10 1194.22(k) Text Only Equivalent

83.10.1

83.10.2

83.10.3

83.11 1194.22(l) Functional Text for Script elements

83.11.1

93.11.2

93.11.3

93.12 1194.22(m) Plug-in Required to Access Content

93.12.1

93.12.2

93.12.3

103.13 1194.22(n) Online Forms

103.13.1

103.13.2

103.13.3

103.14 1194.22(o) Skip Navigation

103.14.1

113.14.2

113.14.3

113.15 1194.22(p) Timed Responses

113.15.1

113.15.2

113.15.3

Section 508 Findings for Software Applications and Operating Systems

124.1 1194.21(a) Ensure Keyboard Control of Applications

124.1.1

124.1.2

124.1.3

124.2 1194.21(b) Applications Shall Not Disrupt or Disable Accessibility Features

124.2.1

134.2.2

134.2.3

134.3 1194.21(c) On-screen & Programmatic Indication of Focus

134.3.1

134.3.2

134.3.3

134.4 1194.21(d) Information about a User Interface Element Must Be Textually Available

134.4.1

144.4.2

144.4.3

144.5 1194.21(e) Standard Use of Images

144.5.1

144.5.2

154.5.3

154.6 1194.21(f) Textual Information Available through Operating System Functions

154.6.1

154.6.2

154.6.3

154.7 1194.21(g) Application Allows for Custom Contrasts and Colors

154.7.1

154.7.2

164.7.3

164.8 1194.21(h) Ensure Information is Displayable without Animation

164.8.1

164.8.2

164.8.3

164.9 1194.21(i) Color Coding

164.9.1

164.9.2

174.9.3

174.10 1194.21(j) Custom Color and Contrast Settings

174.10.1

174.10.2

174.10.3

174.11 1194.21(l) Electronic forms are usable

174.11.1

174.11.2

184.11.3

Section 508 1194.23 – Telecommunications Products

Section 508 1194.24 – Video and Multimedia Products

Section 508 1194.25 – Self Contained, Closed Products

Section 508 1194.26 – Desktop and Portable Computers

Next Steps

Template Instructions:

In support of the Project Management team this template has been provided to assist in documenting Section 508 Compliance Testing Results. 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 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 areas of the template. Test processes in accordance with the Software Testing Policy cannot be removed from the template without approval.

Please note that this template addresses two areas of Section 508 compliance: Web Applications and Software Applications/Operating Systems. Only complete the section that applies to your application.

The preferred tool for testing is the OIM preferred testing tool for Section 508 Compliance is SSB Bart Group’s Accessibility Management Platform InFocus tool. For access and tutorial information for AMP/Infocus, please contact Nisha Vohra.

1 Section 508 Overview

Section 508 of the Rehabilitation Act of 1973, as amended, requires that all electronic information technology procured, maintained, or used by the Federal Government must be accessible to persons with disabilities. As part of the FDA’s adherence, the DOS Testing and QA Team perform Section 508 compliance testing using the InFocus™ Tool, a subset of the Accessibility Management Platform (AMP) tool. The AMP/InFocus tool is currently set up to check against all areas of Section 508 as it pertains to software and web applications.

This document summarizes the findings, explains the nature of the violation and provides recommendations.

2 Section 508 Resources

Section 508 compliance, or Pass criteria, is met when all test scenarios successfully complete with out any Section 508 Compliance violations.

For additional information on Section 508, please visit the following links:

· http://www.hhs.gov/web/508/index.html

· http://www.hhs.gov/web/policies/standardscategory.html

· http://www.fda.gov/AboutFDA/AboutThisWebsite/Accessibility/default.htm

· http://www.access-board.gov/508.htm

· www.section508.gov To review the results in the AMP/InFocus tool, please use the following link:

<Link to AMP/InFocus report>

3 Section 508 Findings for Web-based Applications These findings represent the results of Section 508 testing as it pertains to web-based applications.

3.1 1194.22(a) Text Equivalent for Every Non-Text Element

(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).

The page developer should add appropriate alt attributes for images that do not contain alt attribute. An alt attribute should be a concise and meaningful replacement for the image. For example, when describing a picture of a red balloon, entering alt=”red balloon” will be more helpful than alt=”This is a picture of a red balloon”. If the image does not convey any meaning, such as a spacer image or separation line, or if the image is redundant to adjacent text enter a null alt attribute (alt=””) should be assigned.

3.1.1 Test Overview

<Test Name in Quality Center> Ex:

1194.22(a) Text Equivalent <Description of how this was tested> Ex:

AMP/InFocus tool crawled the website to a depth of # to include ### pages to identify violations.

<N/A must be accompanied with an explanation>

3.1.2 Violations

<Complete this table with identified violations.>

FDA Basics for Industry

3.1.3 Recommendations

<Complete this table with identified recommendations.>

3.2 1194.22(b) Equivalent Alternative for Multimedia

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

Developers must provide synchronized captioning for multimedia presentations.

3.2.1 Test Overview

<Test Name in Quality Center> Ex:

1194.22(b) Alternative Text for Multimedia <Description of how this was tested>

Ex:

AMP/InFocus tool crawled the website to a depth of # to include ### pages to identify violations

3.2.2 Violations

3.2.3 Recommendations

<Complete this table with identified recommendations.>

3.3 1194.22(c) Information is Conveyed without Color

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

If there is any information that is being conveyed by Bolding, italicizing, or color highlighting on a page, screen readers will not be able to pick up on this content. To make the same information accessible, change the information flow to represent the significance of the content without using colors. For example, the election map that shows blue and red states can not be read by a screen reader. However, if a table existed on the page with the same information then the requirement is met.

3.3.1 Test Overview

<Test Name in Quality Center> Ex:

1194.22(c) Information is Conveyed without Color <Description of how this was tested>

Ex:

AMP/InFocus tool crawled the website to a depth of # to include ### pages to identify violations.

3.3.2 Violations

3.3.3 Recommendations

<Complete this section with identified recommendations.>

3.4 1194.22(d) Readable without Style Sheets

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

Style sheets can enable users to define specific viewing preferences to accommodate their disability. For instance, users with low vision may create their own style sheet so that, regardless of what web pages they visit, all text is displayed in an extra large font with white characters on a black background. If designers set up their pages to override user-defined style sheets, people with disabilities may not be able to use those pages. For good access, therefore, it is critical that designers ensure that their web pages do not interfere with user-defined style sheets.

3.4.1 Test Overview

<Test Name in Quality Center> Ex.:

1194.22 (d) Readable without Style Sheets <Test Case Description>

<User Role>

<Preconditions> AMP/InFocus tool crawled the website to a depth of # to include ### pages to identify violations.

3.4.2 Violations

3.4.3 Recommendations

3.5 1194.22(e) Redundant Links for Server-side Image Maps

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

A server-side image map refers to a map where coordinates from the active region are relayed back to the server for additional processing to determine the destination of the link. As a result, screen readers are not able to play back meaningful text for the coordinates on the image map. It is imperative that redundant text links be provided for server-side image maps.

3.5.1 Test Overview

<Test Name in Quality Center> Ex:

<Test Case Description>

<User Role>

<Preconditions>

3.5.2 Violations

3.5.3 Recommendations

3.6 1194.22(f) Client-side Image Maps

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

Client-side image maps provide better accessibility than server-side image maps because a screen reader can easily identify an active regions of a client-side image map and playback the appropriate playback messages. If active regions in an image map can be represented in geometric shapes, then a client-side image map should be used. Each image must contain the “usemap” attribute. Use the <map> and <area> tags to identify the map and regions. Each defined area must contain a value for the alt attribute.

3.6.1 Test Overview

<User Role>

<Preconditions>

3.6.2 Violations

3.6.3 Recommendations

3.7 1194.22(g & h) Row and Column Headers for Data Tables

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

Paragraphs (g) and (h) permit the use of tables, but require that the tables be coded according to the rules of the markup language being used for creating tables. Large tables of data can be difficult to interpret if a person is using a non-visual means of accessing the web. Users of screen readers can easily get "lost" inside a table because it may be impossible to associate a particular cell that a screen reader is reading with the corresponding column headings and row names.

3.7.1 Test Overview

<User Role>

<Preconditions>

3.7.2 Violations

3.7.3 Recommendations

3.8 1194.22(i) Titles for Frames

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

Frames divide the screen into distinct areas that can behave separately and can create problems for users with disabilities. Frames must be easily identified using the title attribute.

3.8.1 Test Overview

<User Role>

<Preconditions> Frames have “title” attributes defined with descriptive names.

<Pass, Fail, or N/A>

3.8.2 Violations

3.8.3 Recommendations

3.9 1194.22(j) Flicker Test

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

In addition to being a distraction on the screen, blinking, flashing, or flickering content on a page can affect seizures in individuals with photosensitive epilepsy. Content that can flicker includes Java applets, videos, JavaScript, animated gifs, and Flash content.

3.9.1 Test Overview

<User Role>

<Preconditions>

3.9.2 Violations

3.9.3 Recommendations

3.10 1194.22(k) Text Only Equivalent

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

A great deal of content may be embedded in objects that are not accessible to screen readers. Examples include scanned pictures of documents, audio files, and videos. Content developers must make this information available to disabled users. Scanned pictures of documents must be transcribed. Audio files must have an available transcript. Video files must have captioning.

Note: PDF documents that are properly created can be read by a screen reader and do not require a text-only equivalent version.

3.10.1 Test Overview

<User Role>

<Preconditions>

3.10.2 Violations

3.10.3 Recommendations

3.11 1194.22(l) Functional Text for Script elements

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

When inadequate functional text is provided, screen readers often attempt to read the contents of the script in an unintelligible jumble of letters and numbers. In addition, there are specific JavaScript event handlers that should be avoided because they are device specific. For example, the OnClick event handler is specific to mouse input disabled users may not be using a mouse. The alternative event handler would be OnKeyPress.

3.11.1 Test Overview

<User Role>

<Preconditions> All scripts are clearly marked.

All device specific event handlers are replaced with alternative event handlers.

<Pass, Fail, or N/A>

3.11.2 Violations

3.11.3 Recommendations

3.12 1194.22(m) Plug-in Required to Access Content

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

Non-html content often requires more than just a browser. Browser Plug-ins and third party applications are often required to render this content in a meaningful fashion. Section 508 states that a link to this plug-in must be available on every page where plug-ins is required.

3.12.1 Test Overview

<User Role>

<Preconditions>

3.12.2 Violations

3.12.3 Recommendations

3.13 1194.22(n) Online Forms

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

The interaction between form controls and screen readers can be unpredictable. The design of the page can contain many controls and labels that might not be properly associated.

3.13.1 Test Overview

<User Role>

Label tags only contain text and do not contain extraneous HTML tags.

<Pass, Fail, or N/A>

3.13.2 Violations

3.13.3 Recommendations

3.14 1194.22(o) Skip Navigation

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

Global navigation provides ease-of-use, and a uniform look and feel. However, screen readers will playback messages for each global navigation element each time that a page loads. If these elements are the same on every screen, these messages can be tedious and unnecessary. Section 508 guidelines state that these pages must contain a mechanism to skip past repetitive global navigation to ease the burden on users with screen readers.

3.14.1 Test Overview

<User Role>

<Preconditions>

3.14.2 Violations

3.14.3 Recommendations

3.15 1194.22(p) Timed Responses

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

Timed responses are oftentimes used as a security measure but can create accessibility problems for those with disabilities. For example, users with poor vision may take longer to complete forms and data may be lost when the session “times out.” Users with poor vision may also take longer to read a long page. For this reason, when a timed response is required, the user shall be alerted via prompt and given sufficient time to indicate whether additional time is needed.

3.15.1 Test Overview

<User Role>

If sessions expire, then a mechanism must exist to prompt the user to extend the session and give the user ample time to respond.

When session is extended, the page is not refreshed.

<Pass, Fail, or N/A>

3.15.2 Violations

3.15.3 Recommendations

4 Section 508 Findings for Software Applications and Operating Systems These findings represent the results of Section 508 testing as it pertains to software applications and operating systems.

4.1 1194.21(a) Ensure Keyboard Control of Applications

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

4.1.1 Test Overview

<User Role>

<Preconditions>

4.1.2 Violations

4.1.3 Recommendations

4.2 1194.21(b) Applications Shall Not Disrupt or Disable Accessibility Features

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

4.2.1 Test Overview

<User Role>

<Preconditions>

4.2.2 Violations

4.2.3 Recommendations

4.3 1194.21(c) On-screen & Programmatic Indication of Focus

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

4.3.1 Test Overview

<User Role>

<Preconditions>

4.3.2 Violations

4.3.3 Recommendations

4.4 1194.21(d) Information about a User Interface Element Must Be Textually Available

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

4.4.1 Test Overview

<User Role>

<Preconditions>

4.4.2 Violations

4.4.3 Recommendations

4.5 1194.21(e) Standard Use of Images

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

4.5.1 Test Overview

<User Role>

<Preconditions>

4.5.2 Violations

4.5.3 Recommendations

4.6 1194.21(f) Textual Information Available through Operating System Functions

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

4.6.1 Test Overview

<User Role>

<Preconditions>

4.6.2 Violations

4.6.3 Recommendations

4.7 1194.21(g) Application Allows for Custom Contrasts and Colors

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

4.7.1 Test Overview

<User Role>

<Preconditions>

4.7.2 Violations

4.7.3 Recommendations

4.8 1194.21(h) Ensure Information is Displayable without Animation

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

4.8.1 Test Overview

<User Role>

<Preconditions>

4.8.2 Violations

4.8.3 Recommendations

4.9 1194.21(i) Color Coding

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

4.9.1 Test Overview

<User Role>

<Preconditions>

4.9.2 Violations

4.9.3 Recommendations

4.10 1194.21(j) Custom Color and Contrast Settings

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

4.10.1 Test Overview

<User Role>

<Preconditions>

4.10.2 Violations

4.10.3 Recommendations

4.11 1194.21(l) Electronic forms are usable

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

4.11.1 Test Overview

<User Role>

<Preconditions>

4.11.2 Violations

4.11.3 Recommendations

5 Section 508 1194.23 – Telecommunications Products Section 508 1194.23 covers Telecommunications Products and mimics the language of Section 255 of the Telecommunications Act of 1996 which mandates phone manufacturers and telecommunications providers must make their products accessible. The Testing and QA team encourages Section 508 compliance in this area but does not test for compliance in this area as it is outside the scope of software testing.

6 Section 508 1194.24 – Video and Multimedia Products Section 508 1194.24 applies to multimedia and captioning requirements for multimedia productions. The Testing and QA team encourages Section 508 compliance in this area but does not test for compliance in this area as it is outside the scope of software testing.

7 Section 508 1194.25 – Self Contained, Closed Products Section 508 1194.25 applies to self contained, closed products such as calculators, ATM machines, and copy machines. The Testing and QA team encourages Section 508 compliance in this area but does not test for compliance in this area as it is outside the scope of software testing.

8 Section 508 1194.26 – Desktop and Portable Computers Section 508 1194.26 applies to hardware requirements for desktop and laptop computers. The Testing and QA team encourages Section 508 compliance in this area but does not test for compliance in this area as it is outside the scope of software testing.

9 Next Steps

Now that Section 508 Testing has been completed on the application, it is important to document the violations in HP Quality Center as defects to be tracked. Each Section 508 defect must be addressed to exit the Stage Gate. Depending on the nature of the violation, you may address a defect in one of the following ways:

· Item is not applicable and rationale for why the area is not applicable.

· Items that will be addressed in a future patch or software release.

· Items that will be remediated before go-live.

· Items that can not be addressed because of undue burden and/or the nature of the technology.

· Additional testing/retesting that will be done to validate that any fixes are successful.

· Application for an accommodation and/or waiver.

Keep this document with other project deliverables. The project may be called upon to provide documentation and test results in a future audit or appraisal.

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

PAGE