WC: Define a variety of disability profiles, and give task and expected use of these.

JG: Two concepts: choose one among, or supply alternatives for concurrent use.

WC: Announce when done loading.

XX: A full image with images off, a blank page.

KL: If there is a URL attached, that id different from a pure img.

KH: Do provide to screen readers info on img.

EH: A link attached to image is read in IBM reader. Often the length of the URL is too confusing.

MP: Render the last part of the link, not the whole thing.

KL: That's what is referenced.

TH: URL on status line, and screen reader would read that to user.

IJ: CSS has a before and after "pseudo-element" before rendered element. Rendering of external objects is not under author control, nor under stylesheet control even. For that reason, there is not adequate to use for alt text.

IJ: Split out 4.1 guideline topics.

JB: Propose overarching controls under user preferences.

IJ: Implementation (by particular ua) vs. technique (CSS).

JA: How pass through user preferences (and to where).

IJ: The techniques doc should be able to indicate what might be achievable.

KB: This format as a checklist is more amenable.

KH: Hard to get this from a longer checklist as too long to an executive summary.

JG: Thanks to participants for taking time and cost to attend.

JB: Indexes in page authoring guidelines, by priority of technique.

WC: Recommend generating checklist from the guidelines. Users of this guideline are the implementors, Microsoft.

CO: Checklist pushback from developer. Why is this important?

KC: How important the turning off of blinking text is dependent on the text, as determined by the author.

JB: May not know that importance.

JB: Report II. Didn't get further to rewriting. Hard to break apart the current organization.

KC: Include the variations in simultaneous access.

JA: complementary or supplementary information revelation. How tell screen reader that a longdesc

is present.

IJ: How let user know that a script is present.

CO: Technique to do longdesc, if image is not shown, put up special icon, add text [indicating that longdesc is present] as well as the alt text, and make the image tab-stoppable if it isn't already, and have menu

choice including longdesc…

WC: Need a querying mechanism to determine what are the alternatives for display.

JG: Characteristics of a context menu may be more generally useful.

EH: If image has longdesc, use "D" special image, present plain text,

CO: Now if right-click on an image get properties of it. Some power tools give more flexibility.

JB: In longdesc, we broke out identification from content, same thing here.

JB: Visibility, group access controls.

JA: If "show-sound" is on, also haul up captions if they are there. Multimedia two streams concurrently that captures visual text in balloons. That is different kind of captions. (Chuck … described to JA).

DC: Complementary vs supplementary, across modalities we have to be clear whether we have a direct interpretation, or an additive interpretation.

JA: Need text caption as well as second video for deaf-blind.

KC: Danger in image file of text, makes inaccessible.

JB: New models of presentation may need to map to

KC: Text in non-text is coming, particularly as digital photography will have overlays of text.

How does user act on application with alternative input means (to mouse events)

How does user know what is changed on a page?

CO: Most difficult and/or important problem.

JG: Need cooperation of PA.

JG: 6.5

CC: Jaws cursor: either mouse pointer or PC cursor can be moved. Can route either to JAWS.

MP: Haven't done much with javascript.

JG: Some context menu useful.

JG: Event bubbling. Now no necessary correspondence to place and script (can have a default responder script for interpreting an event.) An alternative is to put all the event responders on any elements.

IJ: Tried to get a bound on what we should address. Too much intractable as cannot predict semantics of a script. An element may be involved in the initiation of an event, though bubble up may make it remote.

The author must assert what a script is doing.

IJ: DOM 2 may have some coupling to help with semantics.

IJ: Identification only for elements with on… events.

IJ: Navigation

JG: WAI Protocols and Formats feeding DOM group. There are mechanisms to get into DOM any special

requirements that WAI may want.

JG: Any element may have associated script(s).

CO: Keyboard actions on equal footing with mouse actions, in DOM.

KH: Some of the MS developers are on DOM team.

CO: Chris Wilson is one.

CL: Often suppress scripts. Do have a DOM representative.

IJ: Scripts with resprect to HTML: bound to events, executed at load/unload, and in head of document,

Submit buttons to trigger scripts. Issue is which would be disabled.

CO: Demo of Outlook 98 Organize feature, uses HTML through scripting.

CO: Content + style + behavior + user input all impact this.

JA: That HTML is used in other application doesn't matter to us.

KH: If you solve the problem in the browser, then other applications built on it get solution free.

WC: We could list what we want for UA. Element may need events list.

IJ: Propose for PA that title be used to describe the on-event

CO: Title as tool tip.

HB: Title isn't explicit enough for all the ten on-events. There is no hook for these differentiations.

JG: Noscript is alternative.

WC: A page authored with script can be ok.

CO: Need path for older sites "noscript" to avoid rewriting site.

CO: Need improvements to DOM and UA to make scripts more nearly accessible?

IJ: What is an accessible script is?

KC: What makes a script inaccessible?

IJ: What makes a page inaccessible? Provide information to replace what script would have provided.

IJ: User can't tell whether or not a script is accessible.

DC: Focus on content rather than its representation. Find alternative

IJ: If script is making page inaccessible, then let user turn it off.

DC: Need alternative content from author.

JA: Why tell user that a script is doing something? If user is expecting something to happen that the

script provides.

CL: Celestial Seasons is all-script. Others use just java submit -- rather than just HTML submit.

JA: hotcoffee authoring tool has included ACSS styling.

KC: What is the problem we are trying to classify regarding scripts. What are the identifiable problems

in DHTML. We need to avoid the "all scripts are bad" syndrome.

CO: An application of a CD-sampler, lots of demo programs on a CD. Install Shield, Nuts and Bolts,

Hover over, watermarks, click and go, etc. May have been written in anything. The problems are