I have just purchased some new sites and have started optimising them and just ran a check on the html content using an automated checker http://validator.w3.org/check?uri=http://www.121sexfinder.com/ Code (markup): When I ran the checker it failed on 23 counts throughout the site. However what is even worse is that it identified 92 errors in the code for example …';exit=false;return true" onMouseOut="self.status='';"><img src="/images/skin Code (markup): it says this attibute onMouseOut is not supported for this document type. Can anyone advise me as to whether this is due to updates in the html standards? There are many more unsupported attributes listed and I will remove them where they have no affect on the page. My question is should I make all the changes or is there a better tool I should use? I have 27 new sites to check and with this number of errors clearly I'm going to be busy but I wnt to be going in the right direction and would appreciate any advice. Paul
For best accuracy, I'm afraid you'll have to go through each of your websites and try to pass the validation, then correct any errors brought to your attention. If you believe that it's worth investing time into it.
Quite simply put, both onmouseover and onmouseout are not xhtml valid at this point in time; and I don't think there is a valid form of them at this point either. HOWEVER, they should be simply listed as validation "warnings" and not validation "errors"; they should be fine for alternative users as long as it's not affecting navigation (which generally speaking, most sites just use it to swap out images whereas the link text that may be associated with it is commonly still visible to the browser)
Hi Clive, thanks for your input, I do think its worth my time so I will start working on them. Just checked a few of the others I got designed for me and unfortunately my best seller has 101 errors guess I'm going to be busy for a while. Thenks Gremelin, so if I understand you correctly I can leave the onmousover and onmouseout warnings in there as they should not affect navigation. Is my understanding correct? Paul
What does your understanding say about the following fact: www.google.com - 79 Errors, 14 warning(s). W3 Validation Failed. Yet, this doesn't seem to be affecting their ranking or influence their business priorities in any way... So how come they can stay calm about this, and we can't? Just a thought Would we not want to follow their model? I personally definitely would.
I use validation to ensure users with alternative browsers (special needs) can freely access my sites; a simple "on mouse over" event likely wouldn't affect things for the user as long as it isn't hugely intrusive (and in any case, it's a simple warning which their reader should ignore in the first place)