[Accessibleweb] iframe

[R. Benson]

I wondered about this as well. I know that if you load a page with a 
frameset, you are given the source with the frame declaration. However if 
you click or give focus to any element, you are given the source to that 
frame. I haven't figured out a way to bounce back up to that top level 
once you are inside a frame. I wonder if there is a way to give a screen 
reader a hook to climb up to the top level then hop to the frame.

--
Ryan E. Benson
Department of Political Science
Access Technology Lab Consultant
rbenson at u.washington.edu

On Wed, 21 Apr 2010, Wendy Chisholm wrote:


> Terry,

> 

> That's a really good question. Content in iframes and frames is not part of

> the primary document's DOM--each frame has its own document object and thus

> it's "own" DOM. I've struggled with this quite a lot while working on

> WebAnywhere. Here's one of my primary test

> cases: http://sp1ral.com/tests/iframe-simplified.html

> If I want to count the number of headings using getElementsByTagName I need

> to query each document object separately. 

> 

> Also, if an iframe has focus and an event is fired (a keyboard event is most

> common in WebAnywhere) the event doesn't seem to bubble up to the top object

> listeners that handle the event--although this is something I'm still

> working to debug. It looks like each iframe should have event listeners that

> specifically hand off the events to the top document--we need to do that in

> WebAnywhere so that we can intercept events before they go to the browser

> (currently if an iframe has focus and a WebAnywhere keyboard command is

> issued, e.g., control l which should move focus to the location field within

> WebAnywhere, the browser gets the event and moves focus to the browser's

> location text field.)

> 

> Therefore, I suspect that events fired within an iframe will not communicate

> across document object boundaries. Part of this is related to the point of

> origin policy which I don't totally understand.

> 

> I've cc'ed Michael Cooper who is the W3C staff contact for the group working

> on the ARIA specification. Michael, thoughts?

> 

> Thanks,

> --wendy

> 

> On Apr 21, 2010, at 10:19 AM, Terrill Thompson wrote:

>

>       I'm not seeing the iframe on that page Dylan, but as you noted

>       frames/iframes are acceptable as long as they have a title

>       attribute. This is specifically addressed within the WCAG 2.0

>       Techniques documents: 

> 

> http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/html.html#H64

> 

> Your mention of ARIA in this same email though has me wondering

> whether ARIA works across frames. For example, if a user clicks on

> something in Frame A that results in a change to Frame B, does ARIA

> allow that change to be communicated to the user in the same way it

> does if the content were on the same page? I suspect the answer is

> Yes, since the content from the various frames is all loaded into the

> DOM, but I don't know that for sure. Something to ponder, or maybe

> just something to avoid. 

> 

> Terrill Thompson

> Technology Accessibility Specialist

> DO-IT, UW Accessible Technology

> UW Information Technology

> University of Washington

> tft at uw.edu | 206/221-4168

> 

> 

> 

> -----Original Message-----

> From: accessibleweb-bounces at mailman2.u.washington.edu

> [mailto:accessibleweb-bounces at mailman2.u.washington.edu] On Behalf Of

> Dylan Wilbanks

> Sent: Tuesday, April 20, 2010 1:16 PM

> To: 'UW Web Accessibility Group'

> Subject: [Accessibleweb] iframe

> 

> Someone asked me about whether this OSP page is really compliant with

> WCAG. 

> https://www.washington.edu/research/main.php?page=ospFaq

> 

> The question was about iframe, but I seem to recall that iframe is

> allowed

> under WCAG 1.0 so long as they're done correctly and there's a title

> tag and

> meaning associated with it. But given that I've avoided frames as much

> as

> possible all these years, I'm the wrong person to answer this

> question.

> 

> What is the state of play with iframe accessibility? Is the method OSP

> seems

> to be using compliant? I'm not seeing any ARIA tags straightaway on

> the

> jQuery-esque popup.

> 

> dw

> 

> Dylan Wilbanks

> Web Producer

> School of Public Health

> University of Washington

> F-350 Health Sciences Bldg

> 1959 NE Pacific St

> Box 357230

> Seattle, WA 98195-7230

> V: 206.221.6395

> F: 206.543.3813

> E: wilbanks at u.washington.edu 

> 

> 

> _______________________________________________

> Accessibleweb mailing list

> Accessibleweb at u.washington.edu

> http://mailman2.u.washington.edu/mailman/listinfo/accessibleweb

> _______________________________________________

> Accessibleweb mailing list

> Accessibleweb at u.washington.edu

> http://mailman2.u.washington.edu/mailman/listinfo/accessibleweb

> 

> 

> --

> Wendy Chisholm

> Universal Design Evangelist

> http://sp1ral.com/about

> http://staff.washington.edu/chiswa

> twitter: wendyabc

> 

> 

> 

> 

> 

> 

> 

>