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

It appears that this page was in fact made with Dreamweaver.. so, i don't think 
a programmer did it at all. the js rollover script variables are preceded with 
an MM -- Macromedia Dreamweaver does this. 

Quoting david poehlman <poehlman1@comcast.net>:

> 
> you mean wiziwig tools can't just slap this up?
> 
> ----- Original Message ----- 
> From: "Steven Dale" <sdale@stevendale.com>
> To: <cbo@entobox.org>
> Cc: <w3c-wai-ig@w3.org>
> Sent: Thursday, May 06, 2004 2:24 PM
> Subject: Re: screen readers do not seem to see content on page:
> 
> 
> 
> It looks to me like this page was designed by a programmer and not a web
> designer.  The designer does great detail in the coding of the javascript
> and the fancy layering work,  yet, misses the basic page title
> information.
> 
> I think basic web design best practices needs to be learned before the
> accessibility features can be understood here.  Granted, filling in the
> proper page title isnt difficult to understand.  But, I tend to believe
> this site is basically a "programmed document" and not really a website.
> 
> I am not being disrespectful here,  I appreciate the work that went into
> this site. I just think it misses the basic idea of HTML.
> 
> -Steve
> 
> >
> > 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:43:43 UTC