Frames possess inherent problems for accessibility. Fundamentally, it is difficult to restyle content within frames since even simple restyling, such as increasing text size, often results in clipping or the need for horizontal scrolling. Titling of frames by authors (when done at all) is usually so ambiguous that it remains difficult for speech users to know the potential contents of a frame. It is also difficult for speech users what the potential changes will occur to all frames when they select a link in one particular frame. In general, most web developers appear to be staying clear of frame-based content, a trend that supports accessibility.

The one notable exception to this trend is with web application developers who use “hidden” frames to setup server/browser communications. These communications can include information about user interactions and/or automatic notifications of new information that might be useful to the user. One of the major problems with the use of hidden frames for automation is that it is often confusing to screen reader users. If the screen reader interprets the automation activity as new information to the user, it can cause weird screen reader behaviors which lead to screen reader users being unable to access the content of a web resource.

Benefits to People with Disabilities

  1. Titling frames helps screen readers navigate the content of a website.
  2. Frames typically cause problems for screen reader users when they are used to dynamically update web pages. When content changes dynamically, the screen reader may abruptly change focus to the beginning of a document. This is very disorienting to screen reader users.

Benefits to Everyone

  1. Frames cause problmes for all users since the back button does not reliably return the user to the previous content of frames.

Benefits to Developers

  1. Frames may be convenient to the developers, but cause many problems for users and sometimes increase development and maintenance cost of website due to the complexities of frame content interaction.

More Information

  1. W3C WCAG 1.0 frame techniques
  2. 18: HTML links – Frames and Popups (Opera Web Standards Curriculum)


iframe[title] (HTML4)

frame[title] (HTML4)

Related Accessibility Requirements

Section 508

Illinois Information Technology Accessibility Standards

Web Content Accessibility Guidelines (WCAG) 2.0

Web Content Accessibility Guidelines (WCAG) 1.0