Frames

On bulletin boards and forums related to Web development, many of the posts concern problems with frames. Another developer once told us that the reason there are so many reports of problems with frames is that professionals avoid using frames and the amateurs who use them don't know how to use them correctly. What is clear is that the use of frames causes problems for many people -- both developers and visitors.

There are many arguments against the use of frames, but there may be times when it makes sense to use frames. Here is a good rule to follow: use frames only if they fill a purpose that can't be addressed adequately by other methods. If you feel you must use frames, here are some guidelines that originally appeared on about.com which should help you make your framed site accessible:

1. Use minimal frames.
Technology is getting better, and screen readers that used to be unable to read frames can now read some sites with frames, but only if there are just a few frames. Two is best - three if absolutely necessary.

2. Keep navigation in every frame.
Make sure that site navigation (e.g., a navigation menu, navbar, or site map) is included in every frame. That way, even if visitors are not using the frames, they can still get around the site.

3. Always use the noframes tag.
If you must use a framed design, be sure to use the noframes tag. The easiest way to create a noframes page is to use a link to the actual content of your page - usually the main frame. It means that visitors with disabilities will have to click one more time, but at least they can read the content. Of course, the optimal solution is to reproduce the content in the noframes page, so that they have it right there.

---