LOL. Good point. On 6/8/06, Sandra Clark <[EMAIL PROTECTED]> wrote: > Except for people of course who can't see the underlines. > > If you are going to use accesskeys (and really they cause more accessibility > problems than they solve), then you also need to create and link to an > accessibility statement for the page which gives a reference to the access > keys used and what they do. > > > Sandra Clark > ============================== > http://www.shayna.com > Training in Cascading Style Sheets and Accessibility > -----Original Message----- > From: Rob Wilkerson [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 08, 2006 9:53 AM > To: CF-Talk > Subject: Re: accesskey conundrum > > I'm not a big fan of access keys because of how they interfere with the > shortcuts I've set up in my environment and much-discussed accessibility > issues, but when I do use them on forms for whatever reason, I tend to > follow the Windows UI standard of underlining the letter in the label that, > in conjunction with the Alt key activates the shortcut. Most of the people > that are likely to use the shortcuts generally seem to recognize the > convention, from what I've seen. > > On 6/8/06, Andy Matthews <[EMAIL PROTECTED]> wrote: > > Damien... > > > > I like your idea of jumping to the first field in each section. > > Because honestly. Who's going to remember every key command for your > > form? Just give them 5 or 10 and they'll be happy. > > > > <!----------------//------ > > andy matthews > > web developer > > certified advanced coldfusion programmer ICGLink, Inc. > > [EMAIL PROTECTED] > > 615.370.1530 x737 > > --------------//---------> > > > > -----Original Message----- > > From: Damien McKenna [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 07, 2006 3:01 PM > > To: CF-Talk > > Subject: OT: accesskey conundrum > > > > > > Here's the story. I'm working on a series of somewhat long forms that > > I'd like to make completely accessible using accesskeys in addition to > > other basics (labels, pure CSS layout, etc). The problem is that I'm > > ending up with more fields than accesskeys makes sense for, and there > > are multiple fields that could/should use the same key. One idea I > > had was to have one accesskey defined for the top field in each > > fieldset then just let them tab between the different fields, but that > > isn't great in e.g. OSX that has fairly crappy keyboard navigation > > anyway. So what do y'all do to overcome this for your accessible > > forms? Thanks. > > > > -- > > Damien McKenna - Web Developer - [EMAIL PROTECTED] The Limu > > Company - http://www.thelimucompany.com/ - 407-804-1014 #include > > <stdjoke.h> > > > > > > > > > >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:242932 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
