Re: accesskey, 7.1, win98.

On Thu, 30 Jan 2003, Charles McCathieNevile wrote:

> The User Agent Guidelines do cover this as far as I can tell:
> http://www.w3.org/TR/UAAG10/guidelines.html#tech-info-current-ua-config
> says
>
>   Provide information to the user about current user preferences for input
>   configurations.

I expressed this poorly: what I meant was that they don't seem to
recommend a standard way to do this for visual browsers, so I'm not
aware of what I should expect.  They have good reasons for not doing
so in terms of not limiting browser design and innovation.

>
> As far as I can tell this should cover what keys can be used to navigate
> around a document.

Yes, agreed.
>
> One approach to doing this would be to implement the CSS
> pseduo-elements :before and :after, the property content,
> and attr() then a user style sheet rule like
>
>  *[accesskey]:before { content: "<" attr(accesskey) ">" }
>
> would provide a functionality like iCab has for identifying the accesskeys.

Would this work now?  If so, I'll scour the docs for more info on
how to set this up.
>
> There is a similar functionality somewhere in Amaya already, which is used to
> put in markers for things like targets and annotations. Adapting / repeating
> this would be another possiblity. For accessibility purposes, copying the
        [...[

These look good ideas.  So I have not missed existing functionality
then?
>
> just my thoughts...
>
> Chaals
>
> On Wed, 29 Jan 2003, Hugh Sasse Staff Elec Eng wrote:
        [...]
> >be rather quiet about what has been defined.  I could find no
> >mention of how one is supposed to discern this information whilst
> >reading the User Agent Accessibility Guidelines, so if there is a
> >general principle for most browses, I have missed it.
        [...]

> --
> Charles McCathieNevile  http://www.w3.org/People/Charles  tel: +61 409 134 136

        Thank you,
        Hugh

Received on Thursday, 30 January 2003 11:56:18 UTC