E-mail List Archives

You are here: Home > Community > E-mail List Archives > View Thread

Thread: QUESTION: Access Keys

Number of posts in this thread: 11 (In chronological order)

From: Schoppa, Laura
Date: Fri, Sep 28 2001 7:44AM
Subject: QUESTION: Access Keys
No previous message | Next message →

Hello -
I understand that adding Access Keys to navigate around a page is considered
a good idea for making accessible pages.
My question is: How do you let the user know that, for example, ALT + L (if
this is the keystroke combination assigned to go to a field in a form to
fill out one's last name - see attached) - will take them to a certain
location?
Are Access Keys necessary to implement to be in compliance with 508?
Is it a good idea to give the user a page of Access Keystroke combinations
to get around a site in general? Are there any good examples out there of
sites that employ Access Keys effectively?
thanks for any info! <<form.htm>>
Laura Schoppa
Graphic Designer / Web Developer
SI Enterprise Consulting Corp.
Office: 703-905-1687

From: Joel Ward
Date: Fri, Sep 28 2001 9:43AM
Subject: Re: QUESTION: Access Keys
← Previous message | Next message →

Hi Laura,
Accesskeys are not necessary for Section 508, but they are good for
accessibility/usability. So is tabindex. They work in MSIE 4.0+ and
Netscape 6.0+.
I would suggest that you summarize the access keys somewhere prominent on
the site, not just by using an underline. The underline is generally not
recognizable by assistive technology.
You may want to include a help section if the keys are common on many pages,
or just summarize them at the top of the form if they apply just to that
page.
Some notes:
1) In your code, make sure to write the all attributes like this, without
spaces and including double quotes:
type="text"
accesskey="L"
tabindex="3"
Using spaces between the equal sign and the values may cause problems with
some browsers/assistive technology. Also, don't include hard returns in the
code within an attribute in a tag. That doesn't validate either. For
example, this validates:
<input title="This is a test">
but this does not:
<input title="This is a
test">
2) Don't use the same accesskey more than once on a page. Use each letter
only once. (You used F, L, and A twice on your included example.) Also, be
careful not to redefine standard letters/numbers that are used by the
operating system. This may confuse users.
Using the label tag is a good idea. The AT should read the label of the
field if you use the following format:
<label for="test">Test Field</label>
<input type="text" accesskey="T" tabindex="1">
No need to use accesskey in the label tag.
3) The ALT attribute is not officially part of the INPUT tag. So, your
example with the ALT will most likely not work. Instead, you can use the
TITLE attribute with many tags. Example:
<input type="text" title="Please enter your last name so we know how to
address your responses. (Access Key: L)" accesskey="L" id="lname"
tabindex="3">
Check out Index Dot HTML for more reference on these tags:
http://www.blooberry.com/indexdot/html/
Joel
----- Original Message -----
From: "Schoppa, Laura" < = EMAIL ADDRESS REMOVED = >
To: < = EMAIL ADDRESS REMOVED = >
Sent: Friday, September 28, 2001 9:42 AM
Subject: QUESTION: Access Keys

> Hello -
>
> I understand that adding Access Keys to navigate around a page is
considered
> a good idea for making accessible pages.
>
> My question is: How do you let the user know that, for example, ALT + L
(if
> this is the keystroke combination assigned to go to a field in a form to
> fill out one's last name - see attached) - will take them to a certain
> location?
>
> Are Access Keys necessary to implement to be in compliance with 508?
>
> Is it a good idea to give the user a page of Access Keystroke combinations
> to get around a site in general? Are there any good examples out there of
> sites that employ Access Keys effectively?
>
> thanks for any info! <<form.htm>>
>
> Laura Schoppa
> Graphic Designer / Web Developer
> SI Enterprise Consulting Corp.
>
> Office: 703-905-1687
>
>
>

From: Joel Ward
Date: Fri, Sep 28 2001 9:50AM
Subject: Re: QUESTION: Access Keys
← Previous message | Next message →

Whoops, I just noticed I made a mistake on one of my examples. #2's example
should look like this:
<label for="test">Test Field</label>
<input name="test" id="test" type="text" accesskey="T" tabindex="1">
Note the addition of NAME and ID to the INPUT tag.

From: Jon Gunderson
Date: Sat, Sep 29 2001 12:00AM
Subject: Re: QUESTION: Access Keys
← Previous message | Next message →

Laura,
One example of documenting Accesskey on a web site can be found at:
http://www.w3.org/WAI/References/QuickTips/qtform.htm

I also suggest you consider underlining characters that are associated with
the control/link and the access key. This a windows convention for showing
short cuts.
Jon

At 11:39 AM 9/28/2001 -0400, Joel Ward wrote:
>Hi Laura,
>
>Accesskeys are not necessary for Section 508, but they are good for
>accessibility/usability. So is tabindex. They work in MSIE 4.0+ and
>Netscape 6.0+.
>
>I would suggest that you summarize the access keys somewhere prominent on
>the site, not just by using an underline. The underline is generally not
>recognizable by assistive technology.
>
>You may want to include a help section if the keys are common on many pages,
>or just summarize them at the top of the form if they apply just to that
>page.
>
>Some notes:
>
>1) In your code, make sure to write the all attributes like this, without
>spaces and including double quotes:
> type="text"
> accesskey="L"
> tabindex="3"
>
>Using spaces between the equal sign and the values may cause problems with
>some browsers/assistive technology. Also, don't include hard returns in the
>code within an attribute in a tag. That doesn't validate either. For
>example, this validates:
> <input title="This is a test">
>but this does not:
> <input title="This is a
> test">
>
>2) Don't use the same accesskey more than once on a page. Use each letter
>only once. (You used F, L, and A twice on your included example.) Also, be
>careful not to redefine standard letters/numbers that are used by the
>operating system. This may confuse users.
>
>Using the label tag is a good idea. The AT should read the label of the
>field if you use the following format:
> <label for="test">Test Field</label>
> <input type="text" accesskey="T" tabindex="1">
>No need to use accesskey in the label tag.
>
>3) The ALT attribute is not officially part of the INPUT tag. So, your
>example with the ALT will most likely not work. Instead, you can use the
>TITLE attribute with many tags. Example:
> <input type="text" title="Please enter your last name so we know how to
>address your responses. (Access Key: L)" accesskey="L" id="lname"
>tabindex="3">
>
>Check out Index Dot HTML for more reference on these tags:
> http://www.blooberry.com/indexdot/html/
>
>Joel
>
>----- Original Message -----
>From: "Schoppa, Laura" < = EMAIL ADDRESS REMOVED = >
>To: < = EMAIL ADDRESS REMOVED = >
>Sent: Friday, September 28, 2001 9:42 AM
>Subject: QUESTION: Access Keys
>
>
> > Hello -
> >
> > I understand that adding Access Keys to navigate around a page is
>considered
> > a good idea for making accessible pages.
> >
> > My question is: How do you let the user know that, for example, ALT + L
>(if
> > this is the keystroke combination assigned to go to a field in a form to
> > fill out one's last name - see attached) - will take them to a certain
> > location?
> >
> > Are Access Keys necessary to implement to be in compliance with 508?
> >
> > Is it a good idea to give the user a page of Access Keystroke combinations
> > to get around a site in general? Are there any good examples out there of
> > sites that employ Access Keys effectively?
> >
> > thanks for any info! <<form.htm>>
> >
> > Laura Schoppa
> > Graphic Designer / Web Developer
> > SI Enterprise Consulting Corp.
> >
> > Office: 703-905-1687
> >
> >
> >
Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
MC-574
College of Applied Life Studies
University of Illinois at Urbana/Champaign
1207 S. Oak Street, Champaign, IL 61820
Voice: (217) 244-5870
Fax: (217) 333-0248
E-mail: = EMAIL ADDRESS REMOVED =
WWW: http://www.staff.uiuc.edu/~jongund
WWW: http://www.w3.org/wai/ua

From: Schoppa, Laura
Date: Sat, Sep 29 2001 12:13AM
Subject: Re: QUESTION: Access Keys
← Previous message | Next message →

thanks so much! I appreciate your very thorough reply.
- Laura

From: Glenda Watson Hyatt
Date: Sat, Sep 29 2001 12:23AM
Subject: Re: QUESTION: Access Keys
← Previous message | Next message →

Hi Laura,
Actually how to inform users what the accesskeys are is one of the
limitations. As I understand it, accesskeys are good in theory but
difficult to implement. I explain this in at brief article at
http://www.eaglecom.bc.ca/Archives/Issue3.htm.
Others, feel free to enlighten me if I'm misinformed.
Good luck, Laura.
Cheers,
Glenda
*********
Glenda Watson Hyatt
Soaring Eagle Communications
"Creating freedom and power through accessible communications"
E Mail: mailto: = EMAIL ADDRESS REMOVED =
Website: http://www.eaglecom.bc.ca
Want to know how to make your website accessible to more people?
Subscribe to our FREE newsletter by emailing
mailto: = EMAIL ADDRESS REMOVED =
*********

>

From: Joel Ward
Date: Fri, Sep 28 2001 1:47PM
Subject: Re: QUESTION: Access Keys
← Previous message | Next message →

Hi Glenda,
Interesting. Has the technology advanced at all since you wrote that
article in 1999? It would be so very nice to have the accesskey as a viable
option.
I heard there is a list of reserved keys floating around out there. I would
be curious to know which keys are actually safe to use.
Does anyone know of that list? Is it even worth trying to implement
accesskeys these days?
Joel
----- Original Message -----
From: "Glenda Watson Hyatt" < = EMAIL ADDRESS REMOVED = >
To: "WebAIM forum" < = EMAIL ADDRESS REMOVED = >
Sent: Friday, September 28, 2001 2:19 PM
Subject: RE: QUESTION: Access Keys

> Hi Laura,
>
> Actually how to inform users what the accesskeys are is one of the
> limitations. As I understand it, accesskeys are good in theory but
> difficult to implement. I explain this in at brief article at
> http://www.eaglecom.bc.ca/Archives/Issue3.htm.
>
> Others, feel free to enlighten me if I'm misinformed.
>
> Good luck, Laura.
>
> Cheers,
> Glenda
>
> *********
> Glenda Watson Hyatt
> Soaring Eagle Communications
> "Creating freedom and power through accessible communications"
> E Mail: mailto: = EMAIL ADDRESS REMOVED =
> Website: http://www.eaglecom.bc.ca
> Want to know how to make your website accessible to more people?
> Subscribe to our FREE newsletter by emailing
> mailto: = EMAIL ADDRESS REMOVED =
>
> *********
>
>
>
> >

From: Glenda Watson Hyatt
Date: Fri, Sep 28 2001 2:05PM
Subject: Re: QUESTION: Access Keys
← Previous message | Next message →

Good questions, Joel. Perhaps someone with more knowledge of AT can respond
better than I can.
Cheers,
Glenda
*********
Glenda Watson Hyatt
Soaring Eagle Communications
"Creating freedom and power through accessible communications"
E Mail: mailto: = EMAIL ADDRESS REMOVED =
Website: http://www.eaglecom.bc.ca
Want to know how to make your website accessible to more people?
Subscribe to our FREE newsletter by emailing
mailto: = EMAIL ADDRESS REMOVED =
*********

>

From: Ricardo Sanchez
Date: Fri, Sep 28 2001 2:47PM
Subject: Re: QUESTION: Access Keys
← Previous message | Next message →

Hello:
We use accesskeys on diferents web sites. We underline the letter that is accesskey and include a page with a list of accesskeys.
Example:
http://www.timon.com/far/
http://www.timon.com/far/atajos.html
In my opinion, it is important avoid conflicts with browsers shortcut keys. So we don't use the shortcut keys for file, edit, help
and address
F (File), E(Edit) and H (Help) D (aDdress)
In Spanish
A (Archivo), E (Edicion), U (ayUda) and D (Direccion) . We avoid all these letters (F,E,H,D,A,U) because very much people in Spain
use English versions of browsers.
Users with browsers in another languages: Dutch, French, German can have conflict with my accesskeys and their browser shortcut
keys. I should like how avoid this conflict. Any idea?
Regards,
Ricardo

----- Mensaje original -----
De: Joel Ward < = EMAIL ADDRESS REMOVED = >
Para: WebAIM forum < = EMAIL ADDRESS REMOVED = >
Enviado: viernes, 28 de septiembre de 2001 21:43
Asunto: Re: QUESTION: Access Keys

Hi Glenda,
Interesting. Has the technology advanced at all since you wrote that
article in 1999? It would be so very nice to have the accesskey as a viable
option.
I heard there is a list of reserved keys floating around out there. I would
be curious to know which keys are actually safe to use.
Does anyone know of that list? Is it even worth trying to implement
accesskeys these days?
Joel
----- Original Message -----
From: "Glenda Watson Hyatt" < = EMAIL ADDRESS REMOVED = >
To: "WebAIM forum" < = EMAIL ADDRESS REMOVED = >
Sent: Friday, September 28, 2001 2:19 PM
Subject: RE: QUESTION: Access Keys

> Hi Laura,
>
> Actually how to inform users what the accesskeys are is one of the
> limitations. As I understand it, accesskeys are good in theory but
> difficult to implement. I explain this in at brief article at
> http://www.eaglecom.bc.ca/Archives/Issue3.htm.
>
> Others, feel free to enlighten me if I'm misinformed.
>
> Good luck, Laura.
>
> Cheers,
> Glenda
>
> *********
> Glenda Watson Hyatt
> Soaring Eagle Communications
> "Creating freedom and power through accessible communications"
> E Mail: mailto: = EMAIL ADDRESS REMOVED =
> Website: http://www.eaglecom.bc.ca
> Want to know how to make your website accessible to more people?
> Subscribe to our FREE newsletter by emailing
> mailto: = EMAIL ADDRESS REMOVED =
>
> *********
>
>
>
> >

From: Mark Magennis
Date: Mon, Oct 01 2001 9:20PM
Subject: Re: QUESTION: Access Keys
← Previous message | Next message →

A group I know are experimenting with access keys for button clicks. They
have found that in MS IE4, typing an access key combination such as ALT+S is
equivalent to clicking the button. But in IE5, it only puts the focus on the
button but does not click it. Is there a work around for this?
They have also found that on some machines they have to press Shift+ALT+S to
get the access key to work, which sounds like an altogether more complicated
problem.
Any ideas?
Thanks, Mark

From: Mark Magennis
Date: Mon, Oct 01 2001 9:44PM
Subject: Re: QUESTION: Access Keys
← Previous message | No next message