Outdated Content!
The Protocols and Formats Working Group is no longer chartered to operate. Its work will continue in two new Working Groups:
- https://www.w3.org/WAI/APA/ 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
- https://www.w3.org/WAI/ARIA/ 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.
Resources from the PFWG remain available to support long-term institutional memory, but this information is of historical value only.
This Wiki page was edited by participants of the Protocols and Formats Working Group. 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. It may also have some very useful information.
IFRAME
IFRAME Accessibility Inquiry
Contents
The Web Accessibility Initiative, and the accessibility comunity at large, has been asked:
- 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
IFRAMEwhich has access keys defined for it, will the embedded document's UI controls take precedence when the focus is in theIFRAME? what about conflicts between embedded UI controls and UI controls in host documents? what if a tabindex value has been defined for theIFRAME, and the document in theIFRAMEhas its own tabindex order?
- if, for example, one has a document embedded in an
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
What precisely are the problems with IFRAME today? here is a very rough thumbnail:
- tension between global and scopeable UI controls (
accesskey,tabindex, etc.) - horizontal and vertical scrolling impose an undue burden for several user groups;
- one can't resize an
IFRAME; one can only use the User Agent's scaling mechanism, which is crude/gross at best; - ARIA will help with
IFRAMEaccessibility, yes, but what is still lacking in non-ARIA enabled technology, to supportIFRAMEaccessibly?
Providing Feedback
Since this is a read-only wiki for those who do not belong to the Protocols & Formats Working Group, please send all comments to wai-xtech@w3.org. (wai-xtech@w3.org is a publicly archived mailing list. Please use the keyword "[iframe]" in the Subject line of your emessage.
References
Definitions of IFRAME
IFRAME in HTML
-
IFRAMEin HTML4.01 -
IFRAMEin HTML5- sandboxing attribute (new)
- seamless attribute (new)
- note: the
longdescattribute for anIFRAMEhas been dropped from HTML5- reasons to support restoration of
longdescforIFRAME:- easiest rendering solution solution for UAs that do not support
IFRAMEor have support forIFRAMEswitched off- note: suppressing
IFRAMEis still, as of 2010, a regular option offered by most assistive technologies;
- note: suppressing
- easiest work-around to having to build an
IFRAMEDOM subtree for the content of theIFRAME;
- easiest rendering solution solution for UAs that do not support
- reasons to support restoration of
note: bugs are listed in numeric order by bugID number.
- Define tab order for IFrame (8647)
- Title attribute on the IFrame element (Bug 8648)
- Resize IFrame (Bug 8649)
Other Manifestations of IFRAME
- XHTML IFrame Module
- note: does this document have a maintainer working group? should PF and (your suggestions here) develop one?
- question: what is the TAG's opinion of IFrame, as a module and a concept, and what is their processing model for
IFRAME?
-
IFRAMEin OpenAjax
Accessibility Documentation on the Use of IFRAME
-
IFRAMEin Web Content Accessibility Guidelines, Level 1 (WCAG 1.0) -
IFRAMEin Web Content Accessibility Guidelines, Level 2 (WCAG 2.0)