HTML Validation Errors?

Question

Hey Guys, I tried my site for w3c validation, but Now i am unable to solve last 10 errors, can anybody pls help me .. validation link is http://validator.w3.org/check?uri=http://www.yourwebcoders.com/&charset=(detect+automatically)&doctype=Inline&group=0&accept=text/xml,application/xml,application/xhtml%2Bxml,text/html;q%3D0.9,text/plain;q%3D0.8,image/png,*/*;q%3D0.5&accept-language=en-US,en&accept-charset=ISO-8859-1,*,utf-8&user-agent=W3C_Validator/1.591

i would highly appreciate your help ..

thanks ..
vrajesh

Answer 1

OK. Here we go...



First, I'm amazed there are only ten errors. I think there's really going to be more, especially when you go to strict (as you really should.)



Here's the ones I get

61 - Comments must have spaces If that doesn't help, you might just take them out. They aren't doing you a lot of good here.



62 - You haven't closed off your previous so you can't start an new This error is replicated a lot.



235 - You should be using CSS to manage color (but you shouldn't be using hr at all - use the CSS border attribute instead)



276 - table doesn't have a height attribute (even though IE6 supports it. You should really be using CSS for layout rather than tables.



298 - Use CSS instead of bordercolor attribute



301 - Marquee is a non-standard element - it should be removed altogether. This also solves scrolldelay problem



367 - End the object tag with a While you're at it, consider how important the flash is to your site.



It's time to get rid of HTML and table-based design. I applaud you for validating your page, but I encourage you to go the distance, and switch to an XHTML strict format with CSS for all styling. It will take some adjustment, but you'll create pages that look just as good, but are more reliable and easier to maintain.



In the mean time, investigate HTML tidy, which can automatically clean up your code so it validates: There's an online version at:

http://infohound.net/tidy/



Good Luck!

Answer 2

Line 2, Column 12: there is no attribute "XMLNS". - This is caused by the tag being . Your document doctype is HTML, but the xmlns tag is only used if your doctype is XHTML. So either change your doctype, or remove the xmlns attribute completely.



Line 8, Column 77: NET-enabling start-tag requires SHORTTAG YES. This is caused by some problems with HTML compatability. You are closing a meta tag with but in HTML the closing / is not needed.



Line 9, Column 55: document type does not allow element "LINK" here.; Line 17, Column 6: end tag for element "HEAD" which is not open.; Line 19, Column 5: document type does not allow element "BODY" here. - These three bugs are all caused by problems in the validator, and once you fix the bug above, they will all go away.



Line 235, Column 29: there is no attribute "COLOR".

This is caused by a sematic error. You are trying to set a color on a horizontal rule, remove the color attribute to fix this.



Line 276, Column 18: there is no attribute "HEIGHT". - This error is due to a common problem. In HTML there should not be a height on a table. The height of the table should always be based upon the height of the content inside of it. If you need to set a height on a container use a DIV instead. If you don't then just remove the height attribute.



Line 298, Column 91: there is no attribute "BORDERCOLOR". - Border color cannot be called in this manner. Simply replace the tag here with rather than mixing CSS and HTML.



Line 301, Column 29: there is no attribute "SCROLLDELAY";Line 301, Column 34: element "MARQUEE" undefined.. - These bugs are going to be a bigger issue. Marquee's are not valid. Period. You are going to have to accept this error, or replace your scrolling marquee with some javascript code that emulates it's functionality. There isn't any other option in place.



Line 427, Column 123: document type does not allow element "NOSCRIPT" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag. - This last one has me stumpped. I'm really not sure what it's cause is. Maybe you'll get lucky and it is being caused by one of the errors above.

Answer 3

try another time maybe?, maybe something is down