II_1 ATTACHMENT B - applicable-provisions-and-testing-DID (082119).doc

<Modify the heading according to the following example: Applicable Provisions and Testing 3.2 for Return Authorization Data (RAD), Release 1, Milestone 3, Submitted 7/22/2012> Applicable Provisions and Testing for ( ), Release , Milestone , Submitted 1 This Document

1.1 About this Document

The Applicable Provisions and Testing document indicates which Section 508 provisions apply to the system, details how the provisions will be tested and records the results. Different parts are required at different times. It should be completed in stages, beginning with the selection of applicable provisions.

1.2 Change History for this Document

<Enter the detailed change history for this document in the table below>

2 System Description <In several paragraphs, describe the user interfaces of the system. This description is not merely the business purpose of the system. Where possible, list the specific software used, and the components that will be installed. The focus should be on the parts of the system operated by users: forms, controls, screens.> 3 Provisions Index This index links to sections within this document, whose section numbers link back up to this index. The § symbol refers to sections within the subparts of the Section 508 Standards published by the U.S. Access Board. To use the links, you must unprotect the document via the tools menu (Alt-T), but must protect it again before entering data.

Instructions on Provisions and Testing § 1194.21 Software applications and operating systems

1194.21 (a) Executing Function from Keyboard

1194.21 (b) Accessibility Features

1194.21 (c) Input Focus

1194.21 (d) User Interface Element

1194.21 (e) Bitmap Images

1194.21 (f) Textual Information

1194.21 (g) User Selected Attributes

1194.21 (h) Animation

1194.21 (i) Color Coding

1194.21 (j) Color and Contrast Settings

1194.21 (k) Flashing or Blinking Text

1194.21 (l) Electronic Forms

§ 1194.22 Web-based intranet and internet information and applications

1194.22 (a) Text Tags

1194.22 (b) Multimedia Presentations

1194.22 (c) Color

1194.22 (d) Readability

1194.22 (e) Server-Side Image Maps

1194.22 (f) Client-Side Image Maps

1194.22 (g) Data Table 1

1194.22 (h) Data Table 2

1194.22 (i) Frames

1194.22 (j) Flicker Rate

1194.22 (k) Text-Only Alternative

1194.22 (l) Scripts

1194.22 (m) Applets and Plug-Ins

1194.22 (n) Electronic Forms

1194.22 (o) Navigation Links

1194.22 (p) Time Delays

§ 1194.23 Telecommunications products

1194.23 (a) TTY Connection/Microphones

1194.23 (b) TTY Signal Protocols

1194.23 (c) Interactive Voice Response Systems

1194.23 (d) Time Interval Alerts

1194.23 (e) Caller ID and Similar Functions

1194.23 (f) Volume Control

1194.23 (g) Automatic Volume Level Reset

1194.23 (h) Hearing Aid Compatibility

1194.23 (i) Minimized Interference

1194.23 (j) Transmitting/Conducting Information

1194.23 (k) Controls and Keys

§ 1194.24 Video and multimedia products

1194.24 (a) Caption Decoder Circuitry

1194.24 (b) Audio Description Circuitry

1194.24 (c) Video and Multimedia Productions 1

1194.24 (d) Video and Multimedia Productions 2

1194.24 (e) User-Select Feature

§ 1194.25 Self contained, closed products

1194.25 (a) Usability

1194.25 (b) Timed Responses

1194.25 (c) Touchscreens and Controls

1194.25 (d) Biometric Forms/User ID

1194.25 (e) Auditory Output

1194.25 (f) Volume Control

1194.25 (g) Color Coding

1194.25 (h) Color and Contrast Settings

1194.25 (i) Screen Flicker

1194.25 (j) Operable Controls

§ 1194.26 Desktop and portable computers

1194.26 (a) Controls and Keys

1194.26 (b) Touchscreens and controls

1194.26 (c) Biometric User ID

1194.26 (d) Connection Points

§ 1194.31 Functional performance criteria

1194.31 (a) No Vision Required

1194.31 (b) Visual Alternatives

1194.31 (c) No Hearing Required

1194.31 (d) Audio Enhancement/Devices

1194.31 (e) No Speech Required

1194.31 (f) No Fine Motor Control

§ 1194.41 Information, documentation, and support

1194.41 (a) Accessible Formats

1194.41 (b) Accessibility Features Access

1194.41 (c) Accessible Support Services

3 Applicable Provisions and Testing Instructions The table below illustrates the structure of each provision entry and provides instructions for how to submit your entries in each section.

Select the checkbox to indicate that a provision applies.

Based on test results, select the checkbox to indicate that a provision is met.

§ 1194.21 Software applications and operating systems

1. Verify that interactive application objects can accept and release keyboard focus as expected.

2. Verify that application objects that execute functions can do so from the keyboard

Affected Application Objects (and attributes)

1. All interactive application functionality

Testing Procedure

1. Use the keyboard to navigate to all executable / interactive application functions.

2. Verify that these functions can be executed from the keyboard.

3. Verify that the application does not provide mouse-only activated features. Verify that all content and functions accessed using the mouse can be accessed from the keyboard.

4. Verify that the context menu provided via mouse right click is available via keyboard context menu key.

5. Verify that the context menu provided via mouse right click is the same as what is provided via the keyboard context menu key.

1. Verify that the application functions are not disrupted when installing Assistive Technology (AT) or when the accessibility features of the Operating System are executed.

2. Verify that installed AT and the accessibility features of the Operating System are not disrupted when the application is executed.

Affected Application Objects (and attributes)

1. All the accessibility features of the operating system such as Narrator, Magnifier, On-Screen Keyboard and the standard COE approved Assistive Technology tools (JAWS, ZoomText and Dragon Naturally Speaking)

2. The application features and functions

Testing Procedure

1. From Control Panel, open Accessibility Options, Check the following options: Keyboard tab – Use StickyKeys; Use ToggleKeys, Sound tab – Use SoundSentry, Display tab – Use High Contrast

2. Execute the application; execute all installed AT while the application is running.

a. Step through an application use case.

b. Verify that the application features and functions are not disrupted.

c. Verify that the installed AT features and functions are not disrupted.

d. Verify that the options checked in (1) are still checked and have not been disabled.

3. Execute the installed AT; execute application while the installed AT applications are running

a. Step through an application use case.

b. Verify that the application features and functions are not disrupted.

c. Verify that the installed AT features and functions are not disrupted.

d. Verify that the options checked in (1) are still checked and have not been disabled.

1. Verify that application provides a well defined onscreen focus.

2. Verify that focus is consistently maintained and changes in a logical and predictable manner.

3. Verify that the visual focus is synchronized with programmatic focus.

4. Verify that focus is maintained for items in context menus.

Affected Application Objects (and attributes)

1. All interactive application objects

Testing Procedure

1. Use a tool that can expose the properties of the application objects and check the following:

a. If the object is focusable.

b. If the object is keyboard focusable.

c. If (a) and (b) are valid for context menus.

2. Verify that non-interactive application objects such as read-only, disabled, and static text objects do not receive focus.

3. Verify that application child windows, dialog boxes, dockable panes, splitter panes and non-dockable panes can accept and transfer focus to child focusable objects as expected.

4. Verify that the focus is not trapped in any application object.

1. Verify that every interactive application object has a name and provides its role and state information to the operating system.

2. Verify that every image that represents a program element has a name or alternative text associated that can be accessed programmatically

Affected Application Objects (and attributes)

1. All interactive application objects

2. Images that represent program elements

Testing Procedure

1. Use a tool that can expose the properties of application objects and images that represent program elements and check the following:

a. If the object has a Name (referenced as 'Identity' above).

b. If the object provides its State information.

c. If the object provides its Role (referenced as 'Operation' above) information.

1. Verify that the meaning assigned to images that represent program elements is consistent through the application's performance.

Affected Application Objects (and attributes)

1. Images that represent program elements

Testing Procedure

2. Use a tool that can expose the properties of images that represent program elements and check the following:

a. If the image has a Name (Identity) or Alternative text.

b. If the image provides its State information.

c. If the object provides its Role (Operation) information.

d. Verify that the information in (a), (b) and (c) are consistent through out the application.

1. Verify that textual information requested and displayed is provided through standard operating system functions for requesting and displaying textual information.

2. Verify that information obtained through text entry fields is exposed to assistive technology.

Affected Application Objects (and attributes)

All application objects that request and display information

Testing Procedure

1. Use a tool that can expose the properties of application objects that request and display information and check the following:

a. If the object has a Name (Identity).

b. If the object provides its State information.

c. If the object provides its Role ('Operation') information.

d. If the object is focusable.

e. If the object is keyboard focusable.

f. If the object's value information is identical to the information entered in text entry field.

1. Verify that application does not override a user’s system-wide color contrast settings.

2. Verify that application does not override a user’s system-wide display attributes settings.

Affected Application Objects (and attributes)

1. Color contrast settings

2. Display attributes settings

Testing Procedure

Color Contrast

1. From Control Panel, open Accessibility Options, and check the following option: Display tab – Use High Contrast. Go to settings and select a high contrast appearance scheme. Execute the application and check that the High Contrast appearance configurations are respected.

2. From Control Panel, open Appearance and Themes, select Display: in the Appearance tab, click Advanced and configure Advanced Appearance settings. Execute the application and check that the Appearance configurations are respected.

3. If the application provides custom color and contrast settings and display attribute settings, configure a setting different from the operating system's. Verify that the application’s custom settings apply only to the application and not the operating system.

1. Verify that information displayed through animation is available in a non- animated mode (stationary object).

Affected Application Objects (and attributes)

1. Animated application objects

Testing Procedure

Verify that all animated content and application information is also made available through a non-animated mode.

1. Determine that no information is conveyed with color alone.

2. Determine that there is sufficient contract between the foreground and background for all rendered textual objects.

Affected Application Objects (and attributes)

1. All application objects that convey information to the user.

Testing Procedure

1. Look for use of color coding such as a legend.

2. Look for color-based directives such as “the red asterisk.”

3. Look for use of color to tell items apart.

4. If any information is being presented in a color other than the default color, verify that the information is still conveyed if that color is changed to the default color.

1. Verify that color contrast settings of an application provide all the color selections available through the operating system.

Affected Application Objects (and attributes)

1. Application color contrast settings.

1. If the application provides a color contrast setting function / utility, launch the function / utility. Verify that the color contrast options presented are at least equal to the options found in the Windows Paint application. (Start -> Programs -> Accessories -> Paint. From the Colors menu, select Edit Colors…)

1. Determine that all moving, flickering, sliding and pulsating objects have a flash frequency of less than or equal to 2 cycles a second.

Affected Application Objects (and attributes)

1. All application objects.

1. Identify all moving, flickering, sliding and pulsating objects and observe their rate of change by timing how long any number of blinks take. The number of blinks divided by the number of seconds observed should be less than two. In other words, items should blink no more than two times a second. Verify that no object is changing with a frequency greater than two times a second.

1. Determine that form elements have been labeled appropriately.

2. Determine that group elements (such as radio buttons) have been group labeled appropriately.

3. Determine that all form-filling directives, cues, error messages and notification methods have been appropriately defined and presented.

4. Determine that image buttons defined appropriate descriptive alternative text property.

Affected Application Objects (and attributes)

1. All application information accepting objects such as Combo boxes, Edit controls, List boxes, and Tree controls.

Testing Procedure

Form Element Label

1. Verify that the form has a heading (title).

2. Use a tool that can expose the properties of application objects and check the following:

a. If the object has a Name (Identity).

b. If the object provides its State information.

c. If the object provides its Role (Operation) information.

Group Label

Manual Test (with capable tool):

1. Use a manual tool that can isolate fieldset objects.

2. Verify that each group label object has a corresponding title text.

3. Verify that related checkboxes and radio buttons are group labeled.

4. Verify that all logically grouped form objects are also group labeled. E.g. input boxes for ‘Area Code:’, ‘number’ and ‘Extension.’ could be group labeled ‘Telephone.’

Keyboard Access

Manual Test (with capable tool):

1. Use a tool that can expose the properties of application objects and check the following:

1. If the object is focusable.

2. If the object is keyboard focusable.

3. Verify that user focus moves in a logical order, is maintained, and does not disappear.

Directives, Cues, Color Coded Information, Validation Messages, etc.

1. Scan page for form cues and directives such as "required fields" and "completion order."

o Verify that all such directives and cues are placed at the top of the form when they apply to the entire form.

o Verify that directives and cues for individual form elements are placed within the elements' label definition.

2. Check for color-coded information.

o Verify that color alone has not been used to convey any information on the form.

o Check for “color validation” error messages.

3. Verify that a numeric quantity of errors found is listed and placed first within the error message block before the list of errors.

4. Verify that error messages are either presented in a JavaScript alert box or incorporated into the page and placed at the top of the form.

5. Verify that the user is alerted in an accessible manner when new error information is added to the page.

Web Provisions

§ 1194.22 Web-based intranet and internet information and applications

Determine that textual equivalents (TE) for all non-text elements such as graphics, multimedia objects and inline frames are provided.

1. Verify that all image elements have alternative text. Images that do not convey any information should have the ‘alt’ attribute set to null e.g. alt=’’

2. Verify that background images do not convey meaningful information, since there is no easy method to define their equivalent alternative text (including using the title attribute.)

3. Verify that client-side image map links define textual equivalents for their respective geometric area hotspots via the alt attribute <area alt=’TE’> Note, null alt (alt=’’) definitions are not acceptable for <area> element definitions.

4. Verify that video, audio, multimedia objects, and inline frames contain the equivalent alternative text in their element content e.g. <object>TE</object> or <iframe>TE</iframe>

Affected HTML Elements (and attributes)

<img alt=’TE’>, <area alt=’TE’>, <object>TE</object>, <embed alt=’TE’>TE</embed>, <applet alt=’TE’>, <iframe>TE</iframe>, <input type=’image’ alt=’TE’>

Testing Procedure

1. Automated Test: Use an automated tool that can identify the affected elements above and verify that alternative content has been adequately provided.

2. Manual Test: Use a manual tool that can isolate and expose the affected elements above and ensure textual equivalents have been adequately provided.

3. Manual Test: Use a manual tool that can isolate and expose all the background images and ensure that they do not convey meaningful information.

4. Manual Test: Search the source code for each of the elements above and examine the elements as defined and ensure textual equivalents have been adequately provided. (This may not be very effective because the source HTML may not reflect the rendered information.)

Test Results

1. Determine that video, audio and multimedia objects have synchronized captions rendered in conjunction with the presentation media playback.

2. Determine that video and audio presentations have the equivalent alternative content defined as audio descriptions and / or transcripts.

Affected HTML Elements (and attributes)

<applet>, <embed>, <objects>

Testing Procedure

1. Automated Test: Use an automated tool that can identify the affected elements above and verify that the media source file defined in the elements is an integrated source and caption file e.g. .SMIL, .ASX (.SAMI), etc.

2. Manual Test: Review the audio track and verify that a captioned equivalent is displayed in conjunction with the audio.

3. Review the visual track and verify that visual elements are described using a synchronized alternative.

4. Manual Test: Search the source code for each of the elements above and examine to determine if the element content contains audio descriptions and / or transcripts. E.g. <objects>Audio Descriptions / Transcripts</objects>

1. Determine that no information is conveyed with color alone.

Affected HTML Elements (and attributes)

All displayable HTML elements

Testing Procedure

Manual Test:

1. Look for use of color coding such as a legend.

2. Look for color-based directives such as “the red button.”

3. Look for use of color to tell items apart.

4. List the means other than color used to express that information.

Test Results

1. Determine that a logical reading order is maintained when all styles are removed (including all inline and CSS defined styles.)

2. Determine that no meaningful content is removed when all styles are removed (including all inline and CSS defined styles.)

3. Determine that the sequence of placement for all aggregate block element is maintained when all styles are removed (including all inline and CSS defined styles.)

Affected HTML Elements (and attributes)

All displayable HTML elements

Testing Procedure

Manual Test:

Use a manual tool that can remove all styles defined for display including inline and CSS defined styles and ensure that:

1. A logical reading order is maintained.

2. Information has not been lost.

3. Sequence of object placement are maintained.

Erroneous / out of context information is not displayed.

Test Results

1. If a page contains a server-side image map, determine that the page contains a redundant text link for each region of the server-side image map that provides a valid server destination.

Affected HTML Elements (and attributes)

<img ISMAP>, <input type=’image’>

Testing Procedure

Manual Test:

Use a manual tool that can identify server-side image maps or visually scan the source code file for <img ismap> elements and for each server-side image map do the following:

1. Determine the actionable hotspot URLs. (Hotspots that map to valid server destinations.)

2. Verify that redundant (additional) text links exist for the URLs.

1. If a page contains a server-side image map, determine that the active regions of the image map (hotspots that provide valid server destinations) cannot be defined with an available geometric shape

Affected HTML Elements (and attributes)

<img ISMAP>

Testing Procedure

Manual Test:

Use a manual tool that can identify server-side image maps or visually scan the source code file for <img ismap> elements and for each server-side image map do the following:

1. Verify that the actionable hotspot regions (Hotspots that map to valid server destinations) cannot be defined with any of the available geometric shapes.

2.Note that every image shape, can be defined with the <area shape= ‘circle’ or ‘rect’ or ‘poly’ coord=’Point1, Point2, PointN,’>.

Test Results

1. Determine if each subject table is a data table.

2. Determine that each data table has marked header cells and provides header information.

3. Verify that row and column header cells have been associated with row and column data cells respectively.

Affected HTML Elements (and attributes)

<table>, <th scope=’HeaderContextValue’>, <td scope=’ HeaderContextValue’>

HeaderContextValue = col, row, colgroup, rowgroup

Testing Procedure

Manual Test:

Visually scan page and source code, or use a manual tool that can identify data tables and for each data table do the following:

1. Verify that the header cells defined with a <th> element have scope attributes defined.

2. Verify that the header cells defined with a <td> element have scope attributes defined.

3. A <td> header cell can also qualify as header cell without a scope attribute definition if it has defined an ‘id’ attribute and another data cell includes that ‘id’ as part of its header through the “headers=’id1, id2, ..’.” associations.

Test Results

1. Determine if each subject table is a data table.

2. Determine that subject data table has two or more logical levels of row or column headers

Affected HTML Elements (and attributes)

<table>, <th id=’Cellid1’>, <td id=’CellId2’> <td headers=’CSV of HeaderCellIds’>

Testing Procedure

Manual Test:

Visually scan page and source code, or use a manual tool that can identify data tables and for each data table do the following:

1. Visually determine if subject table has two or more logical levels of row or column headers.

2. Scan the source code or use a manual tool that can isolate the table from the page source code. Verify that all data cells with more than one header have defined the IDs of the header cells in the attributes.

Test Results

1. Determine that an appropriate document type has been defined for the frameset markup.

2. Determine that the name and title attribute have been defined for all defined frames.

3. Determine that every non-frameset page (regular pages) has a unique and descriptive page title.

4. Determine that the <noframes> element has been defined and contains an anchor <a> link to the framed document(s).

Affected HTML Elements (and attributes)

<!doctype “-//W3C//DTD HTML 4.01 Frameset//EN”>, <frame name=’FameName’ title=’FrameTitle’>, <iframe name=’iframeName’ title=’iframeTitle’>, <noframes><a href=”frame document1.html”> <a href=”frame document2.html”> <a href=”frame document1.htm3”>… <noframes>

Testing Procedure

Manual Test:

Visually scan frameset source code, or use a manual tool that can isolate HTML element’s attributes / value pairs and do the following:

1. Verify that the correct document type has been specified as explained above.

2. Verify that every frame defined in the frameset provides a descriptive title and name attributes.

3. Verify that every stand-alone page defines a unique descriptive page title within the <head> element content, e.g. <title>Unique Descriptive Page Title Goes Here</title>

4. Verify that the <noframes> element has been defined for all defined frames and includes <a> links to the page framed documents, e.g.

<noframes><a href=”frame document1.html”> <a href=”frame document2.html”> <a href=”frame document1.htm3”>… <noframes>

1. Determine that all moving, flickering, sliding and pulsating objects have a frequency of less or equal to 2 cycles a second

Affected HTML Elements (and attributes)

<applet>, <blink>, <embed>, <img>, <input type=’image’>, <marquee>, <object>

Testing Procedure

Manual Test:

1. Identify all moving, flickering, sliding and pulsating objects and observe their rate of change by timing how long any number of blinks take. The number of blinks divided by the number of seconds observed should be less than two. In other words, items should blink no more than two times a second. Verify that no object is changing with a frequency greater than two times a second.

Test Results

1. Determine if the page contains a link to a text-only page.

2. If it does, verify that the page cannot be made to comply with the rest of the provisions of this standard(Section 508 1194.22 A – J and L - P)

Affected HTML Elements (and attributes)

<a>, <area>, form actions that produce text-only pages

Testing Procedure

Manual Test:

Visually scan source code, or use a manual tool that can isolate all the HTML links and other URI request definitions:

1. Examine links/URI definitions to text-only pages.

2. Verify that page cannot be made to comply with the rest of the provisions of this standard (Section 508 1194.22 A – J and L - P).

3. Verify that identical information and functionality are contained in both the text-only page and the subject page.

1. Determine that the page is accessible when scripts are executed, e.g. focus is maintained and rendered objects are keyboard accessible.

2. Determine that information created by script(s) is identified with functional text.

3. Determine that scripts do not define inaccessible events.

4. When a script defines an input device event to perform a script function, another input device or device independent event should be defined to perform the same function as well. For example, every onmousemove event should have a corresponding onfocus event.

5. Determine that accessible events have not been defined inaccessibly (e.g. defined on elements that are not focusable)

Affected HTML Elements (and attributes)

All HTML elements

Testing Procedure

Manual Test:

1. Visually scan source code or use a manual tool that can isolate all inaccessible events.

2. Visually scan source code or use a manual tool that can isolate all device dependent events without a corresponding device independent event.

3. Visually scan source code or use a manual tool that can isolate all accessible events that have been defined inaccessibly (e.g. defined on elements that are not focusable).

4. Verify that visual focus is not lost and moves appropriately when scripts are executed.

5. Verify that user is alerted when page content is updated by script action.

6. Verify that when scripts are executed, focus and logical reading order are maintained.

Test Results

1. Determine if page contains non-HTML content such as Java applest, integrated Office Documents, Adobe PDF documents, Adobe Flash, Active X component documents, etc.

2. If it does, verify that the page provides a link to the rendering plug-in or application that complies with the section 508 1194.21 provisions (A) to (L ).

Affected HTML Elements (and attributes)

<applet>, <embed>, <object>

Testing Procedure

Manual Test:

Visually scan source code, or use a manual tool that can isolate all the <embed>, <applet> and <object> elements and their attributes:

1. For <object> elements, check that the “codebase” attribute contains a valid URI that links to the rendering plug-in or application.

2. For <embed> elements, check that the “pluginspage” attribute contains a valid URI that links to the rendering plug-in or application.

3. In any case, this rendering plug-in or application as it renders the content on the page must comply with Section 508 1194.21 (A) – (L) provisions.

1. Determine that the form has heading information defined or form heading is implied and intuitive from the first labeled text of the form.

2. Determine that form elements have been labeled appropriately.

3. Determine that the Id attributes used for labels are unique.

4. Determine that no label object has been used more than once.

5. Determine that group elements such as radio buttons have been group labeled appropriately.

6. Determine that form-filling directives, cues, error messages and notification methods have been appropriately defined/presented.

7. Determine that image buttons define an appropriate descriptive alternative text property.

8. For public facing sites, determine that JavaScript has not been defined to accept form submissions.

Affected HTML Elements (and attributes)

<button>, <form>, <input>, <select>, <textarea>

Testing Procedure

Form Element Label

Manual Test (with capable tool):

1. Use a manual tool that can isolate form elements and their corresponding labels.

2. Verify that there are no duplicate label to element associations.

3. Verify that there are no orphaned labels or other inconsistent labeling.

Manual Test:

1. Visually scan page and source code and verify that forms have headings, preferably marked up using one of the html heading elements, e.g. <h2>Form Heading Information</h2>

2. Visually scan source code file for <input type=’text’ or type=’password’>, <input type=’checkbox’>, <input type=’radio’>, <select>, <textarea>.

3. Verify that each of these elements contains an id attribute with a unique value within the source file.

4. Verify that for each element that contains a valid unique id, there is a corresponding <label for=’UniqueId’> element and that no other label element defines the same ‘for’ attribute.

Fieldset and Legend

Manual Test (with capable tool):

1. Use a manual tool that can isolate fieldset elements, including the opening and closing tags and the element content.

2. Verify that each <fieldset> element has a corresponding <legend> element defined in the element content.

3. Verify that related radio buttons are group labeled.

4. Verify that all logically grouped form elements are also group labeled. E.g. input boxes for ‘Area Code:’, ‘number’ and ‘Extension.’ could be group labeled ‘Telephone.’

Manual Test:

1. Visually scan source code file for <fieldset>element. For each <fieldset> element, verify that there is a corresponding <legend> element in the element content of the <fieldset> element.

2. Visually scan source code file and rendered page for logically related form elements, such as a group of radio buttons. Verify that related radio buttons (<input type="radio">) are group labeled using this <fieldset> - <legend> relationship. For example <fieldset> <legend>Group label for radio buttons</legend><input type=’radio’ id=’Uniqueid1’> <input type=’radio’ id=’Uniqueid2’></fieldset>. (Note that in this example, the <label> elements and their text were intentionally left out for clarity.)

Keyboard Access

Manual Test (with capable tool):

1. Use a capable tool that can isolate elements and their attributes. Scan the page for any element that defines or sets “tabindex." Verify that values are in a logical order that corresponds to page tab order and that interactive elements do not have values set to negative numbers.

2. Verify that the form elements have logical reading order

3. Verify that the"form elements are keyboard accessible

Manual Test:

1. Tab through the displayed page and verify that the form elements have logical reading order.

2. Verify that user focus moves in a logical order, is maintained, and does not disappear.

Directives, Cues, Color Coded Information, Validation Messages, etc.

1. Scan the page for form cues and directives such as "required fields" and "completion order."

o Verify that all such directives and cues are placed at the top of the form when they apply to the whole form.

o Verify that directives and cues for individual form elements are placed within the elements' label definition.

2. Check for color-coded information.

o Verify that color alone has not been used to convey information on the form.

o Check for color validation error messages.

3. Verify that a numeric quantity of errors found is listed and placed first within the error message block before listing the errors.

4. Verify that error messages are either presented in a JavaScript "alert box" or incorporated into the page and placed at top of the form. If presented through JavaScript at the top of the form, set the error message block tabindex to -1 to enable a programmatic focus and set focus to the error message block.

5. Verify that the user is alerted in an accessible manner when new error information is added to the page (see the testing guide for 1194,22 L)

Image Buttons

1. Scan source code or use a tool that can isolate and expose the attributes of elements.

2. Verify that image buttons (<input type=’image’ alt=’TE’>) define appropriate contextual alternative text.

JavaScript Submitted Forms

1. Scan source code or use a tool that can isolate and expose the attributes of elements.

Verify that a real URI and not JavaScript has been defined to accept form submissions e.g. <form action=’Real URI not Javascript:function’ >

Test Results

1. Determine that the page contains a ‘Skip To main Content’ as the first link on the page (first repeating link for a page within a site with repetitive links )

2. Determine that every ‘site-repeating’ link can be effectively skipped.

Affected HTML Elements (and attributes)

<a>, <area>

Testing Procedure

Manual Test:

1. Scan source code or use a tool that can isolate the <a>, and <area> elements on the page.

2. Verify that the first link (first repeating link for a page within a site with repetitive links ) links to the main page content. The link should be of the form <a href=’#BeginMainContent’>Skip to main content</a> where BeginMainContent is defined as a named anchor or a valid unique id of an element. For example <a name=’ BeginMainContent’></a> or <div id=’ BeginMainContent’></div>

3. Verify that other repetitive navigation links can be effectively skipped using the method above.

1. Determine that the page does not automatically reload without warning the user and allowing the user to stop the reload.

2. Determine that the user is alerted and given sufficient time to indicate that more time is needed for any timed response.

Affected HTML Elements (and attributes)

<meta http-equiv=’refresh’>, <script>

Testing Procedure

Automatic Page Reload

Manual Test:

1. Scan source code or use a tool that can isolate the <meta> elements on the page.

2. Verify that none of the <meta> elements define the “http-equiv=’refresh’” property.

Timed Response

1. Examine the page for interactive objects that require a timed response.

2. Verify that before the page or the object times out, the user is given an option to request for more time.

3. Verify that user focus is returned to the object the user was on before the warning dialog box was displayed.

§ 1194.23 Telecommunications products

§ 1194.24 Video and multimedia products

§ 1194.25 Self contained, closed products