“The idea of equal access, equal opportunity has sort of evolved in its application from brick and mortar to eCommerce. At first, many companies were worried about the desktop experience. Now, the concern extends to both smart phones and devices.  Wherever a consumer accesses your content – whether it be directly through the web or an app – you need to be concerned about accessibility.”
more than the list of websites, I appreciate the 10-second method you describe. I think it's worth explaining to developers and site owners that there are indeed some simple tricks to quickly assess a web page without having a deep understanding of the WCAG. Personally, I like removing all the CSS styles (with the Web Developer Toolbar in Firefox, shortcut is Shift+Ctrl+S). If the page is still pretty readable, with no clumsy technical code; if it shows a neat heading structure; if lists appear well structured and appropriately used; if all text, is in black (except links), left-aligned, and with its default font and size; then it's been probably properly coded, HTML-wise.

The ruling references the Web Content Accessibility Guidelines (WCAG) 2.0 created by the W3C’s Web Accessibility Initiative. The World Wide Web Consortium (W3C) describes itself as “an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.” The complete Web standards for ADA accessibility can be found here.
This guidance document is not intended to be a final agency action, has no legally binding effect, and may be rescinded or modified in the Department's complete discretion, in accordance with applicable laws. The Department's guidance documents, including this guidance, do not establish legally enforceable responsibilities beyond what is required by the terms of the applicable statutes, regulations, or binding judicial precedent.