- From: Lisa Seeman <lisa@ubaccess.com>
- Date: Sun, 08 Aug 2004 00:00:29 +0200
- To: Gregg Vanderheiden <gv@trace.wisc.edu>, w3c-wai-gl@w3.org
was traveling Lisa ----- Original Message ----- From: "Gregg Vanderheiden" <gv@trace.wisc.edu> To: <w3c-wai-gl@w3.org> Sent: Wednesday, August 04, 2004 7:55 PM Subject: Agenda: Aug 5 2004 WCAG WG telecon > > > Time: 20:00 UTC (16:00 Thurs. US Eastern, 22:00 Thurs. Central Europe, > 06:00 Fri. Eastern Australia) > Number: +1-617-761-6200, passcode 9224 irc.w3.org 6665, channel #wai-wcag > > Agenda: > > This week we will be discussing a number of topics that have been active on > the list. Goal is to get closure if possible -- but good progress at least. > I don't expect we will close them all -- but lets see if we can come > prepared and have a good discussion. > > > 1. Accesskey alternative, most common access types > refer to Becky's starter message at: > <http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0773.html> > > 2. programmatically located, issue 330 > <http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=330> > We have a number of terms and we need to define them. One appears to be > redundant with another as well. > "derived programmatically", > "programmatically determined", > "programmatically located" and > "programmatically identified" > Jason posted one set of definitions that are listed at the end of the > agenda. John is working on a version that might be available for the > meeting. [1] > > 3. Definition of authored unit > Jason's original post > <http://lists.w3.org/Archives/Public/w3c-wai-gl/2004JulSep/0203.html> > Thread started by DIWG folks > <http://lists.w3.org/Archives/Public/w3c-wai-gl/2004JulSep/0279.html> > > 4. Guideline 4.1 > <http://lists.w3.org/Archives/Public/w3c-wai-gl/2004JulSep/0202.html> > > 5. Guideline 4.2 > <http://lists.w3.org/Archives/Public/w3c-wai-gl/2004JulSep/0200.html> > > Other discussions that have occurred on the list recently: > 1. Javascript and alternatives > <http://lists.w3.org/Archives/Public/w3c-wai-gl/2004JulSep/0140.html> > > > [1] Jason writes: > I have made a quick search of the document, and noticed that we say > "derived programmatically" (guideline 1.3), "programmatically > determined", "programmatically located" and "programmatically > identified" under principle 3. One solution would be: > > "Programmatically determined" - is available in a standard > machine-readable form (e.g., in markup, a data model or metadata) that > can be processed by software. > > "Programmatically located" - is available in a machine-readable form, > or as text in a natural language, that can be reliably found by > searching or data traversal mechanisms implemented in user agents or other > tools. To satisfy this requirement it suffices that a list of relevant > alterantives (e.g., alternative definitions of a word) can be found. > > "Programmatically identified" - is available in a machine-readable > form, or as text in a natural language, that can be reliably found by > searching or data traversal mechanisms implemented in user agents or other > tools. To satisfy this requirement it is necessary to provide > sufficient information to enable software to locate the exact item > required; it is not sufficient that a list of alternatives can be > identified. > > This is a very rough attempt at some definitions. > > > >
Received on Saturday, 7 August 2004 22:01:07 UTC