WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: screen readers constantly saying "clickable" with onMouseDown Javascript in a table, is there a better design recommendation for this?

for

From: Vincent Young
Date: Dec 5, 2011 12:18PM

I would consider adding role="button". I know the function is obvious to
most but I've never liked links used in this way.

On Mon, Dec 5, 2011 at 11:11 AM, Jim Allan < <EMAIL REMOVED> > wrote:

> If you find a way eliminate the word 'clickable' you have also removed a
> primary way that the screen reader user knows that an action can be
> performed at a particular location. Perhaps you could make these table
> headers actual links with some javascript attached that does the sorting
> (that would substitute 1 syllable 'link' for 3 syllables 'click-a-ble').
> Also, the sort functions would show up in a links list and the user would
> know the range of functions that are possible in the table (most users know
> how to get a links list). Though the latest version of Jaws has a 'list of
> clickable' elements your average user is not likely to have Jaws 13 nor
> know the command (insert-control-slash)
>
> On Mon, Dec 5, 2011 at 12:02 PM, Ro < <EMAIL REMOVED> > wrote:
>
> > From a screen reader user's standpoint, using Voiceover, I can change the
> > verbosity settings to eliminate the word clickable. Unfortunately,
> getting
> > rid of this word eliminates other useful words for me, so it would be
> great
> > if there's a fix. However I encounter the word on nearly every website I
> > access.
> >
> > I just wanted to offer that point of view because in my opinion, it's not
> > always the developers' responsibility to eliminate things, especially if
> > they are necessary, if we as screen reader users, can change it.
> >
> > ~Ro
> >
> > On Dec 5, 2011, at 8:25 AM, Birkir R. Gunnarsson wrote:
> >
> > > Hi all
> > >
> > > I am working with a library page (in Icelandic admittedly).
> > > The page is
> > > http://hbleit.bbi.is/
> > >
> > > To get a sample of a table, type in "Auel" (or any other author you
> > > fancy) in the search field and hit enter (leit = search).
> > > The resulting interface table is a bit clumsy but it does work.
> > > There is a lot of "fancy" drag and drop functionality going on, but
> > > there is sufficient keyboard support to get it done.
> > > The problem I am having with this, and the users complain about, is
> > > that the word "clickable" is read for practically every column,
> > > because there is an onMouseDown event associated with almost every
> > > column and value.
> > > When an Icelandic tts voice is used, but the word clickable is not
> > > translated, you end up with a minor, but irritating user distraction.
> > > I have looked at accessibility commentary for "onMouseDown" but it
> > > only suggest implementing appropriate keyboard support, which is not
> > > the issue, but I can't find anywhere how one could prevent it from
> > > being "vissible" to the screen readers.
> > >
> > > Is it possible to either use a different type of event, use ARIa to
> > > hide this functionality, or would you simply recommend a more major
> > > overhaul of how this search result table is implemented?
> > > (the last 3 columns in the result table have options like "add to wish
> > > list" "download" and "order on cd").
> > > We have the vendors attention at the moment, especially for small
> > > accessibility repairs.
> > > I know, in the perfect world, this whole set up should be recoded, and
> > > it is on the agenda for next year, but if there is a quickish type of
> > > fix that could be implemented to prevent the word "clickable" from
> > > being read constantly, it would be a feather in my cap and no misatke.
> > > Thanks all.
> > > -Birkir
> > >