W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2001


From: Charles McCathieNevile <charles@w3.org>
Date: Thu, 5 Apr 2001 18:00:06 -0400 (EDT)
To: Liz Roberts <liz@netlogix.net>
cc: <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.30.0104051752590.20692-100000@tux.w3.org>
I would put  the accesskey stuff in the first one so people can see it fast.
I assume that people who are skipping the navbar will kow it was there and go
back to it when they want to know how to get around it, and many accesskey
users will be ding it visually.

It is a good idea to stay away from teh windows keys because that is a major
implementation thing at the moment, but long term that is not a successful
strategy - many people who are looking for key-friendly browsers will use
Opera or something anyway, possibly on a different system. Long term there is
a basic problem with the way accesskey was specified which looks like getting
resolved in the future without having to really break anything you do happen
to do now.

There is one screenreader for the Mac - outSpoken. There are a number of
tools that can be used to get speech output - iCab and Lynx both have it
built in, for example. The Mac also has built-in voice recognition for
commands, which is a nice feature. (especially since the mac is not really a
platform where people are good at keyboard shortcuts). Mousekeys, sticky keys
and so on are available, as are free talking keyboards and other speech
system tools (Mac has had built in text to speech available for some years,
so people have been making things for it for a while).

I found a handful of intersting applications at http://www.tucows.com - look
for Mac, then Education, then Accessibility (I don't know why accessibility
is part of education, but that's ok...)


Charles McCN

On Thu, 5 Apr 2001, Liz Roberts wrote:

  On navigation bars which repeat, at the top of the page and in the footer
  for instance, should accesskey information be present in both sets, the
  first set, or the second set (perhaps since the first needs to have an
  option to skip it available)?

  Also, I've tried to stay away from using quick key combinations from Windows
  IE (F, E, V, A, T, H) because "they're needed to access Explorer's menus."
  Is this necessary, important, and/or are their other issues regarding this
  to be concerned about?

  Finally, on an unrelated note, are there any programs along the lines of
  JAWS, pwWebspeak, etc. for the Mac?


  P.S. The tabindex 10's tip is great, thanks!

Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Thursday, 5 April 2001 18:00:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:12 UTC