Matthew Pennell wrote:
Until you tell that to someone that knows what they're talking about, and then you look like an idiot. Valid code means the browser has to spend less time figuring out what you meant to write, the page is is more likely to look the same across browsers and platforms, and accessibility AT will have an easier time rendering the content in whatever format it produces.
I'd honestly be quite suprised if having good validating semantic markup didn't improve your search engine rankings for certain queries. It only makes sense for it to do so since the search engine has more knowledge regarding what your site is about.

I know all the other reasons for why you should use validating markup, but people generally don't care and the question was how you would sell it rather than why should you do it. Minor speed increases, accessibility, identical appearance - not sure why but for some reason these aren't generally enough to convince people to spend more just to get a competent developer

    Sometimes I make invalid code with the specific purpose of
    increasing accessibility (ie making it work in as many browsers as
    possible).


Example?
Anything where you're unable to change the html to include conditional comments. Sites that are modelled on css zen garden for example, i've worked on one of those. Myspace themes (ew). I believe the YUI Fonts styles don't validate either.


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to