tension between global and scopeable UI controls ( accesskey, tabindex, etc.).What precisely are the problems with IFRAME today? here is a very rough thumbnail: The basic question is: How do the two documents interact and what can be done to standardize this interaction? Is it possible to harmonize W3C's efforts on IFRAME reform consult, for example, the definitions of IFRAME in XHTML2 (a subject which was revisited after having been dropped), the XHTML IFRAME Module and the XHTML Legacy Module with IFRAME in HTML5 as well as with OpenAjax's support for iFrames What Needs to Be Documented/Corraborated 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?.What are the outstanding accessibility problems inherit to IFRAME, or have they been mitigated?.What is the current state of accessibility of IFRAME?.The Web Accessibility Initiative, and the accessibility comunity at large, has been asked: 1.2.2 Accessibility Documentation on the Use of IFRAME.1.1 What Needs to Be Documented/Corraborated.It may also have some very useful information. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. This Wiki page was edited by participants of the Protocols and Formats Working Group. Resources from the PFWG remain available to support long-term institutional memory, but this information is of historical value only. Accessible Rich Internet Applications, to continue development of the Accessible Rich Internet Applications (WAI-ARIA) suite of technologies and other technical specifications when needed to bridge known gaps.Accessible Platform Architectures, to review specifications, develop technical support materials, collaborate with other Working Groups on technology accessibility, and coordinate harmonized accessibility strategies within W3C and.Its work will continue in two new Working Groups: The Protocols and Formats Working Group is no longer chartered to operate.