Access to Content Contained in an Inline Frame (IFRAME)

What Is Being Tested?

This page contains an inline frame (IFRAME), which is used to embed another XHTML document into this document. If you are using a graphical browser, the inline frame should be scrollable. If you are using a frames-incapable browser (such as Lynx or NetTamer) or have support for frames turned off, you should still be able to review the content contained in the IFRAME, either inline (that is, in the body of this document), or by following a link.

This document is part of a suite of pages designed to test the implementation of the W3C's User Agent Accessibility Guidelines (UAAG). In particular, this page is designed to test implementation of UAAG checkpoints 2.1 and 9.1. Note that the actual text of these checkpoints is contained in the inline frame defined for this page.

How to Provide Feedback

Please send comments and observations about this test page to <w3c-wai-ua@w3.org>. Your comments will be archived in the mailing list's public hypertext archive. Please make your observations as specific and detailed as possible. Be sure to include the following information when you report your observations to the User Agent Accessibility Guidelines Working Group:

operating system (including version/revision number)
assistive technology, if any (please include version number)
user agent name and version (i.e. MSIE, version 5.00.2920.0000 update versions ;q254902)
any special settings (i.e. any changes you or your adaptive equipment made to your user agent's default configuration)
were you able to access the content contained in the inline frame?
how did your browser render the content of the IFRAME? Was the checkpoint text contained in a scrollable sub-window, or was it displayed inline (i.e., as if the content obtained from the source of the IFRAME is part of this document?)
were you able to expose the content of the inline frame in a new viewport (e.g. in a new "window")? if so, how? Please be as specific as possible, listing all keystrokes, mouse clicks, etc.

<dl class="checkpoint"> <dt class="checkpoint"><span class="checkpoint"><a id="tech-doc-content-access" name="tech-doc-content-access">2.1</a></span> For all format specifications that the user agent <a href="http://www.w3.org/TR/UAAG10/#def-implement" rel="glossary" title="Definition of implement"><span class="dfn-instance"> implements</span></a>, make <a href="http://www.w3.org/TR/UAAG10/#def-content" rel="glossary" title="Definition of Content"><span class="dfn-instance">content</span></a> available through the rendering processes described by those specifications. <span class="priority1">[Priority&nbsp;1]</span> Content only.</dt> <dd class="checkpoint"><strong>Note:</strong> This includes format-defined interactions between author preferences and user preferences/capabilities (e.g., when to render the "<code>alt</code>" <a href="http://www.w3.org/TR/UAAG10/#def-attribute" rel="glossary" title="Definition of Attribute"><span class="dfn-instance"> attribute</span></a> in HTML <cite><a href="http://www.w3.org/TR/UAAG10/#ref-HTML4" title="Link to reference HTML4">[HTML4]</a></cite>, the rendering order of nested <code>OBJECT</code> elements in HTML, test attributes in SMIL <cite><a href="http://www.w3.org/TR/UAAG10/#ref-SMIL" title="Link to reference SMIL">[SMIL]</a></cite>, and the cascade in CSS2 <cite><a href="http://www.w3.org/TR/UAAG10/#ref-CSS2" title="Link to reference CSS2"> [CSS2]</a></cite>). If a conforming user agent does not render a content type, it should allow the user to choose a way to handle that content (e.g., by launching another application, by saving it to disk, etc.). This checkpoint does not require that all content be available through each <a href="http://www.w3.org/TR/UAAG10/#def-viewport" rel="glossary" title="Definition of viewports"><span class="dfn-instance">viewport</span></a>.</dd> <dd><span class="noprint"><a href="http://www.w3.org/WAI/UA/UAAG10-TECHS/guidelines.html#tech-doc-content-access"> Techniques for checkpoint 2.1</a></span></dd> <dt class="checkpoint"><span class="checkpoint"><a id="tech-nav-viewports" name="tech-nav-viewports">9.1</a></span> Allow the user to make the <a href="http://www.w3.org/TR/UAAG10/#def-selection" rel="glossary" title="Definition of Selection"><span class="dfn-instance">selection</span></a> and <a href="http://www.w3.org/TR/UAAG10/#def-focus" rel="glossary" title="Definition of Focus"><span class="dfn-instance"> focus</span></a> of each <a href="http://www.w3.org/TR/UAAG10/#def-viewport" rel="glossary" title="Definition of viewports"><span class="dfn-instance">viewport</span></a> (including frames) the <a href="http://www.w3.org/TR/UAAG10/#def-current-selection" rel="glossary" title="Definition of current selection"><span class="dfn-instance">current selection</span></a> and <a href="http://www.w3.org/TR/UAAG10/#def-current-focus" rel="glossary" title="Definition of current focus"><span class="dfn-instance">current focus</span></a>, respectively. <span class="priority1"> [Priority&nbsp;1]</span> User agent only.</dt> <dd class="checkpoint"><strong>Note:</strong> For example, when all frames of a frameset are displayed side-by-side, allow the user (via the keyboard) to move the <a href="http://www.w3.org/TR/UAAG10/#def-focus" rel="glossary" title="Definition of Focus"><span class="dfn-instance">focus</span></a> among them.</dd> <dd><span class="noprint"><a href="http://www.w3.org/WAI/UA/UAAG10-TECHS/guidelines.html#tech-nav-viewports"> Techniques for checkpoint 9.1</a></span></dd> </dl>

Terminal Index: 1) Return to the User Agent Test Suite's Index; 2) User Agent Accessibility Guidelines Working Group (UAWG); 3) send comments and observations to w3c-wai-ua@w3.org

Copyright © 2001 W3C (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.