E-mail List Archives
Re: Re[2]: Re[2]: Dayton Art Alternative Descriptions
From: Philip Kiff
Date: Nov 12, 2004 6:14AM
- Next message: Patrick Lauke: "Re: Re[2]: Re[2]: Dayton Art Alternative Descriptions"
- Previous message: michael.brockington: "Re: Re[2]: Re[2]: Dayton Art Alternative Descriptions"
- Next message in Thread: Patrick Lauke: "Re: Re[2]: Re[2]: Dayton Art Alternative Descriptions"
- Previous message in Thread: michael.brockington: "Re: Re[2]: Re[2]: Dayton Art Alternative Descriptions"
- View all messages in this Thread
> > Well, can't vouch for all screen readers, but certainly JAWS
> > (4.02 anyway) ignores the "visual" order on screen and reads
> > out the document exactly as it's marked up in the source
>
> That's useful to know, but merely enhances the problem: where
> do you put a skip-nav / skip-content link if you can't gauruntee
> that the two blocks will be in the same order for all users?
I hadn't thought about this before as an issue. I don't know about these
other browsers you mention that imitate the order of the positioning
produced by CSS positioning instead of merely following the order of items
in the underlying code itself. The screen readers I know a bit about are:
JAWS, Window-Eyes, and IBM Home Page Reader (this last is a browser, not a
full screen reading program). These all read page content linearly, based
on the actual HTML/XHTML code, I think. Are these other screen readers or
aural browsers or whatever much used currently? I'm not familiar with them.
Phil.
- Next message: Patrick Lauke: "Re: Re[2]: Re[2]: Dayton Art Alternative Descriptions"
- Previous message: michael.brockington: "Re: Re[2]: Re[2]: Dayton Art Alternative Descriptions"
- Next message in Thread: Patrick Lauke: "Re: Re[2]: Re[2]: Dayton Art Alternative Descriptions"
- Previous message in Thread: michael.brockington: "Re: Re[2]: Re[2]: Dayton Art Alternative Descriptions"
- View all messages in this Thread