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

RE: Comment - 25. XHTML Role Access Module

From: John Foliot - WATS.ca <foliot@wats.ca>
Date: Tue, 7 Jun 2005 08:07:38 -0400
To: "'Mikko Rantalainen'" <mikko.rantalainen@peda.net>, <www-html@w3.org>, "'W3c-Wai-Ig'" <w3c-wai-ig@w3.org>
Message-ID: <003801c56b59$816f17d0$6401a8c0@bosshog>

Mikko Rantalainen wrote:
> +1
> There isn't enough accelerator keys available that are unused in
> every browser. Firefox, MSIE or Opera already reserve almost every
> ALT+anything combination by default. Alt+1 to Alt+9 are used by
> firefox to directly change to another tab so I cannot use those
> either as a page author. 

Do you not mean Ctrl+(#) for tab focus shift?  That at least is the default
in my (North American) installation on Windows - are you saying that it is
different on/in a different configuration?

> All unused key ALT-combinations available after testing Firefox,
> Konqueror, MSIE with Finnish localization and Opera:
> Alt+q
> Alt+r
> Alt+y
> Alt+u
> Alt+i
> Alt+x
> Alt+c
> Alt+0
> (And at least Alt+q, Alt+r, Alt+c and Alt+x are used by Unix version
> of Netscape Navigator so don't give any written instructions on the
> page for these combinations in any case.)

Thank you for this Mikko.  Much of this we have already documented at
http://wats.ca/resources/accesskeysandkeystrokes/38, however, if from your
research you have any information which can be added to the table I would
appreciate your notes.  Due credit will be accorded.

> I think 'role' or 'accesstarget' attribute giving a name for the
> access point would make much more sense. There's even a remote
> change that two random authors might select "search" for the
> function 'role' name by accident even when there weren't any list of
> defined roles available.

Yes, in my opinion it is a better start, but I remain concerned about the
ability for authors to bind specific keystrokes - I do not see appropriate
resolution solutions within the spec and fear that perpetuating this ability
will weaken rather than strengthen the concept, as it still leaves the
construct open to abuse by un-informed authors (deliberately or otherwise).

I have written at great length over the past weekend in response to numerous
comments to my postings... The sum is quite disjointed and so I will
endeavor to summarize and repost the salient points in a more
reader-friendly fashion over the next day.

Thanks for your comments and support.

John Foliot  foliot@wats.ca
Web Accessibility Specialist / Co-founder of WATS.ca
Web Accessibility Testing and Services
Phone: 1-613-482-7053
Received on Tuesday, 7 June 2005 12:07:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:25 UTC