- From: <gian@stanleymilford.com.au>
- Date: Mon, 18 Mar 2002 17:29:26 +1100
- TO: lguarino@adobe.com
- CC: w3c-wai-gl@w3.org
- Message-Id: <H00000e000400d37.1016432965.tux.sofcom.com.au@MHS>
OK- good point. Another example is that PDFs are not manipulable (for want of a better term). Someone with vision impairment that browses in point 34 font and white text on a black background will find the PDF inaccessible. > -----Original Message----- > From: lguarino [mailto:lguarino@adobe.com] > Sent: Friday, 1 March 2002 4:59 PM > To: Gian Sampson-Wild > Cc: w3c-wai-gl > Subject: Re: 'Non-economic' rationale for backward compatibility > > > Gian, > I'm confused by this example. The author can provide alternative > descriptions for images in PDF files, just as he can for HTML files. > If they are present, they are exposed to screen readers and other > assistive technologies. Requiring these descriptions is one of the > WCAG PDF techniques. > Loretta > > > > 4. Technologies that have been built for accessibility > often only focus > > on one area (needs rewrite) > > For example there has been a lot of discussion about the > latest Adobe > > version being compatible with screen-readers, however if > the document > > has images in the text then these images can't be > represented through a > > screen-reader (unless an alternative exists). > > >
Received on Monday, 18 March 2002 01:31:40 UTC