W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2008

RE: IFRAME Accessibility Inquiry

From: Evans, Donald <Donald.Evans@corp.aol.com>
Date: Wed, 18 Jun 2008 11:53:33 -0400
Message-ID: <03D07FA9A6F1344081610CF5B15598F201652AC6@EXCHNVA01.ad.office.aol.com>
To: "Schnabel, Stefan" <stefan.schnabel@sap.com>, "Gregory J. Rosmaita" <oedipus@hicom.net>, <w3c-wai-ua@w3.org>, <wai-xtech@w3.org>

It presents significant problems for us.  As an example we might attach
a JS keyboard handler to the parent page, but unless the same JS is
attached to the iFrame too the keyboard shortcuts are not recognized
when focus is in the iFrame.  Since many ads are delivered via iFrames
and developers of ads like to grab focus, it presents major problems.
As Stefan says, "it's a black hole".

  

> -----Original Message-----
> From: wai-xtech-request@w3.org 
> [mailto:wai-xtech-request@w3.org] On Behalf Of Schnabel, Stefan
> Sent: Wednesday, June 18, 2008 4:43 AM
> To: Gregory J. Rosmaita; w3c-wai-ua@w3.org; wai-xtech@w3.org
> Subject: RE: IFRAME Accessibility Inquiry 
> 
> 
> Thanks to raising this question, Greg.
> 
> IFrame is black hole regarding accessibility, any AJAX-based 
> framework that allows usage of IFRAMES as part of its control 
> set will inherit all issues you described.
> 
> Will/Can the new HTML5 properties (like sandbox etc.) maybe help here?
> 
> Best Regards
> Stefan
> 
> -----Original Message-----
> From: wai-xtech-request@w3.org 
> [mailto:wai-xtech-request@w3.org] On Behalf Of Gregory J. Rosmaita
> Sent: Mittwoch, 18. Juni 2008 10:11
> To: w3c-wai-ua@w3.org; wai-xtech@w3.org
> Subject: IFRAME Accessibility Inquiry 
> 
> 
> what is the current state of accessibility of IFRAME?  what 
> are the outstanding accessibility problems inherit to IFRAME, 
> or have they been mitigated?
> 
> if, for example, one has a document embedded in an IFRAME 
> which has access keys defined for it, will the embedded 
> document's UI controls take precedence when the focus is in 
> the IFRAME?  what about conflicts between embedded UI 
> controls and UI controls in host documents?  what if a 
> tabindex value has been defined for the IFRAME, and the 
> document in the IFRAME has its own tabindex order?
> 
> the basic question is: how do the 2 documents interact and 
> what can we do to standardize this interaction?  can we 
> harmonize our efforts with OpenAjax's support for iFrames?
> 
> so, what are the problems with IFRAME today?  here is a very 
> rough thumbnail:
> 
> 1. tension between global and scopeable UI controls (accesskey, 
>    tabindex, etc.)
> 
> 2. horizontal and vertical scrolling impose an undue burden for 
>    several user groups;
> 
> 3. one can't resize an IFRAME; one can only use the UA's scaling 
>    mechanism, which is crude/gross at best;
> 
> 4. ARIA will help with IFRAME accessibility, yes, but what is still 
>    lacking in non-ARIA enabled technology, to support IFRAME 
>    accessibly?
> 
> References:
> IFRAME in HTML4.01/XHTML1.0:
>   http://www.w3.org/TR/html401/present/frames.html#edef-IFRAME
> 
> IFRAME in OpenAjax: 
> http://www.openajax.org/member/wiki/OpenAjax_Hub_1.1_Roadmap#L
> everaging_
> IFRAMEs_for_mashup_security
> 
> thank you, gregory
> ----------------------------------------------------------------
> CONSERVATIVE, n.  A statesman who is enamored of existing 
> evils, as distinguished from the Liberal, who wishes to replace them 
> with others.         -- Ambrose Bierce, _The Devil's Dictionary_
> ----------------------------------------------------------------
>              Gregory J. Rosmaita, oedipus@hicom.net
>   Camera Obscura: http://www.hicom.net/~oedipus/index.html
> ----------------------------------------------------------------
> 
> 
> 
> 
Received on Wednesday, 18 June 2008 15:56:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:57 GMT