I’m creating an interactive infographic. For those users who need explanation once they encounter the map, there is a button that activates tool tips over certain interaction points that help the user get started.
There’s currently a push for these tooltips to display for a period of 5 seconds when the user encounters the map.
My thinking is that not all users need the tips. and even less users need the tips the second time around. The third time around users will get annoyed.
Which is better:
1 Don’t show the tool tips at all unless the user activates them
2 Show the tool tips for 5 seconds when a user encounters the graphic
Sometimes Flash is the MOST accessible answer. This is why some tests for (X)SL (somelang as a second language, like ESL) are done in Flash, because the audio+video component is the only thing that works with a large number of people who are challenged by a language. Something entirely different would have to be presented for those who can’t get those two benefits (they are better off with a real web page, with text accessibility and not device (mouse) or motor-skills-dependent). This is why Flash or other progams with interactive images preferred for (x)SL and working with small children.
The Netherlands gives test to immigrants using Flash. They have to log in to a central machine, are timed, and are tested on reading and listening. They are given multiple choice with large, obvious buttons which change colour and give a very clear “click” when chosen. They did this for a reason.
Though I’m not saying maps or infographics have to be Flash (I do them in CSS regularly). Who is the audience?
1 Don’t show the tool tips at all unless the user activates them
Yes, I think the way you have it now is doable. I can mouse over to Helpful Hints, which shows the hints for as long as my mouse sits there.
It’s damn small though, and hard to read. Can’t it be zoomed, or scale to the user’s screen? Who can read that?
Do you consider 5-seconds is long enough though and it is probably best to keep them appearing as you don’t know how good your users short-term memory is in the first place.
Yes, they could be slightly “annoying” but at least it would be a ‘constant behaviour’ for an unfamiliar interface.
Yeah, Stevie. I’m right there with you. I’m simply the hands on this one.
My questions is more about what should happen once the users hit enter and passes the splash screen, should the tool tips come up on their own, or can the user be expected to see the “helpful tips” button if they encounter confusion. Rolling over the helpful tips button reveals the tooltips.
I think automatically showing the tool tips each time a user looks at it will get annoying. But I’m looking to the forum here to discuss which is better in this instance so I can better tell my party why this isn’t a good idea.
Considering accessibility isn’t going to be possible with a Flash site like that, your best bet is to focus on what’s most usable (by that I mean what is the least annoying for the end user). In regards to the accessibility issues, the only thing you can do (if you’re just on the side lines) is to-do everything you can to convince the team that an entirely Flash built solution is going to damage them in the long-term. Education is part of the job and unfortunately every now and again we need to give the powers that be a firm shake to allow them to see the errors of their ways. As things currently stand, the work is 99% inaccessible (non-disabled friendly)!
Sorry to be the bearer of bad news, but the tooltips are the least of your accessibility worries.
For a start, to have the entire thing written in Flash is just about the biggest accessibility no-no out there. Your accessibility is currently hovering somewhere around the zero mark.
Second, I have no idea what it is, what it does, or what the issue over tooltips is. As far as I can see, all it does is give tooltips. You hover over something, and up pops a message. It has a hand cursor, so you click on it, and nothing happens.
