RE: Document fragment anchor elements

At 07:15 AM 05/14/2001, Dave  J Woolley wrote:
> > From: Greg Marr [SMTP:gregm@alum.wpi.edu]
> >
> > At 06:25 AM 05/11/2001, Dave J Woolley wrote:
> > >[DJW:]  In that case, accesskey needs to be allowed on all 
> elements.
> >
> > No, it doesn't.  Notice "link targets" (NAME) not "links"
> > (HREF).  That means replacing <P><A NAME="blah">text</A></P> with 
> <P
> > ID="blah">text</P>.
>
>[DJW:]  There's nothing that says that accesskey is limited to <a 
>href...  To me it would seem that anything that is a target is 
>something that you are likely to want to get to quickly without 
>using a mouse.

If it's something you are likely to want to get to quickly, then the 
author of the page has likely provided a link to that portion of the 
page (or they wouldn't have put in the ID/NAME in the first 
place).  That *link* can be activated using the accesskey.

http://www.w3.org/TR/html401/interact/forms.html#adef-accesskey
>Pressing an access key assigned to an element gives focus to the 
>element. The action that occurs when an element receives focus 
>depends on the element. For example, when a user activates a link 
>defined by the A element, the user agent generally follows the link.

How do you give focus to an element that doesn't have any visual 
representation, such as BR?  How does the user know what the access 
key is for an element unless they can see the element?  The "action" 
that occurs is that the element is brought into view.  If they can 
already see the element, what is the point in brining that element 
into view?

If accesskey were defined as you suggest, what would happen if I 
wrote this: <INPUT TYPE=SUBMIT ID=SOME_ID ACCESSKEY="A"> and then 
used that accesskey?  Would it submit the form, or would it bring me 
to that portion of the page?

-- 
Greg Marr
gregm@alum.wpi.edu
"We thought you were dead."
"I was, but I'm better now." - Sheridan, "The Summoning"

Received on Monday, 14 May 2001 11:53:17 UTC