Accessibility is tricky. For instance, one of the largest things that HTML tables break is the linear flow of the page. For people using screen readers or text-only browsers it becomes far, far more difficult to understand the content of a page.
CSS tables can be applied with consideration only against the hierarchal structure of the page allowing you to write pages that are accessibly legible yet stylish.
That is unless you want to make whole new versions of your site for any number of accessibility domains: modern browsers, IE 6-, blind people, lynx, mobile browsers, mobile safari, colorblind people, &c. Good luck with SEO on all of those, too.
Regardless, use of tables means absolutely jack * as to whether real life sites are "accessible." Lots of this anti-table stuff makes sites less accessible to regular users.
Avoiding table based layouts is not the definition of accessibility and I never implied that. They are frequently a symptom of poor accessibility, however, and then they almost always obscure the intended hierarchy of a page which defeats accessibility for text based browsers and screen readers and messes with SEO.
You think that not using tables will just automatically give you loads of accessibility? It won't.