W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2004

Re: RE: strange reader behaviour in form elements

From: david poehlman <poehlman1@comcast.net>
Date: Fri, 7 May 2004 13:04:09 -0400
Message-ID: <000101c4345c$f8826ff0$6401a8c0@DAVIDPC>
To: "P.H.Lauke" <P.H.Lauke@salford.ac.uk>, <w3c-wai-ig@w3.org>

it's simply that freedom has not put support into jaws for anything but ie
on the browser front for quite some time I think the last netscape version
they actually supported was v 4.75.

If an application uses msaa, jaws or another msaa enabled screen reader
still has to hook into it with some work from the screen reader development
end.  If an application does not use msaa, this is still the case.  If an
application uses standard windows ui, it is highly possible that jaws will
work with it with maybe a tweek or two that a competent user can perform

----- Original Message ----- 
From: "P.H.Lauke" <P.H.Lauke@salford.ac.uk>
To: <w3c-wai-ig@w3.org>
Sent: Friday, May 07, 2004 12:14 PM
Subject: FW: RE: strange reader behaviour in form elements

-----Original Message-----
From: David Murdoch [mailto:david@clarifeye.com]
Sent: 07 May 2004 14:17
To: Lauke PH
Subject: RE: strange reader behaviour in form elements

>Maybe off topic, but...is JAWS *meant* to work with Firefox (or
>rather, let's turn this around...is Firefox correctly working with
>Windows' MSSA)? It may be an issue on Firefox's end...

JAWS works best with IE (unfortunately) I have never had a problem with
Firefox on Windows or Linux but using JAWS with Firefox requires a
customised script for proper functioning.

There may also be a bug in JAWS 5, my colleague prefers a previous JAWS
version because he has had some problems with the latest one, though I
can't remember them off the top of my head.

David Murdoch
Received on Friday, 7 May 2004 14:00:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:28 UTC