W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2001

Re: Raw minutes from 4 January 2001 UAWG teleconference

From: Charles McCathieNevile <charles@w3.org>
Date: Fri, 5 Jan 2001 09:21:24 -0500 (EST)
To: Ian Jacobs <ij@w3.org>
cc: <w3c-wai-ua@w3.org>
Message-ID: <Pine.LNX.4.30.0101050911000.11374-100000@tux.w3.org>
On Thu, 4 Jan 2001, Ian Jacobs wrote:

     1.Next User Agent face-to-face meeting in Boston on 1-2 March 2001

I will be at the week of meetings, but I will be in the AU and ERT meetings
at that time.


     2.Update on glossary group formed in WCAG

     JG: There has been a glossary group formed. There is a published

More update (mostly for editors perhaps, or for future planning): I have
nearly finished getting Max Froumentin to write scripts that allow me to use
this glossary to provide the glossary for ATAG drafts. Thus future drafts of
the Techniques and of ATAG 2 will contain their own glossary, but it will be
derived from teh version of the unified glossary that is current at the time
they are published. I am hoping that we can have a pretty well unified
glossary rather than redifining terms for each spec.

     6.Issue #423: Checkpoint 9.3: Need min requirement for how/where conf
       information presented.

      a) For 9.3, min req is that all information about author-specified
         input configs be availble in a single place.
         (Need to define clearly what "in a single place" means,
          or what "distributed solution" means). For example,
         a list of bindings would satisfy the requirement.
      b) For 9.1, (which is P1), distributed solution ok (e.g.,
         information available in menus).
         Note that if the default config is the current
         config (and user can't change), then 10.3 requirement ensures
         that 9.1 is satisfied.
      c) Do not add in-context rendering as a P3 checkpoint.
      d) Add in-context rendering and configurability to techniques.

iCab 2.1 and 2.2 provide in-context information about accesskeys (they put
<x> next to the thing that has the attribute, by default).

Lynx effectively provides a list (well, really it provides several different
lists, depending on what kind of action you are thinking of) as a page which
replaces the current page in the viewport - you then hit the back button to
go back to where you wanted to use the action. In some cases (e.g. lists of
links) you don't have to hit back - the options are available "live" from the

     7.Issue #424: Checkpoint 9.3: Do author-specified shortcuts include
       active elements that take mouse input?

     TL: I think that this is an authoring issue.

CMN: I agree that this is an authoring issue, but I think that in some cases
these things are shortcuts. I am just not sure (off the ntop of my head) how
to tell which ones.

       a) Presentation of information about bindings
          achieved through scripts are not required by checkpoint 9.3.
       b) Don't say explicitly that mouse bindings are excluded
          (although today, we don't think markup languages let you
          specify mouse bindings).
Received on Friday, 5 January 2001 09:21:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:29 UTC