W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2007

RE: How do our SC do when rating these two examples?

From: Bailey Bruce <Bailey@Access-Board.gov>
Date: Wed, 22 Aug 2007 12:53:45 -0400
Message-ID: <23EB0B5A59FF804E9A219B2C4EF3AE3DBB1A9F@Access-Exch.Access-Board.gov>
To: "Chris Blouch" <cblouch@aol.com>
Cc: "WCAG" <w3c-wai-gl@w3.org>

Annoying is too gentle a characterization IMHO.  I concur that your
suggested modification would be a noticeable improvement.  Would that be
enough for enough people though?  And what SC is satisfied by such a
modification?

My motivation in bringing this question up is less for work-around and
more as test to see if the SC catch this kind of accessibility barrier.
Having AT freeze the page is a solution too, but I think anticipating
such AT functionality is not sufficient justification for neglecting
this real-world problem.


-----Original Message-----
From: Chris Blouch [mailto:cblouch@aol.com] 
Sent: Wednesday, August 22, 2007 10:31 AM
To: Bailey Bruce
Cc: WCAG
Subject: Re: How do our SC do when rating these two examples?

This is annoying in general in that the very instant I mouse off the
image the popup leaves.  What would be more ideal is a 500ms timer on
the popup hide function.  This would allow you to refocus on the popup
and that focus would cancel the pending hide.  This gives a much more
forgiving navigation in general and would solve the screen magnification
issue. What's funny is that mousing over the 'wedge' which forms the
thought balloon still retains the popup's state, but beyond the wedge
into the main body of the balloon pops it.

CB
Received on Wednesday, 22 August 2007 16:51:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:50 GMT