7119 2009-07-17 12:23:50 +0000 Find out how IE computes names and descriptions of frames/iframes and the documents inside them 2010-07-20 20:58:20 +0000 1 1 1 Unclassified ARIA Core AAM 1.0 PC Windows XP RESOLVED FIXED P1 normal --- 1 andi.snowweaver cyns dbolter aria-ua-impl oldest_to_newest 26004 0 andi.snowweaver 2009-07-17 12:23:50 +0000 27090 1 cyns 2009-09-11 20:22:50 +0000 in IE, <frame> and <iframe> elements aren't mapped to the accessibility tree by default. The document inside them is mapped, and is in the tab order. When you tab to framed content, focus goes to the <body> element of the contained page. The role of the <body> is 'pane' and the name comes from the <title>, just like in the main browser window. You can add <frame> and <iframe> to the accessibility tree just like any other element (using ARIA attributes or tabindex), in which case @title, @aria* and inner text would provide the name, like other elements. 27092 2 andi.snowweaver 2009-09-11 20:46:55 +0000 Related to bug # 7120 27408 3 dbolter 2009-09-21 16:54:28 +0000 (In reply to comment #1) > You can add <frame> and <iframe> to the accessibility tree just like any other > element (using ARIA attributes or tabindex), in which case @title, @aria* and > inner text would provide the name, like other elements. > Thanks. Can you give me an example of markup for this? Are the aria attributes on the <iframe> element, or on the <body> of the frame source? 31199 4 andi.snowweaver 2010-01-25 17:02:16 +0000 Reassigning to Cynthia to answer David's question. 32512 5 cyns 2010-02-23 00:07:08 +0000 <frame> and <iframe> elements are not accessible by default (meaning you wont see these specific elements in the accessibility tree). If they are made accessible (such as putting ARIA information on them), then they will get their accName like other MSHTML elements that are not usually accessible: 1. Label (ARIA can override this via aria-labeledby) 2. Title 3. innerText However, the BODY and FRAMESET elements are accessible by default and will return the page title as their name. I mention this because these are most likely the elements you will interact with on a page that has frames/iframes. the <frame> or <iframe> element itself cannot receive focus (by default) so it goes to the first child that can (body). 32865 6 dbolter 2010-03-09 15:40:14 +0000 Would be good to know the IE tree for each of the frames here: http://people.mozilla.com/~dbolter/frames/ 35193 7 andi.snowweaver 2010-04-21 19:37:00 +0000 Saving the old text on the container-foo paragraph: Computing container-foo on any node in a sub document: For container-live, container-atomic, container-relevant, and container-busy, inner nodes override outer nodes from within the same document, because the inner subtree is the more relevant context. However, outer documents override inner documents, because the outer document author may be different and may wish to define the context for a live iframe. Therefore: 1. Walk the entire parent chain including that from outer documents, collecting the properties from aria-live, aria-atomic, aria-relevant, and aria-busy into the container-[property] object attribute 2. If a node sets a given object attribute, set a state that does not allow that value to change that object attribute again within the document 3. When entering a parent document, refresh the state to again allow override of each of these object properties 35194 8 andi.snowweaver 2010-04-21 19:42:41 +0000 Modified 5.1. Documents, Handling frame and iframe elements per March 9th meeting minutes: http://www.w3.org/2010/03/09-aapi-minutes.html Changed terms: "outer document accessible" to "accessibility node for frame elements" "inner document accessible" to "accessibility node for contained documents" Deleted glossary terms for "outer document accessible" "inner document accessible" Modified paragraph on computing "container-" object attributes to indicate this is specific to IAccessible2 and ATK. Added mashup example scenario from meeting minutes. Needs review by David, then Cynthia. 35393 9 dbolter 2010-05-04 14:29:13 +0000 OK 36524 10 andi.snowweaver 2010-07-01 21:20:27 +0000 Cynthia, Please review section 5.1. If you are okay with it, I think we can close this bug. http://www.w3.org/WAI/PF/aria-implementation/#document-handling_frames 37026 11 andi.snowweaver 2010-07-20 20:58:20 +0000 Closing per meeting minutes from 8 June 2010 http://www.w3.org/2010/06/08-aapi-minutes.html