Test Case Description for Scripts
Purpose:- Verify the functionality of scripts is keyboard accessible.
- If the content affected by scripting is not accessible, provide an
alternative.
Initial Conditions:
- Have Screen Reader program installed.
Steps/Description:
Verify
|
Steps and Description
|
Results
|
Script functionality is
keyboard accessible |
Test the following pages with Screen Reader to see
if your script is accessible with the keyboard. page1 page2 |
If the script is keyboard accessible, you will be
able to activate the script on the page using only the keyboard keys. |
Test the following pages with Netscape Browser using
only the keyboard (no mouse) to test the functionality of the site.
page1 page2 |
If the script is keyboard accessible, you will be
able to activate the script on the page using only the keyboard (tab and
enter) keys. |
|
Content affected by scripts
are available to assistive technology |
||
Test the page3 with a combination of browser and the assistive technology. | All the important content is still available to
assistive technology, for example spoken by the screen reader. |
|
Alternatives to essential scripts that are not keyboard
accessible or that affect content such that it is not accessible. |
Test page4
in a browser that does not support scripts or in a browser with
support for scripts disabled: From Netscape Browser: 1. Click Edit | Preferences. 2. Click Advanced, and then clear the options to enable JavaScript. |
If the NOSCRIPT element was used, the equivalent
alternative content is rendered. |
HTML Source Code:
Page1:
<button onfocus="alert('You focused on the the button by keyboard and as a result, this dialog box was generated')">
click this Button</button>
Page2:
<a href="success.html" onkeypress="window.alert ('Key was pressed!')" onclick="window.alert ('Clicked!')">
Page3:
<img src="../images/convert.gif" alt="char to unicode" width="200" height="40" onclick="toUnicode()">
Page4:
<noscript> <A HREF="http://www.mozilla.org">Home Page of Mozilla Org</a> </noscript>