The use of checklists, when conducting accessibility testing, is sometimes seen as controversial. Some view such checklists as stifling creativity. Others suggest that checklists minimize the needs of people with disabilities, who want to access the web, in favor of ticking off checkboxes. And sometimes, checklists created to supplement (or speed) testing against WCAG 2.0, or Section 508, are flawed or inaccurate. Jimmy Chandler's Slideshare presentation, Accessibility is not a Checklist, is worth considering
Several checklists are included below, as references, because they can be valuable. But you are encouraged to think of these lists as Double Check lists. They should not constrain you, nor should you follow them without a basic understanding of what each item means and why it has been included. Ideally, designers, content creators, and developers will have training from skilled experts before simply turning to these lists, see Training and Conferences on this website. It will also be helpful to observe people using a range of assistive technologies (preferably in-person, but watching videos is better than nothing).
In short, checklists are useful, but there are many ways that the Web Content Accessibility Guidelines can be met. Keep in mind that the WCAG Techniques are informative, not normative.
Only extensive reading and observation can provide a fundamental understanding to engrain the "why" of the guidelines so that considering them becomes a part of every decision made throughout a project's lifecycle.
So, please use the following checklists with care. Take the time to read and understand the caveats that the checklist creators, themselves, often include. Also, you will notice a set of "quick check" articles, below. Remember that they will not assure that you have fully met the Web Content Accessibility Guidelines.
Attached below is a blank checklist that was developed to do Stanford accessibility assessments.