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

RE: strange reader behaviour in form elements

From: Charles McCathieNevile <charles@sidar.org>
Date: Fri, 7 May 2004 09:35:35 -0500 (CDT)
Message-ID: <3919.>
To: "Jim Thatcher" <jim@jimthatcher.com>
Cc: "'Scarlett Julian'" <julian.scarlett@sheffield.gov.uk>, w3c-wai-ig@w3.org

Right. I believe that some other Windows screen readers are designed more
generally, to take maximum advantage of whatever accessibility stuff is in

Talking to other screen reader developers, it seems that isn't as easy as
it should be :(

For many screen readers you can write a profile to get them working better
with whatever application you think of. But I would suggest that one of
the things to test is whether Firefox is putting information out to MSAA
properly, by checking with some MSAA-based system. (I don't know if there
is one, or if you'd need to look around for testing software. Aaron
Leventhal might have the answers you're looking for. He hangs out in



Charles McCathieNevile           charles@sidar.org

<quote who="Jim Thatcher">
> Sure any screen reader should not crash, and most text should be
> available,
> with any Windows application, but to "work with" is quite another story.
> Someone referred to MSAA in this thread. In fact JAWS uses the IE DOM and
> parses the HTML. More and more screen readers are accessing the private
> information of the application. That wasn't true in my screen reader for
> OS/2 days but it was essential to tailor the careen reader, to have made a
> "profile," for any application you really wanted to use.
> Jim

> -----Original Message-----
> Hhmm... hadn't thought of that. Surely JAWS is *meant* to work with
> anything
> that is text-based on a Win machine.
> Is there a reader that is independent of MSSA that I could use as a test?
Received on Friday, 7 May 2004 10:37:12 UTC

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