Kevin I'm sure others will chime in much more richly than I, but there is a simple answer, and it's this - using inline styles breaks the concept of separation of content and presentation.
Your markup, whether a form, a page or whatever, could notionally be stored in any acceptable form and rendered as XHTML or some other publication form (print, screen, audio, etc.) through a transformation process. You want this to be the case for many reasons, not least of which is the ability to potentially "write once, publish many". By including visual rendering information in your form, you pollute the *content* with material not related purely to the content. CSS gives you the ability, as you well know, to completely isolate visual rendering from meaningful content. This of course, provides you with content that is more likely to be able to be machine read, or read by a non-visual rendering engine. The CSS is (largely) a visual rendering instruction set that provides you the ability (if you have your rendering isolated in the CSS) to completely change as and when you see fit. A simplistic answer, but I think a largely correct one. Steve Collins ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
