0) Make sure all of your HTML is valid.
For instance, the WGAC 2.0 guidelines require that HTML be valid, and if a client wants WGAC 2.0 compliance (even A level, not AA), the site's gotta validate [1].
[1] http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-pars...
http://www.alistapart.com/articles/tohellwithwcag2 "To Hell with WCAG 2" (2006)
[1] cover your ass engineering
Too many people build something that works for them; on their browser version, at their screen size, on their OS.
That's especially harmful for accessible sites.
invalid code doesn't mean shitty code, and the other way around - being valid doesn't say anything about the practical quality of code. know your craft = know the rules + know when you can break them.