If you took the Help images out of a link tag and then used JS to
create the popup behaviour, then the help image would not be included
in the tab-order.
I.e.
<img src="help.png" id="helpimg_4001"/>...
var x=document.getElementById("helpimg_4001");
x.onclick=popupfunction;...
Stephen
On 13 Mar 2006, at 19:31, <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> wrote:
Thanks for your replies to date. To give you a deeper understanding
of the situation:
- despite quite skilled users, double tabbing hundreds and hundreds
of times a day is seen as a efficiency issue too (x 5days x 45weeks)
- the sample form (http://users.bigpond.net.au/leenath/form/forms-
example.htm) is nothing like our applications (obviously in real
life first name, last name etc. would not require any help). They
are complex! It's the nature of our business. Therefore, despite a
very clear label, users often need to be reminded of the type of
data that is required in a response. Sometimes policy and
legislation requirements are included in the help, making them
lengthy at times (so samples of input or "always there" help
information/tips is not appropriate).
Thanks for your replies to date. I'll go through them all in more
detail tonight.
-------------------------------
ORIGINAL MESSAGE:
Hi all,
I'm hoping to get some feedback from people regarding a solution to a
usability issue. I work for a large organisation and we have very
large/detailed processing required. Because the applications we
develop are
very detailed and change dynamically depending upon the current input,
context sensitive help becomes very important.
I have quickly thrown together an example of what Im talk about...
http://users.bigpond.net.au/leenath/form/forms-example.htm
The issue we face is that users are frustrated with having to tab
through
the help icons all the time. Users get into the habbit of tabbing
twice (to
go past the help and get to the next input field), but sometimes a
help item
wont exist, meaning the user accidentally tabs past the next input
feild.
Users say they want the help, because it comes in handy frequently,
especially as the organisation is so huge and complex that they
could never
remember exactly what every input feild is about.
So, here is what feeback Im looking for - How can we keep context
sensitive
help available for each input feild that requires it but
potentially ignore
it in a tabbing sequence? However, help must also be accessible
(think about
screen readers) and available via keyboard if they need to select
it. It
seems like a catch 22 to me, but I figure someone out there may see a
solution that I cannot.
I look forward to your feedback/ideas.
Cheers
Nathan
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
