Post "Likes" and W3C validity « Support Forum | Kriesi.at

Support Forum » Flagship

Post "Likes" and W3C validity

4 posts from 3 voices

Started 7 months ago by jobsource1
Latest reply from Devin
This topic is resolved

Tags:

jobsource1
Member

Hi,

I'm working through the site fixing html so it meets W3C standards. I'm having a problem with the archive pages. The errors the W3C validator returns are as follows:

Line 213, Column 136: & did not start a character reference.

Line 213, Column 1557: Bad value category tag for attribute rel on element a: Keyword category is not registered.

Line 213, Column 1715: Bad value category tag for attribute rel on element a: Keyword category is not registered.

These errors repeat for all blog posts. You can see the full list of errors, with more details, here:

http://validator.w3.org/check?uri=http%3A%2F%2Fwww.jobsource.ie%2Findex.php%2Fvacancies%2F&charset=%28detect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.3

I want to remove all possible W3C issues, but I don't know how to address these problems.

Any help would be greatly appreciated.

Posted 7 months ago #
Nick
Moderator

Hi,

Please read the warning on that website "be aware that it may be unreliable, or not perfectly up to date with the latest development of some cutting-edge technologies."

Those are not errors since HTML5 has never been formalized nor standardized, and that process should conclude by late 2014 . Even their regular validator is full of bugs (padding: 20 0 0 0; will always come up as an error even though its just as valid as padding: 20px 0px 0px 0px according to their own standard). That's why Amazon, Ebay, Google and Yahoo fail with hundreds of errors on each page.

http://wordpress.org/support/topic/wordpress-abuses-rel-tag

http://stackoverflow.com/questions/6188878/validation-error-bad-value-apple-touch-icon-precomposed-for-attribute-rel-on-el

Please read the explanation from Wordpress moderator and Stackexchange senior members regarding this issue.

Thanks,

Nick

Posted 7 months ago #
jobsource1
Member

Thanks for the info. I could tell from the look of both elements that the code and its syntax couldn't be changed, and as long as there are no <i>unavoidable</i> W3C errors I'm happy. Thanks again for your help.

Posted 7 months ago #
Devin
Moderator

Glad Nick could shed some light on it for you :)

Regards,

Devin

Posted 7 months ago #