public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Rich Caloggero" <rjc@MIT.EDU>
To: <speakup@braille.uwo.ca>
Subject: MSAA for Linux
Date: Mon, 2 Jul 2001 14:10:29 -0400	[thread overview]
Message-ID: <002a01c10322$4975e8c0$4c015112@vantaa> (raw)
In-Reply-To: <001d01c10035$aef9fcd0$0100a8c0@cybertsar>

Well, not exactly MSAA, but something in the spirit of MSAA for linux would
be a *great* thing. MSAA allows a process to ask another process about its
internals. The questions which can be asked and the data which can be
gathered about process  X by process Y are carefully designed to minimize
security concerns and to be particularly useful to a screen reader. To put
it another way, if process X is a screen reader and process Y is, say, a web
browser, then process X is going to want to know a bunch of things about
process Y in order to allow a blind user to interact with it. Actually, if
process X could just get hold of the parsed html (this tree is usually
called the document object model - DOM), then the screen reader would be
able to do great things. If you look at the jfw scripts for internet
explorer, there is a call which returns a DOM object. The function called is
not defined anywhere in JFW; its a magic call  made posible by MSAA.
As fare as I know, the ultrasonix screen reader for X-Windows is based upon
similar technology. With X, however, implementing a protocol which can allow
any process to gather this kind of information from another process is
complex and risks exposing too much, making security a problem. There are
other issues too which I'm not really up on, but I do believe that X now has
RAP and ICE protocols (romote access protocol, and I'm not sure what ICE
stands for), but I'm not sure how fully developed they or ultrasonix are at
present.
Can anyone shed more light on this?

                    Rich




----- Original Message -----
From: "Victor Tsaran" <tsar@sylaba.poznan.pl>
To: <speakup@braille.uwo.ca>
Sent: Thursday, June 28, 2001 1:17 PM
Subject: Re: NICHOLAS PETRELEY: "The Open Source" from InfoWorld.com,
Wednesday, June 27, 2001


> I think this is a very interesting article. How do we, VIP, benefit from
the
> powerful and yet easy-to-use KDE version 2.1? Unfortunately, we can see it
> happening more often that more and more programs are written for X-Window.
> Don't tell me there are console alternatives for every GUI program, this
is
> no longer true. MSAA for Linux is what we need!
> Best,
> Vic
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  parent reply	other threads:[~ UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 FW: NICHOLAS PETRELEY: "The Open Source" from InfoWorld.com, Wednesday, June 27, 2001 Stephen Dawes
 ` Victor Tsaran
   ` David Poehlman
     ` Janina Sajka
       ` David Poehlman
         ` Janina Sajka
           ` David Poehlman
             ` Using an appropriate USB 56k modem Will Smith
               ` Ann Parsons
             ` NICHOLAS PETRELEY: "The Open Source" from InfoWorld.com, Wednesday, June 27, 2001 Gregory Nowak
               ` Frank Carmickle
                 ` Gregory Nowak
               ` Geoff Shang
                 ` Gregory Nowak
               ` David Poehlman
   ` Kirk Wood
   ` Geoff Shang
     ` Georgina Joyce
   ` Rich Caloggero [this message]
     ` MSAA for Linux Kirk Wood
     ` Saqib Shaikh
       ` linux on a mac with speech Angelo Sonnesso
         ` Saqib Shaikh
     ` MSAA for Linux Scott Howell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002a01c10322$4975e8c0$4c015112@vantaa' \
    --to=rjc@mit.edu \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).