WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Lynn Holdsworth
Date: Feb 6, 2015 2:47AM

Thanks for your comment Ron. The site will be tested using various AT
and browser combinations. However, being blind I need to choose a
screenreader with which to do the bulk of the testing (my day job),
and JAWS is my screenreader of choice. I'm aware of the extra
accessibility hacks it introduces, and I constantly examine the markup
to compensate for this.

Best, Lynn

On 05/02/2015, Ron Stewart < <EMAIL REMOVED> > wrote:
> On the inverse a sites functionality with JAWS also does not insure that
> the
> site is accessible. JAWS is a very powerful and very expensive software
> program, that can brute force its way through accessibility errors in a
> site. For the visually impaired I actually recommend you do your testing
> with NVDA, Voiceover and perhaps CromeVox. You also need to insure the site
> will work for other users of assistive technology such as Voice Recognition
> users and users of alternative input devices. The first step is to insure
> that the site is WCAG 2.0 AA compliant but also that it is tested by actual
> users of AT.
>
> I have reviewed quite a variety of sites that worked with a screen reader,
> but when colors were inverted such as for a low vision user significant
> portions of the content disappeared. Or that they could be effectively
> navigated by someone with a sensory disability but a user with mobility
> issues could not effectively navigate the site with their voice or their
> screen based keyboard.
>
> Ron Stewart
>
> -----Original Message-----
> From: <EMAIL REMOVED>
> [mailto: <EMAIL REMOVED> ] On Behalf Of Léonie Watson
> Sent: Thursday, February 05, 2015 8:46 AM
> To: 'WebAIM Discussion List'
> Subject: Re: [WebAIM] JAWS cursor doesn't work in Firefox or Chrome
>
> " Hm, if the site is so inaccessible that the accessiblity tester can't
> even
> test it, isn't that right there an automatic fail?"
>
> Needing the Jaws cursor isn't necessarily a sign of inaccessibility. You
> use
> it to move the mouse pointer over specific objects in the UI, so you can do
> things like ascertain the colours being used, or pull up the context menu
> to
> open tools like Firebug etc.
>
> It can also be used when you need to simulate mouse interaction because
> there is no keyboard support available of course.
>
> Léonie.
> --
> @LeonieWatson Tink.UK Carpe diem
>
>> -----Original Message-----
>> From: <EMAIL REMOVED> [mailto:webaim-forum-
>> <EMAIL REMOVED> ] On Behalf Of _mallory
>> Sent: 05 February 2015 15:02
>> To: WebAIM Discussion List
>> Subject: Re: [WebAIM] JAWS cursor doesn't work in Firefox or Chrome
>>
>> Hm, if the site is so inaccessible that the accessiblity tester can't
>> even
> test it,
>> isn't that right there an automatic fail?
>>
>> I mean, would they expect general users to use the cursor to find stuff?
> Or is
>> it more so you can point specifically to "area x with these words" to
>> the developers?
>>
>> _mallory
>> >> >> list messages to <EMAIL REMOVED>
>
> > > messages to <EMAIL REMOVED>
>
>
> > > >