No browser is completely compliant with every existing web standard, certainly not Safari. Acid3 is just a small set of tests (many of which were written specifically to break Firefox) that are meant to measure compliance with some standards. It's definitely not a de-facto tool to judge whether a browser is or is not standards compliant.
Regardless, I disagree with the very idea of the Acid3 test; finding a few ways a browser mistakenly implements a standard means next to nothing, especially when the developers start fixing that small subset of bugs you've found (instead of fixing larger problems relating to the standard in question). I have more respect for browser developers, like Firefox's and Konqueror's, who aren't focusing specifically on fixing the bugs found in Acid3; than for those teams who have been scrambling to fix Acid3 bugs so they can market their browser to anyone who's heard of the test (and, in turn, anyone they market it to).
And those administrators shouldn't complain about DTA's aggressiveness if they aren't providing a similar functionality on their sites. If I'm forced to go out and grab an addon for a functionality your site should already have, you've no right to complain about it being too aggressive.
