W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2014

Re: iframes

From: Ramón Corominas <listas@ramoncorominas.com>
Date: Sat, 09 Aug 2014 20:47:26 +0200
Message-ID: <53E66CBE.4080009@ramoncorominas.com>
To: Marc Haunschild <mh@zadi.de>
CC: w3c-wai-ig@w3.org
Hello, Marc.

In relity, the iframe and its contents are read like any other content 
in the page, for example, content within a <div>. The only difference is 
that the user can browse to the iframe (for example, using the "M" key 
in JAWS), and the title of the iframe is announced when the user 
navigates to it. If the user reads the content with the up/down arrow 
keys, the iframe start and end are announced using the title, something 
like "My title frame, inline frame" (I'm using the Spanish version so I 
don't know the exact words it uses in English).

So, you only have to ensure that the contents of the iframe follow the 
main structure (for example, start with <h2> to follow the <h1> in the 
container page and so on). Of course, this applies to any other content 
that you could put inside the iframe.


Marc wrote:

> I already got some answers - thnak you. But I think I have to add one thing to my initial post: I know that iframes are allowed. They can be used in screenreaders. But there have been some inconveniences anyway.
> For example a screenreader tells you how many headers a page includes - except the headlines in the iframe. This I found in posts older than 5 years. So I wonder if this still is a problem - or not.
Received on Saturday, 9 August 2014 18:47:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:52 UTC