From: <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: GUIs (was Re: A comment on Slashdot)
Date: Fri, 14 Apr 2000 20:45:09 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10004142036300.2673-100000@rocky> (raw)
In-Reply-To: <005a01bfa68b$c5d81180$70105b80@wang>
You are right that at least M$ has done something. But I would also remind
you that Netscape isn't the only group not supporting MSAA. Heck, even the
screen readers weren't jumping on that wagon. Hynter-Joyce bypassed it
when they supported IE4 initially. Don't know the company name, but
Window Eyes also was slow to support it. And Daulphin found that not
paying much attention to M$ whims was benificial as well.
While I think Netscape could have done more, it was also fighting to even
stay alive (and failed). Truthfully, Winblows is so convoluted, that I
think screen reading is always going to be somewhat convoluted. Keep in
mind that though MSAA is supposedly part of the OS, support is not
automatic. In my limited view, the OS should be able to deal with reading
any text it creates. Thus, software manufacturers should not have to worry
about being accessible (other then to include such things as keyboard
shortcuts).
DOS applications never took time to be accessible. They sent text off to
the OS and it was done. Same with the console apps in Linux. I would bet
that few (if any) of the apps you use in Linux ever had blind accesibility
as a part of their design criteria. It should be built in by running on
the accessible OS.
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Why can't you be a non-conformist, like everybody else?
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
A comment on Slashdot that concerns me Martin G. McCormick
` GUIs (was Re: A comment on Slashdot) cpt.kirk
` Janina Sajka
` cpt.kirk
` Mike Gorse
` cpt.kirk
` Janina Sajka
` cpt.kirk
` Scott Howell
` Janina Sajka
` cpt.kirk
` Victor Tsaran
` cpt.kirk [this message]
` Victor Tsaran
` cpt.kirk
` Matthew Campbell
` Janina Sajka
` A comment on Slashdot that concerns me Tommy Moore
GUIs (was Re: A comment on Slashdot) Martin G. McCormick
` Christopher Moore
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=Pine.LNX.4.10.10004142036300.2673-100000@rocky \
--to=cpt.kirk@1tree.net \
--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).