- From: Marc Haunschild <mh@zadi.de>
- Date: Mon, 11 Aug 2014 10:34:14 +0200
- To: w3c-wai-ig@w3.org
This helps a lot, thx Ramón! Am 09.08.14 20:47, schrieb Ramón Corominas: > 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. > > Regards, > Ramón. > > 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. > > -- Mit freundlichen Grüßen, i. A. Marc Haunschild Zugängliche Anwendungsentwicklung und Qualitätskontrolle ________________________________________ Referat 414 / Abteilung 4 Bundesanstalt für Landwirtschaft und Ernährung Deichmanns Aue 29, 53179 Bonn Telefon: +49 (0)228 996845-7324 Fax: +49 (0)228 6845-3101 E-Mail: marc.haunschild@ble.de Internet: www.ble.de ( http://www.ble.de/ )
Received on Monday, 11 August 2014 08:34:47 UTC