[thelist] IE - The claret (white dotted line) on clickable images

.jeff jeff at members.evolt.org
Mon Nov 26 21:57:30 CST 2001


james,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: MRC
>
> > in tandem with this technique, however, at least the
> > sighted keyboard surfer can still get a feel for where
> > they're at.
>
> AFAIK, the dotted outline is only useful to the sighted.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

yes, which is why i qualified my statement by referring to a specific subset
of keyboard users -- the sighted.  i've personally come to rely on the
dotted outline when chasing down information from a page full of links.
when i toggle back to the window with all the links the last one i clicked
on has the outline around it.   it's now very easy for me to find where i
left off.  removing that makes it more difficult.  if the "designer" of the
site chose in his/her infinite wisdom to also make the visited link color
the same as the link color then i'm completely screwed.  i'm not impaired or
disabled in any way (some might argue otherwise) and yet i find myself
relying on this accessibility feature quite a bit.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> The hidefocus property has drawbacks, but focus-bouncing
> is not one of them.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

one of these drawbacks is most certainly one of validation.

the other is the issue i've brought up about.  it's no coincidence that
making something more accessible won't also make it more usable.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> In web design, I have come to the conclusion that there
> are almost always exceptions to even the best of rules.
> By definition, an exception should occur a minority of
> the time.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

couldn't agree more myself.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> One *possible* scenario for removing the dotted line
> around an element:  you have several linked images that
> represent buttons on a button bar in a web-based
> application.  Many standard applications don't provide
> keyboard access to the buttons on button bars, and thus
> don't place a dotted border around a button when it is
> clicked. If you have provided sufficient menu options
> and accesskeys for keyboard users, removing the dotted
> focus line around a button -- and even removing keyboard
> access to the buttons -- could be considered sound since
> the web-based application will function much more
> consistently with standard applications.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

this is a excellently crafted argument for an exception and probably one of
the only ones i'd entertain as valid since the point of removing them from
some items is to maintain consistency with other applications the user is
familiar with thereby improving the usability.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> Also keep in mind that if every browser fully supported
> CSS 2, removing -- or modifying -- the focus outline
> would be as simple as adding hover effects.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

in my opinion, just because we may eventually be able to remove or modify
the outline doesn't mean that we should.  it's been purposely been recreated
to look and behave the same as in other applications.  modifying it takes
away the instant familiarity, replacing it with "huh?  what's this?" from
the user.  with basic navigational aids, that sort of question can be a
showstopper.

thanks,

.jeff

http://evolt.org/
jeff at members.evolt.org
http://members.evolt.org/jeff/






More information about the thelist mailing list