W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 1999

Re: Techniques for 3.3.6 Orientation to Frames

From: Jon Gunderson <jongund@staff.uiuc.edu>
Date: Wed, 06 Oct 1999 17:02:10 -0700
Message-Id: <4.1.19991006170149.00b65640@staff.uiuc.edu>
To: Charles McCathieNevile <charles@w3.org>
Cc: w3c-wai-ua@w3.org, ij@w3.org
When will you have it ready?
Jon


At 02:16 PM 10/5/99 -0400, Charles McCathieNevile wrote:
>It would make a lot more sense to give a sound file as the demonstration for
>Home Page Reader (with a synchronised transcript), and to include the lynx
>output as text instead of an image.
>
>Charles McCN
>
>On Tue, 5 Oct 1999, Jon Gunderson wrote:
>
>  3.6.6 Frames
>  
>  Frames were originally designed for use by graphical user interfaces to
allow
>  the graphical view to be broken up into independently controllable views of
>  documents on the same page.  Actions in one frame can change the contents of
>  another set of frames in a frame set.  For people who use speech,
refreshable
>  Braille and magnified views need to have access to the frame information.  
>  
>  Users need to know:
>  a. Are frames present in the document?
>  b. If there are frames, how many?
>  c. What (if any) descriptive information is available about the frame?
>  d. Which frame has the current programmatic focus?
>  
>  This information should be available through the DOM and appropriate
>  accessibility interfaces.  Using DOM and operating specific accessibility
API
>  to expose frame information provides one means for assistive technologies to
>  provide alterantive control of frames and rendering of frame information.
The
>  user agent should fully implement the DOM level 1 recommendations related to
>  FRAME elements, including:
>  
>  HTMLFrameSetElement 
>  http://www.w3.org/TR/REC-DOM-Level-1/level-one-html.html#ID-43829095
>  
>  HTMLFrameElement
>  http://www.w3.org/TR/REC-DOM-Level-1/level-one-html.html#ID-98869594
>  
>  HTMLIFrameElement 
>  http://www.w3.org/TR/REC-DOM-Level-1/level-one-html.html#ID-50708718
>  
>  For people with visual impairments who are enlarging fonts on the screen to
>  improve readability, frames become distorted and unusable.  Other users with
>  cognitive disabilities sometimes become disoriented when frames are rendered
>  simultaneously.  To improve access to frames user agents should allow 
>frames to
>  be viewed as a list so the user can identify the number of frames and the
>  functions of each frame.   If no frames information is present it should
also
>  be rendered so the user can optionally use that view of the information.
>  
>  The following HTML code is used to illustrate accessible frames:
>  > > > CONTENT="Microsoft Internet Assistant for PowerPoint 97"> > > > > > >
> buttons" > TITLE="Size buttons"> > NAME="Presentation > Outline"
TITLE="Presentation Outline"> > > > > buttons" TITLE="Navigation buttons"> >
Image" > TITLE="Slide Image"> > > > > > > > > 

List of Presentation Slides
> 
> 
    * <slide001.htm>Time Value of Money  
    * > > 
    * <slide002.htm>Topic Overview  
    * > > 
    * <slide003.htm>Terms and Short Hand >  
    * > > 
    * <slide004.htm>Future Value of a Single CF >  
    * > > 
    * <slide005.htm>Example 1: FV example:The > NBA’s new Larry Bird
exception  
    * > > 
    * <slide006.htm>FV Example: NBA’s Larry > Bird Exception (cont.)  
    * > > 
    * <slide007.htm>SuperStar’s Contract > Breakdown  
    * > > 
    * <slide008.htm>Present Value of a Single > Cash Flow  
    * > > 
    * <slide009.htm>Example 2: Paying Jr, and > A-Rod  
    * > > 
    * <slide010.htm>Example 3: Finding Rate of > Return or Interest Rate  
    * > > 
    * <slide011.htm>Annuities  
    * > > 
    * <slide012.htm>FV of Annuities  
    * > > 
    * <slide013.htm>PV of Annuities  
    * > > 
    * <slide014.htm>Example 4: Invest Early in > an IRA  
    * > > 
    * <slide015.htm>Example 4 Solution  
    * > > 
    * <slide016.htm>Example 5: Lotto Fever >  
    * > > 
    * <slide017.htm>Uneven Cash Flows: Example > 6:Fun with the CF function  
    * > > 
    * <slide018.htm>Example 6 CF worksheet > inputs  
    * > > 
    * <slide019.htm>CF inputs continued >  
    * > > 
    * <slide020.htm>Non-Annual Interest > Compounding  
    * > > 
    * <slide021.htm>Example 7: What rate are > you really paying?  
    * > > 
    * <slide022.htm>Nominal to EAR Calculator >  
    * > > 
    * <slide023.htm>Continuous Interest > Compounding  
    * > > 
    * <slide024.htm>FV and PV with non-annual > interest compounding  
    * > > 
    * <slide025.htm>Non-annual annuities >  
    * > > 
    * <slide026.htm>Example 8: Finding Monthly > Mortgage Payment  
    * > > 
    * <slide027.htm>solution to Example 8 >  
    * > > 
> > > > 
>  
>  This following is a rendering of this code using Microsoft Internet Explorer
>  5.0
>  
>  **** insert image: finance-frame-explorer.gif ****
>  ALT=”Image shows a web page with five frame panes in Microsoft Internet
>  Explorer”
>  
>  A configuration option in the user agent could allow the user to render the
>  information as a list of links.  The following two examples indicate how
Lynx
>  and IBM Home Page reader render frame sets.  The TITLE (NAME can be used it
>  TITLE is missing) attributes are used to label each of the frames.  The
>  NOFRAMES information is rendered after the links to the frames.
>  
>  *** insert image: finance-frame-lynx.gif ****
>  ALT=”Image shows a web page with five links for each of the frame elements
in
>  the lynx browser”
>  
>  *** insert image: finance-frame-hpr.gif  ****
>  ALT=”Image shows a web page with five links for each of the frame elements
in
>  IBM home page reader”
>  
>  Another way to indicate the number of frames in a document and which frame 
>has
>  the focus is to use the menu bar or popup menus.  Users can configure the 
>user
>  agent to include a FRAMES menu item in their menu bar.  The use of the 
>menu bar
>  makes the information highly visible to all users and is very accessible to
>  assistive technologies.  In the following example the menu bar indicates the
>  number of frames and a check next to the name of the frame element indicates
>  which frame has the current focus.
>  
>  *** insert image: finance-frame-awb.gif ****
>  
>  ALT=”Image shows a pull down menu indicating the number of frames in a
>  document, the labels associated with each frame and a check mark to indicate
>  the frame with the current focus ”
>  
>
>--Charles McCathieNevile            mailto:charles@w3.org
>phone: +1 617 258 0992   http://www.w3.org/People/Charles
>W3C Web Accessibility Initiative    http://www.w3.org/WAI
>MIT/LCS  -  545 Technology sq., Cambridge MA, 02139,  USA

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Chair, W3C WAI User Agent Working Group
Division of Rehabilitation - Education Services
University of Illinois at Urbana/Champaign
1207 S. Oak Street
Champaign, IL 61820

Voice: 217-244-5870
Fax: 217-333-0248
E-mail: jongund@uiuc.edu
WWW:	http://www.staff.uiuc.edu/~jongund
		http://www.w3.org/wai/ua
		http://www.als.uiuc.edu/InfoTechAccess
Received on Wednesday, 6 October 1999 17:57:37 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:24 UTC