public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: cpt.kirk@1tree.net
To: speakup@braille.uwo.ca
Subject: Re: GUIs (was Re: A comment on Slashdot)
Date: Tue, 11 Apr 2000 20:32:12 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10004111508130.2718-100000@rocky> (raw)
In-Reply-To: <Pine.GSO.4.21.0004111530080.29668-100000@helen.afb.net>

Janina,

I agree that M$ should provide the offscreen model. This is especially
true since you are not supposed to decompile the software and all. Now I
won't go into software lisince isssues and what is really legal. But if
one were to abide by the letter of the lisence, then I doubt that a screen
reader could be written.

I am also quite familiar with the broken Active Accessibility. I believe
that M$ wants to appear responsible, but they are not willing to put up
the ante. I know for instance that MSAA was broken and they knew it ahead
of time. There was no surprise when IE4 released. It was known and the
decision made to go ahead.

But I think that when a company decides to close their code off from view
they should shoulder 100% of the load in making the code workable to all
who have a need to interface to it. The truth is, that they can and should
do better. They could make keyboard access a requirement. (For that
matter, they could probably make it so that keyboard access just happens
for all things.) They could also make it so that every peice of textual
data is always available. But they have chosen not too.

Part of the problem is that it has been years since there was a true
coordinated development effort in Windows. The project has grown to the
point where it is no longer coordinated. And in case your wondering, no
there is no documentation on the registry that comes anywhere close to
complete. There are branches that developers impliment because they need
to store settings and the programmer is the only one to know what is being
used for what. In some of those cases the programmer has left the company.

I used to be a staunch supporter if M$. I will not spend any of my money
on a product again if given a choice. In fact, I would ask for a refund
for any bundled apps that came on a computer.

Kirk Wood
Cpt.Kirk@1tree.net
------------------

Why can't you be a non-conformist, like everybody else?





  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 [this message]
           ` Scott Howell
           ` Janina Sajka
             ` cpt.kirk
               ` Victor Tsaran
                 ` cpt.kirk
                   ` 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.10004111508130.2718-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).