WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JAWS cursor doesn't work in Firefox or Chrome

for

From: Léonie Watson
Date: Feb 5, 2015 5:02AM

" Obviously if anyone has a solution I'd love to hear it. But I've spent
3 hours this morning searching, tweaking, restarting and failing."

Unfortunately it's been this way with Jaws and Firefox for several versions
of both the browser and the screen reader. It has to do with the graphics
engine Mozilla uses in Firefox I think.


Chrome isn't officially supported by Jaws, so I'm not sure there's any
expectation that the Jaws cursor should work there.

FS is aware of the Firefox problem. Please contact them to let them know
you're finding it a problem though - as with all software and bugs, the more
people that raise the issue the better.

Léonie.
--
@LeonieWatson Tink.UK Carpe diem

> -----Original Message-----
> From: <EMAIL REMOVED> [mailto:webaim-forum-
> <EMAIL REMOVED> ] On Behalf Of Lynn Holdsworth
> Sent: 05 February 2015 11:34
> To: WebAIM Discussion List
> Subject: [WebAIM] JAWS cursor doesn't work in Firefox or Chrome
>
> Hi all,
>
> This is more of a rant than a question.
>
> I'm feeling totally disempowered and unequal today. I've been asked to
> audit a site that doesn't work in IE (it has a cross-domain login issue),
so
> thought I'd jump ship to Firefox and audit it in there.
>
> It's a very visual site with lots of inaccessible widgets, and I'd usually
use the
> JAWS cursor to find out what's where and what the current value is if
> possible.
>
> But it doesn't work in Firefox.
>
> I searched the web and changed some values in about:config and in FF's
> advanced settings, to no avail.
>
> Enter Google Chrome!
>
> The JAWS cursor doesn't work in that browser either.
>
> So I'm having to pay someone with eyesight to help me identify and
describe
> issues on the site.
>
> That's all. Just feeling as though a previously levelling playing-field
has been
> whipped out from under my feet.
>
> Obviously if anyone has a solution I'd love to hear it. But I've spent
> 3 hours this morning searching, tweaking, restarting and failing.
>
> Thanks for listening!
>
> Best, Lynn
> > > messages to <EMAIL REMOVED>