Display the text of the code used for both frame pages.
On almost any list of pet peeves with the World Wide Web, the use of frames in web sites usually ranks very near the top. In addition to being confusing to less experienced web visitors and merely annoying to the more experienced, they pose some unique problems in and of themselves.
You can't link to anything other than the main (parent) frame. This means if you select content that is displayed in a subordinate (child) frame, the link will still bring you to the parent frame.
Many programmers don't use relative measurements in setting up frames. This means that if you use a monitor with 640X480 resolution and the programmer has specified that the left-side frame will be 100 pixels, the content may be cut off or you may be required to scroll left-to-right to see it all.
This original page is an mockup of an old frame site I did circa 1995. Now take a look at the result when Lynxview renders this page. As you can see, the Lynxview version gives the user virtually nothing to work with. This is also what many screen reader users will see as well. Finally, take a look at the Bobby report for this page. As you can see, it fails to meet the Priority 1 checkpoint for titling frames, and consequently cannot be considered to be an accessible page.
The improved version of the original page looks exactly the same in your browser. However, the NAME element content has been modified to be more descriptive, and a TITLE element was also added. You can see the difference in the the Lynxview version and the Bobby report for this page, which now achieves Priority 1 compliance status.