From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: pdf, javascript, and flash was Re: hello
Date: Sat, 16 Jun 2007 13:10:22 -0500 [thread overview]
Message-ID: <001b01c7b041$9b7fb830$ab00a8c0@tenstac> (raw)
In-Reply-To: <87wsy3n92f.fsf_-_@cox.net>
Javascript really is a bad idea as Chris stated, and so is flash.
Both can be opening connections to anywhere without your
knowledge. They are not secure, period. Many sites will not
work properly with browsers like links even though they have
javascript support.
The adobe situation is far worse. It is becoming an entirely
different platform on its own. Its almost like windows, in fact
it is competition to windows, it's a challenge to own desktop.
Look what google does, it can convert pdf to html but NOT
text, its graphical. Its a total mess. It's huge software and is
buggy.
I could go on and on about these three evil bits of software.
But fundamentally they all assume I am on a PC, also on
windows, and desktop windows. This is not my idea of
information being free. The future does not lie in PCs. It
will be portable devices. None of them handle these types
of "pages" properly. Web sites should be standardized in
such a way that they are not form fit for PCs. There are
some that support mini version pages like WAP format
but that's pretty lame. The information should be just
information, and the protocols should be standard and
generic such that ANY device or process can read them
and re-format them any way necessary. This will never
happen with javascript, flash, or pdf.
All of the above are really used because of the silly need
to make the web more like TV than information, with
all kinds of dizzying adverts, and the use of them is usually
ONLY to make the site look pretty. Wrong reasons to
diverge from the original idea, that there should be a set
of standards that are globally accessible.
I believe in accessibility beyond just for what most
people think, it should allow not only different devices
or browsers, it shoul allow different modalities. The
CONTROLS in particular should not assume that
there is keyboard and mouse. Some very serious work
needs to be done in accessibility standards, and it's
not headed in the right direction.
-- Doug
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
hello Jude DaShiell
` hello Jim Grimsby Jr.
` hello Glenn Ervin
` hello Sina Bahram
` hello Gaijin
` pdf, javascript, and flash was hello C.M. Brannon
` Doug Sutherland [this message]
` Glenn Ervin
` Michael Whapples
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='001b01c7b041$9b7fb830$ab00a8c0@tenstac' \
--to=doug@proficio.ca \
--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).