W3C home > Mailing lists > Public > public-html@w3.org > July 2007

Re: Accesskey - spec proposal

From: Michael(tm) Smith <mike@w3.org>
Date: Tue, 3 Jul 2007 20:27:35 +0900
To: Henri Sivonen <hsivonen@iki.fi>
Cc: Charles McCathieNevile <chaals@opera.com>, Maciej Stachowiak <mjs@apple.com>, "public-html@w3.org" <public-html@w3.org>
Message-ID: <20070703112734.GC12430@mikesmith>
Henri Sivonen <hsivonen@iki.fi>, 2007-07-03 14:13 +0300:

> On Jul 3, 2007, at 14:08, Charles McCathieNevile wrote:
>
>> The WAP forum (now OMA) obviously disagreed with you, since on WAP 
>> browsers accesskey (although restricted to numbers 1-9) is widely 
>> interoperable.
>
> How is the discoverability problem addressed by WAP browsers?

See my previous messages in this thread. It works like this:

  - elements with access keys are typically grouped by convention
    at the bottom of a page and are used, almost universally, just
    for navigational functions (up/home, forward/next,
    back/previous, ...) 

  - for elements with access keys, numbered buttons (plus star and
    hash buttons) are rendered inline next to the content of the
    element (which is typically just localized "Home", "Back",
    etc. text)

  - the browser is in access-key mode by default

This has worked well for mobile browsing for many years now and
there is nobody asking for it to fixed or improved. The use case
and requirements just must be supported going forward in any new
HTML specification.

  --Mike

-- 
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/

Received on Tuesday, 3 July 2007 11:28:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:02 GMT