Understanding HTML, however, is critical to understanding other languages, and will contain most of the information that the web browser and screen reader will communicate to each other. The following is a list of HTML elements that some accessibility tools deem inappropriate for an accessible web page. Each of these elements will be looked at in detail, in relation to design and screen readers, to examine the possibility of conflict, and to see if solutions are available. Because GW Micro is conducting this presentation, the screen reader of choice will be Window-Eyes. All information regarding web page access will be drawn upon the features of Window-Eyes.
Frames can be very beneficial for grouping related content on a web page.
Frames require a document source by default. The document source is the URL to an HTML document. Although web designers can do their part by adding a NAME element to a frame, screen reader manufacturers are able to take this one step further. For example, Window-Eyes will read the title given to an HTML document that is loading into a given frame as the name of the frame, providing the user with a dynamic title every time a new page is loaded into that frame. If neither a frame name nor an HTML document title is given, then Window-Eyes will announce untitled as the frame name.