Jedadiah Ashford
3/8/2008
Guideline 8. Ensure direct accessibility of embedded user interfaces.
 The point of this guideline is to provide alternatives to applets and scripts. This is important due to the nature of these applets and scripts. They cannot be accesses a lot of times by other assistive technologies like screen readers. But if we are to add applets and scripts, we need to make sure that they are built to work with assistive technologies. This seems like something that is not easy to do but there is a simple way, make sure the applets and scripts output text to the screen. This seems like a simple solution and doesn’t need lots of extra coding. As long as the information is outputted to the screen and there is a way to tab to the box that has text, the screen reader should read it. This should be tested before the technology is implemented on the webpage.
                This is priority 1 unless the information is non-important to the webpage. If the information in the applet does not affect the purpose of the site then this isn’t such a high priority. We just need to make sure that the information is provided to everyone through these applets can be accessible to all. As we follow these guidelines then we can provide more traffic to our websites and more people will buy and browse our products or services.