Skenow is correct on this one,

Theme developers are usually much more adept to compliance than module devs.

We cant blame them though, they already spend countless hours writing the backend, that when they get to the user side... well you get the idea.

Ideally module authors should care enough to consult designers. Though this hasn't become commonplace as of yet.

Your best bet is to either rewrite all the templates, while doing so make sure you plan on theme swaps, or hope someone does as skenow has suggested.

Personally I have done quite a bit of work on some of the templates that I use regularly. I think that I will look into forwarding what I have done to the module authors as well.

First of all, we must define and propose a naming of the selectors Css for the core and the modules.
Zetareticuli, morphogenesis, XOOPS 2.3, go in this direction

Quote:

Yeah, if your read the errors you can look at page source to figure out which module pages not compliant. Then you can edit the templates to fix. Working this way I reduced my home page down to 2 errors from 40.

Also, if you put images in news stories and things you need to add alt tags. So, content can cause not valid to.