Description Eddie 2003-05-09 10:10:44 EDT

When the user presses Ctrl-E in Home Page Reader a list of frames is displayed. 
Frames are either Internal or external.
Some of the internal frames clearly belong to the Help system, but some are 
empty according to HPR. The problem is that the frame titles do not all 
correspond to the expected frame. Several "internal" frames are untitled. These 
belong to the Eclipse help infrastructure. For example HPR detects a frame 
surrounding the back, forward, show in TOC, bookmark and print buttons in the 
top right. However this frame is untitled, 
so a visually impaired user cannot tell easily what the frame contains without 
changing to it and having its contents read out.

This sounds as if the problem is with the Eclipse Help System and the way in 
which it names frames.


The Web checklist (http://w3.austin.ibm.com/~snsinfo/webcheck.html), item 9 
states: 
"There are two parts to the technique for providing accessible frame 
navigation. First, meaningful titles should be included on the source page for 
each frame by using the TITLE element. The second part of the solution is to 
assign a meaningful name attribute and title attribute for each FRAME element 
on the FRAMESET page. "

It also states: 

"The source of the FRAME element should always be an HTML file. If the source 
of a FRAME is an image file (such as, logo.gif), there is no opportunity to add 
the alt attribute. Therefore, the source of the frame is inaccessible. " 


Bob Waller, the Java Technology center's Accessibility man will help us to put 
together some words to explain these accessbility limitations. Also, he will 
bring this up at the next cross-site accessibility meeting.