W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2004

Re: screen readers do not seem to see content on page:

From: <cbo@entobox.org>
Date: Thu, 6 May 2004 13:53:12 -0400
Message-ID: <1083865992.409a7b8881ae8@65.19.179.2>
To: w3c-wai-ig@w3.org

Maybe I am missing something here... But the page's content primarily consists 
of an image -- not text. As far as I know, the screen reader isn't supposed to 
read text embedded in a jpeg. That's why we have title, alt and longdesc to 
compensate for those who feel that they need to retain a certain font or 
something else and present their text as images. The text should be text... not 
an image. 

The Untitled Document means that you haven't taken the time to put a title on 
your page. Simply replace the default Dreamweaver setting in the head of the 
document. 

Once the screen reader gets past that, it seems that there is nothing else for 
it to go to and read, save some images w/out descriptions and some inaccessible 
js links. 

Hence the output: 
images/index2_top1
images/index_ovl1
void(null)
void(null)
void(null)

I agree with the previous poster about starting from scratch. And make some 
individual, accessible pages that don't rely on js flyouts and image rollovers 
that contain the core copy for the site.

Quoting david poehlman <poehlman1@comcast.net>:

> 
> Thanks Mark,
> 
> Looking at the source and seeing all the js and styling, I figure something
> is preventing rendering but just what is hard to diagnose for me.
> Here's the output I get.
> Untitled Document
> images/index2_top1
> images/index_ovl1
> void(null)
> void(null)
> void(null)
> And I noticed that it does say that there are errors on the page.
> 
> ----- Original Message ----- 
> From: "Mark Thomas" <mark@carbonchip.com>
> To: <w3c-wai-ig@w3.org>
> Sent: Thursday, May 06, 2004 11:31 AM
> Subject: Re: screen readers do not seem to see content on page:
> 
> 
> 
> David
> 
> I don't have a screen reader to hand, but I'm guessing that it might be
> something to do with the JavaScript. IE6 is generating errors, but still
> rendering the page.
> 
> There does seem to be an awful lot of <script> included in the document - is
> it all necessary? First impressions indicate that the page could be
> streamlined significantly.
> 
> It might be an idea to post the output you are getting from your screen
> reader. The chaps over at www.accessifyforum.com are excellent with screen
> reader issues.
> 
> Mark Thomas
> mark@carbonchip.com
> 
> > -----Original Message-----
> > From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org]On
> > Behalf Of david poehlman
> > Sent: 06 May 2004 16:03
> > To: wai-ig list
> > Subject: screen readers do not seem to see content on page:
> >
> >
> >
> > We've tried three screen readers and three separate systems on
> > the following
> > page and cannot get any meaningfull text:
> > http://healthyforyou.showmewhy.com
> > is the page.  If anyone can help, the developpers would love to correct
> > this.
> >
> > Thanks!
> >
> > David Poehlman
> > poehlman1@comcast.net
> 
> 
> 
Received on Thursday, 6 May 2004 14:03:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:32 UTC