Re: 1.5: Discuss link characteristics?
At 4:00 AM 2/10/97, Martin Bryan wrote:
>Behaviour is not up to the user, it is up to the author. It is the
>author/server that has to control what happens when the link is selected by
>the user. Except in rare cases the user should not be able to change the
>action that selecting a link causes.This is why you must separate
>presentation from behaviour.
I'm sorry. Color blind users should be able to see fromthe link type that
Kringle.class implements a "pop-up-list" instead of failing to see Green
text on a red background when they have equal brightness.
Similarly it may help a blind user to see a series of hierarchically
organized links instead of an animated display of shuffling cards.
Similarly, it may help a web-walker to see that two pages are connected by
a link rather than having to execute a java script in a "sandbox area" and
trap calls to AppletContext.showDocument().
We need to be able to specify behavior, but we need not be ruled by our
need to specify behavior.
>This would be better called Link Action. Traversal is not something
>non-rocket scientists understand. What most users understand by clicking on
>a hotspot is that some action should take place. This is what the
>behavioural side of the equation covers.
I like "Link Action". It's a much less predjudicial term than traversal,
and it covers the same field beautifully, as well as many things beyond
that field, that traversal slights.
I am not a number. I am an undefined character.
David Durand email@example.com \ david@dynamicDiagrams.com
Boston University Computer Science \ Sr. Analyst
http://www.cs.bu.edu/students/grads/dgd/ \ Dynamic Diagrams
MAPA: mapping for the WWW \__________________________