I don't think being able to parse invalid CSS (intentional or otherwise) counts as standards compliance. In fact, shouldn't broken code just be ignored by a perfectly compliant browser? In my opinion at least, it should; it shouldn't try to "fix" the problem in its output. So you could have a perfectly standards-compliant browser that fails the Acid2 test, no?