W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2002

Re: Accessing PDFs

From: Access Systems <accessys@smart.net>
Date: Fri, 25 Oct 2002 10:16:54 -0400 (EDT)
To: Aaron Smith <aaron@gwmicro.com>
cc: David Poehlman <poehlman1@comcast.net>, kestrell <aeryadne@theworld.com>, RUST Randal <RRust@COVANSYS.com>, w3c-wai-ig@w3.org
Message-ID: <Pine.LNX.4.21.0210251009360.21077-100000@smarty.smart.net>

On Fri, 25 Oct 2002, Aaron Smith wrote:

> So, in other words, we should never embrace new technology because older 
> technology already exists? In my opinion, that's a stifling point of view 
> that will never assist in advancing the accessibility market. That line of 
> thinking is part of the reason that accessibility isn't more mainstream. 

the idea is not to "never embrace new technology" but rather to make sure
the information contained in the new technology can still be used by those
with the older technology.....Japan's new bullet trains exceed 200 MPH but
the old Tom Thumb would still be able to run on their tracks....the same
concept...make sure we "Leave no one behind"  

> What's the point of moving from Windows 9X to XP, IE 5 to IE 6, Office 2000 
> to Office XP? Because the latter products have more/better accessibility 
> built in, as well as more general features. Same thing with PDFs. 

you don't want to get me started there....besides I have never run any of
those products why should I degrade my computer...;8*}   but I digress

> Originally, there were not accessible at all. Now they are accessible. 

no they still are not accessible UNLESS you spend $$$ for restrictive
propritary software that constantly has to be upgraded at great expense.
and remember 70% of people with disabilities live below the poverty level,
a computer of any kind is a major purchase and can not be constantly being
upgraded

> Maybe not 100% of them 100% of the time, but to say, "It's not perfect, so 
> let's not use it" violates the whole direction of accessibility advocacy.

nothing is 100% accessible 100% of the time, But I have the same feelings
about people who intentionally build inaccessible web sites as I have for
folks who build new buildings with steps, and putting an accessible door
in the back of the building is NOT making it accessible.

> At 12:21 PM 10/24/2002 -0400, David Poehlman wrote:
> 
> >the problem with this logic is that it totally misses the mark when
> >those documents can just as well be much more accessible by not being in
> >pdf.

can't argue there.  PDF is for printers not for users

Bob
> >
> >----- Original Message -----
> >From: "Aaron Smith" <aaron@gwmicro.com>
> >To: "kestrell" <aeryadne@theworld.com>; "Access Systems"
> ><accessys@smart.net>
> >Cc: "RUST Randal" <RRust@COVANSYS.com>; <w3c-wai-ig@w3.org>
> >Sent: Thursday, October 24, 2002 9:02 AM
> >Subject: Re: Accessing PDFs
> >
> >
> >The point is that we had to start somewhere. I know for a fact that the
> >IRS
> >are working on accessible PDFs, as are other government agencies. The
> >more
> >we spread the information that there is a way to make PDFs accessible,
> >the
> >better the chances that those practices will become mainstream.
> >
> >At 07:29 AM 10/24/2002 -0400, kestrell wrote:
> >
> >
> > >It is also worth noting where the quote accessible unquote pdf docs
> >are:
> > >Of course the screen reader manuals are accessible, because any company
> > >who produced a pdf doc that had any relation to screen readers and did
> >not
> > >assure it was accessible would be crazy, though there are a lot of
> >crazy
> > >company decisions out there. Places to check for accessible pdf docs
> >would
> > >be government web sites, such as the IRS web site, or materials online
> >at
> > >university libraries, or just about any eBook sold in the pdf format.
> >The
> > >rate of inaccessibility just sky-rocketed to about eighty percent
> >there.
> > >
> > >kestrell
> >
> >--
> >To insure that you receive proper support, please include all
> >past correspondence (where applicable), and any relevant
> >information pertinent to your situation when submitting a
> >problem report to the GW Micro Technical Support Team.
> >
> >Aaron Smith
> >GW Micro
> >Phone: 260/489-3671
> >Fax: 260/489-2608
> >WWW: http://www.gwmicro.com
> >FTP: ftp://ftp.gwmicro.com
> >Technical Support & Web Development
> 
> --
> To insure that you receive proper support, please include all
> past correspondence (where applicable), and any relevant
> information pertinent to your situation when submitting a
> problem report to the GW Micro Technical Support Team.
> 
> Aaron Smith
> GW Micro
> Phone: 260/489-3671
> Fax: 260/489-2608
> WWW: http://www.gwmicro.com
> FTP: ftp://ftp.gwmicro.com
> Technical Support & Web Development
> 
> 

   ASCII Ribbon Campaign                        accessBob                       
    NO HTML/PDF/RTF in e-mail                   accessys@smartnospam.net       
    NO MSWord docs in e-mail                    Access Systems, engineers       
    NO attachments in e-mail,  *LINUX powered*   access is a civil right 
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
THIS message and any attachments are CONFIDENTIAL and may be
privileged.  They are intended ONLY for the individual or entity named
above. If you are not the intended recipient, Please notify the sender as
soon as possible. Please DO NOT READ, COPY, USE, or DISCLOSE this
communication to others and DELETE it from your computer systems.  Thanks
Received on Friday, 25 October 2002 10:17:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:07 GMT