1. Error: An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
From line 64, column 123; to line 64, column 147
1. This occurs with the logo which you can add in JAlbum Settings for Turtle. According to html5 there should be an alt attribute with an image. Other img's go well. I think alt="Logo" should be added.
2. Error: Bad value generator for attribute rel on element <a: The string generator is not a registered keyword.
3. Error: Bad value generator for attribute rel on element a: The string generator is not a registered keyword.
From line 213, column 172; to line 213, column 254
/a> & <a href="http://lazaworx.com/" rel="generator" target="_blank" data-tooltip="#stt">Turtle
2 and 3 are the courtesy links at the bottom of the page for Jalbum and Turtle. "generator" in the script isn't a right value for the rel attribute. I think it should be rel="external".
I prefer not to change the standard Jalbum/Turtle scripts. Could these errors be resolved in the JAlbum/Turtle scripts?
The logo image doesn't have ALT text, because the skin has no idea what's the image is about (it's added by the user), and the purpose of the ALT text is to provide a clue for those using screen readers. Naturally, I could give an ALT text anyway, but that's "design for robots" - google suggests to avoid -, and the visually impaired people won't be happy with a filename either.
The rel="generator" marks that the links lead to the generator tool, and is accepted by google. Every Wordpress page has the back links this format too:
<a href="http://wordpress.org/" rel="generator">Proudly powered by WordPress</a>
This was necessary to avoid "link spamming" we were accused by Google. Validator isn't up to date every time, and if there's something it coughs up it doesn't mean the page does anything wrong.
Validation is a handy way of making sure you're not making any stupid mistakes - one of the reasons I like Total Validator is that it also checks your links, and warns you if they're pointing to non-existent pages. But there are no prizes for "passing" validation, nor are there any penalties for getting some errors or warnings.
@Laza: at the moment I don't know any issues and I really don't want to come across any.
@Gromit: Yes I know, but when some use non-standard tags or values it will get complicated for the different browsers to view your website the way you intended it to view. Also for the different Search engines that will crawl your pages. What will they do with a unknown rel(ation)? Ignore, fault it. I don't know. That's why I prefer to use the agreed standard. I had a page made in 1999 which viewed perfectly but had almost everything not according to nowadays standard. I can imagine that it will do nothing good for the performance (and I can't proof that either). So I changed it to html5 with a css.
But that's enough discussion for now. I'll just wait till wordpress will apply for 'generator' to be added tot the value list