From: Jim Stevenson <jims@eos.arc.nasa.gov>
To: raman@Adobe.COM
Cc: blinux-list@redhat.com, linux-access@ssv1.union.utah.edu
Subject: unix, & BeOS?
Date: Wed, 1 Jul 1998 05:12:24 -0700 [thread overview]
Message-ID: <199807011212.FAA14311@eos.arc.nasa.gov> (raw)
I need a white paper that describes what is necessary for an OS to be accessible
and speech friendly,
It should also describe what is necessary to include in a screen reader
for the OS.
I am currently discussing accessibility with the developers of the Be Os.
Does anyone have knowledge of Be?
If you quote me, please put your comments first.
I have already listened to my questions.
Thanks.
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199807011212.FAA14311@eos.arc.nasa.gov \
--to=jims@eos.arc.nasa.gov \
--cc=blinux-list@redhat.com \
--cc=linux-access@ssv1.union.utah.edu \
--cc=raman@Adobe.COM \
/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).