Re: UA Telecon for September 23rd at 12:00 EST

to follow up on what Mark Hakkinen said:

> >
> >How a user agent implements frames is less important than the authoring
> >issues.  From the UA point of view:
> >
> >1. Structure of frameset must be exposed (number of frames, etc).
> >2. Frames titles /longdesc need to be exposed to user
> >3. Navigation between frames needs to be supported
> >4. Determining where user is in a frameset must be easily determined
> >
> >Beyond that, the rest is authoring guidelines, in my mind.

What information does pwWebSpeak use to satisfy requirement
number 4?  It seems to me that the solutions for number 1
and 4 have to correspond, and that there is no precedent with
"specification" status that we can follow, here.

There is no defined URL syntax IIRC for where you are in a
frameset, including the fact that frames may have been
overwritten by prior link activations.

As with tables, perhaps some additional markup would help in
unrolling the web of possible frame-state combinations into a
hierarchical list.

For example, the top frame is typically a masthead and does not
change throughout all states of the frameset.  The bottom may
be another invariant frame.  The left sidebar is likely to change
infrequently and have a unique value for each state of the main
frame.  In that case there is a simple two-level hierarchical
list of the feasible states of the frameset:

Global properties across all states of the frameset:
	top frame URL
	[bottom frame URL]
Properties associated with the first level of decomposition
(outer sort):
	URL to left sidebar frame contents
Properties associated with the second level of decomposition
(inner sort):
	URL to contents of main frame.

If the frameset is programmed in this manner, then it can be
clearly described by a hierarchical table of contents [actually
states].

But the rules of framesets don't guarantee that simplicity AFAIK.

One would have to explore the state space by exercising the
frameset to be sure of any structure assumed for the reachable
states.

Al

> >
> >Mark
> >
> >> -----Original Message-----
> >> From: w3c-wai-ua-request@w3.org [mailto:w3c-wai-ua-request@w3.org]On
> >> Behalf Of Jon Gunderson
> >> Sent: Tuesday, September 22, 1998 12:44 PM
> >> To: w3c-wai-ua@w3.org
> >> Subject: UA Telecon for September 23rd at 12:00 EST
> >>
> >>
> >> WAI UA Telecon for September 23rd, 1998
> >>
> >> !! Note time and phone number !!
> >>
> >> Chair: Jon Gunderson
> >>
> >> Date: Wednesday, September 23rd
> >>
> >> Time:
> >> 12:00 EST
> >> 11:00 CST
> >> 10:00 MST
> >> 9:00 PST
> >>
> >> Call-in: (+1) 617/258-7910
> >>
> >> Agenda
> >>
> >> 12:00-12:30 Frames
> >>
> >> 12:30-1:00 Embedded applications and DHTML Scipting
> >>
> >> Jon Gunderson, Ph.D., ATP
> >> Coordinator of Assistive Communication and Information Technology
> >> 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.als.uiuc.edu/InfoTechAccess
> >>
> >>
> > 
> Jon Gunderson, Ph.D., ATP
> Coordinator of Assistive Communication and Information Technology
> 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.als.uiuc.edu/InfoTechAccess
>

Received on Wednesday, 23 September 1998 11:32:49 UTC