Date: Wednesday, October 14th
Time: 12:00 noon to1:00 pm Eastern Standard Time
Call-in: (+1) 617/258-7910
12:00-12:30 Terminology related to point of reguard, selection and focus
Chair: Jon Gunderson
Scribe: Ian Jacobs
Scott and Harvey: will review tables sections
Jim: will review multimedia stuff
Jon and Ian: Publish new format for guidelines
/* Are people coming to UA Technologies gathering (Nov 1-4 in San
Sig Chi and UA Science and Technology meetings?
Impromptu discussion of gesticular interfaces */
1) Discussion of terminology.
a) selection (cf. guidelines)
b) focus (cf. guidelines)
Is the selection?
Or does it include focus and selection?
Concern that an extra term will confuse users.
Ian: selection/focus don't occur often in this document, not worth adding another term.
Paul: What do you want to use p.o.r for? Jon: E.g., we talk about moving
selection around and moving focus around (e.g., sequential nav).
We could simplify. Focus has a specific meaning to developers.
Ian: Is the distinction useful?
Ian: Not enough places in the document where are discussing "point of regard" would be useful. Focus: a specific element that can receive focus. Selection: may encompass several elements, even not-continguous areas.
Conclusion: Leave as is for now and discuss on list.
2) DHTML See http://lists.w3.org/Archives/Public/w3c-wai-ua/1998OctDec/0056.html - Define what a DHTML element is.
Ian: I hoped to remove the term DHTML from the doc. - Part of DHTML that is not event driven - presentation is modified on the fly.
DD: Need a section in compatibility on support for DHTML. Problem: it's
not entirely based on W3C technologies. Several scripting languages
W3C doesn't use the name DHTML (HTML+CSS+DOM+scripting). Which DOM (Level 0 or Level 1)?
Either we discuss DHTML in the guidelines (even if not W3C-wide definition) or we remove the term. - Say HTML under control of scripts instead?
Ian: Yes, I want to refer to DHTML only parenthetically. Only refer to scripts in guidelines.
DD: Probably put reference to what we mean by DHTML in compat section. - Proposal to put in techniques document.
Jon: We need Page Authoring support as well. They have no reference to DHTML or events in their guidelines or techniques. About all we can do now is deal with events set explicitly on elements (and not event bubbling).
Ian: How is event bubbling specified?
/* Jon gives overview of event handling */
Proposal: Guidelines only deal with explicit events. DD: Really a page author guideline issue.
People should not be allowed to use programs to replace markup. Analogous to server-side image map: can't do anything in the UA in that case.
Marja: Most important elements are form controls and links. What happens at scripting level is less important.
Jon: Summary what key subjects are:
1) What events are associated? (Proposed: "on*" attributes).
2) Keyboard support to navigate to those elements
3) Emulation of events (keyboard emulation of mouse actions).
4) User is notified of changes to document (notably spawned windows).
4): How in the general case do you describe what happened? - This is the problem. E.g., floating menu moves depending on what you're doing. - Add component to browser: A narrative window. Tell authors to write scripts that send descriptions of changes to narrative window.
Jon: Use "title" attribute?
Ian: Overloading of "title" already...
Ian: Ask script author to provide description in script definition (static). - But dynamic approach also necessary.
Actions: Scott and Harvey will review tables sections Jim will review multimedia stuff
Next telecon: 28 October
Face-to-face 25-26 October
- Will there be phone access to ftf? Jon: It's difficult to do.