Test Case Description for Applets and Plug-ins
Purpose:- When an applet, plug-in or other non-HTML content requiring another
application is required to be present,
provide a link to an applet, plug-in or other application that is directly accessible, or - Provide alternate content for applets, plug-ins, or other applications which are not directly accessible.
Initial Conditions:
- Have Screen Reader program installed.
Steps and Description:
|
Verify
|
Steps and Descrition
|
Results
|
| Applet, plug-in is directly accessible |
Test the following pages that contain an applet,
or plug-in, with a browser and assistive technology that supports it. Use
only the keyboard to interact with the controls. page1 contains an applet page2 contains plug-in |
The user interface is operational with only
the keyboard and the content is available to assistive technologies. |
| Plug-in content and user interface is accessible |
Test the
page3
with Screen Reader. |
If a link to a supported file is available,
Screen Reader will launch it separately in an accessible player. The user
interface controls will be spoken and operable from the keyboard. |
| Applet, plug-in, or
object alternative is accessible |
Test page
that contain an applet or object in a browser that does not support
applets or objects or in a browser with support for these features disabled: From Netscape Browser: 1. Click Edit | Preferences. 2. Click Advanced, and then deselect Enable Java. |
If equivalent alternatives were added to the
page, they are rendered and are usable. |
| Test the
page
with a combination of browser and the assistive technology. |
If the applets, plug-ins, or object equivalent
alternatives were added to the page, they are rendered and are usable. |
HTML Source Code:
<applet name="line" code="MagicLine1.class" width="225" height="220" alt="this is the first applet.">
<param name="bgcolor" value="c0c0c0">
<param name="speed" value="3">
</applet>
