WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Re[2]: Re[2]: Dayton Art Alternative Descriptions

for

From: michael.brockington
Date: Nov 11, 2004 8:58AM

> -----Original Message-----
> From: p.h.lauke [mailto: <EMAIL REMOVED> ]

> > As a further complication, I believe it is a fairly common
> > practice to use
> > CSS positioning to move a block of content links from the end
> > of a document
> > to a side margin, in this case the links are effectively at
> > both ends of the
> > document, depending on whether a screen reader is used on top
> > of a visual
> > browser, or a non-CSS browser is used.
>
> Sorry, but...wouldn't the screen reader still read it out in
> the order in which it appears in the markup, regardless of
> any CSS positioning?

My understanding is that this is the primary difference between designing for
a Screen Reader, and designing for an Aural Browser; the latter read the HTML
(and ignore the CSS) while the former interpret the output of the underlying
application, such as IE, and therefore read pretty much exactly what is
displayed on screen, as modified by CSS and Javascript where present.

The two categories of device do tend to get lumped together a lot, which
complicates matters a lot, perhaps that was what confused you, or perhaps I
have got it wrong for the same reason?

Mike


********************************************************************

This email may contain information which is privileged or confidential. If you are not the intended recipient of this email, please notify the sender immediately and delete it without reading, copying, storing, forwarding or disclosing its contents to any other person
Thank you

Check us out at http://www.bt.com/consulting

********************************************************************