Could do a little extension
that posts the page's source code to a url. Firefox also has "view rendered source" which, if you can hook that, would give you the post-javascript html.
I did write it in Smalltalk - its the only way to get this much done by yourself. It also makes it dead easy to install (one squeak vm, one image, one changes file) and it runs on just about anything. It is also possible to push changes from my dev image on my laptop to the deployed one without taking the app down.
I have many issues with the w3c validator. Installation is fiddly and you have to have all latest C libs on your system (its actually written in Perl with dependencies on a C SGML library which depends on the latest glibc....). The output of the thing breaks my browser when using it on my employer's home page. IOW, you see the big list of errors, click it to go to place in source code and occasionally the browser loses its mind and crashes. I couldn't reliably find errors with it. Additionally, it doesn't classify errors by severity - rather it lists them in the order in which it finds them and I think it complains too much about stuff that isn't that important - like escaping ampersands in urls in href attributes. Nobody bothers to do that and the browsers are more than OK with it.
Structural errors, OTOH, can result in totally broken pages and I really want to fix those.
Other stuff that nothing really catches that well is script syntax errors - we have deployed stuff with minor syntax errors that resulted in very visible error dialogs o some browsers. Something needs to check those.
I appreciate your feedback.
"Whenever you find you are on the side of the majority, it is time to pause and reflect" --Mark Twain
"The significant problems we face cannot be solved at the same level of thinking we were at when we created them." --Albert Einstein
"This is still a dangerous world. It's a world of madmen and uncertainty and potential mental losses." --George W. Bush