Stevio wrote:
I am interesting in your thoughts on linearization. What it means and
how you apply it?
For all intents and purposes, linearisation = source order.
If you have something like a screenreader, it will read things in the
order in which they appear in the source code. If you a) use a table or
b) use CSS positioning for layout, it's important to check that things
don't just look right, but that they make sense in source order. The
classic table based example can be found at
http://www.webaim.org/techniques/forms/2 (in the context of forms, but
the same principle applies to content laid out in tables).
Basically, make sure that your content makes sense a) when linearised
(you can check for this, for instance, in Firefox with the Web Developer
Toolbar under Miscellaneous > Linearize Tables) or b) when styles are off.
--
Patrick H. Lauke
__________________________________________________________
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com
__________________________________________________________
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__________________________________________________________
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
