I don't see why the Admins should bother fixing that. Sure, it's not really difficult, but it does take quite some time and I don't think anyone is going to complain that we don't comply to the W3C guidelines
I think it would be good to update the code in small steps... one thing I know works using dreamweaver, is that you can search for a string and replace it with another... nothing new, But: You can choose to do it in all the files in the working directory and subdirectories and stuff... then, searching for
and replacing with
will get rid of a good few of those errors.
And those of you who ask if it's true and what not: It's the W3C, those who made the standards. so It is accurate.
Sure there are many many "errors" and it still works, but things like alt attributes to link areas will help those who rely on hearing etc. and also, doing some maintenance on the code a little at the time isn't as bad as trying to fix it all
EDIT: Just to make sure: I don't say that anyone SHOULD do this... I'm saying that it could be a good idea to make sure the compatibility is as good as it possibly can, some time. It is a lot of work, and all... but as I said, a few of these errors are rather easy to iron out. the search and replace of
, and also saw that the text for the spoiler tags "warning: spoiler alert" or what it was.. starts with and ends with just making sure that it is lowercase can also be done with a search and replace