W3C home > Mailing lists > Public > public-html-a11y@w3.org > February 2010

[Bug 8717] Usability and Element-level-focus-apis

From: <bugzilla@wiggum.w3.org>
Date: Tue, 09 Feb 2010 10:56:43 +0000
To: public-html-a11y@w3.org
Message-Id: <E1Nenlr-0002Qo-LT@wiggum.w3.org>

Joshue O Connor <joshue.oconnor@cfit.ie> changed:

           What    |Removed                     |Added
                 CC|                            |joshue.oconnor@cfit.ie

--- Comment #2 from Joshue O Connor <joshue.oconnor@cfit.ie>  2010-02-09 10:56:43 ---
Thanks to Gez for the following example:

There can be usability issues using the JavaScript blur method. Some designers
don't like the dotted rectangle that some browsers place around the
link that currently has focus (either from tabbing to the link, or
clicking through a link and then pressing the back button).

This dotted rectangle is an aid for keyboard only users to
give some kind of visual indication that an element has focus, but
some designers only focus on the mode they're familiar with; using the
mouse to navigate, and rarely think about keyboard only users. Some of
these designers use the blur technique to remove focus so that the
dotted line is removed so as not to ruin their design with
something like:

<a href="..." onfocus="this.blur()">...</a>

The problem with this is that this method effectively renders the page useless
for keyboard users, as it's impossible to navigate to or go past that
link using the keyboard, as the blur method deliberately removes focus
from the element. That could be a typical example that a user agent
would ignore for usability, as this kind of behaviour is not beneficial.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 9 February 2010 10:56:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:08 UTC