That is my point, not all these other arguments about where to or where not to use transitional or strict.
However, that *was* the point of the original question. To recap: something can't be done in strict which is not presentational, but nevertheless has been dropped from the DTD. It can be done in transitional, but some shortsighted policy maker in the company decided that their guidelines should absolutely require strict. Which then prompted the (admittedly more general) question of whether or not strict has any accessibility advantages over transitional so as to warrant it being made mandatory in an accessibility policy.
I still stand by the idea that there is nothing intrinsically more accessible to strict over transitional - and in very rare cases such as this one, transitional *is* more accessible than strict.
-- 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 ****************************************************** The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
