> -----Original Message-----
> From: m.taylor
> I'm putting together a proposal to convert our website to use css
> and xhtml (including for layout) to improve accessibility and
> move away form having to maintain a separate text-only site (the
> site currently uses tables for layout).
You will not necessarily improve accessibility by using CSS for positioning.
For example, people with older browsers may find your content hard to
access/inaccessible if you use CSS-P + xhtml, depending on how you markup
your site.
You can build an accessible site with html4 + CSS. You can build an
*inaccessible* site with CSS + xhtml. There's more to accessibility than
just the file format.
Be aware that the W3C's standards and guidance do not map exactly onto the
real world. Most (all?) screen readers can handle tables as long as the
content linearises ok. Which it usually does. You shouldn't need two
versions of your site. Experiment for yourself: try the Jaws screen reader
(recommended by RNIB, ISTR) or pwWebSpeak voice browser.
HTH,
Matt
|