The following are the things that need to be checked manually to meet Web Accessibility.

The following checklist has been re-worded for simplicity. For the full text, please see the Full Checklist for the complete wording on W3C WAI and Section 508.

General (W3C Priority 1)YesNoN/A
2.1 & 508 (c) Make sure information is not determined by color alone. YesNoN/A
6.1 & 508 (d) Documents must be able to function without CSS. YesNoN/A

If you use images and maps.
1.2 & 508 (e) Include text links for each server-side image map. YesNoN/A
9.1 & 508 (f) Use client-side image maps instead of server-side maps. YesNoN/A

If you use tables.
5.1 & 508 (g) For data tables, identify row and column headers. YesNoN/A
5.2 & 508 (h) Use <th> & <td> to associate data cells and header cells. YesNoN/A

If you use applets and scripts.
6.3 Ensure that pages functions without scripts, or have text only. YesNoN/A

If you use multimedia.
1.3 Provide an audio track for multimedia. YesNoN/A
1.4 & 508 (b) Provide closed captioning for multimedia. YesNoN/A

If all else fails.
11.4 & 508 (k) If all else fails, provide a text only page. YesNoN/A

Standard (Section 508)YesNoN/A
508 (l) Make content generated by scripts compliant. YesNoN/A
508 (m) Provide links to plug-ins and make their content compliant. YesNoN/A
508 (n) Make forms compliant for screen readers by using the <label> tag. YesNoN/A
508 (o) Allow users to skip repetitive navigation links. YesNoN/A
508 (p) Alert the user about timed responses. YesNoN/A

General (W3C Priority 2)YesNoN/A
3.3 Use CSS. YesNoN/A
3.4 Use relative (width="70%") rather than absolute (width="500") units. YesNoN/A
10.1 Do not cause pop-ups or change the current window without notice. YesNoN/A

If you use tables.
5.3 Ensure table makes sense when linearized or provide text only. YesNoN/A
5.4 For layout tables, do not use structural tags (<h1>, <dt>, etc.) YesNoN/A

If you use forms.
10.2 Use the <label> tags with forms for screen readers. YesNoN/A
12.4 Associate labels with their controls. YesNoN/A

If you use applets and scripts.
6.4 Ensure that script event handlers are input device-independent. YesNoN/A
7.3 Avoid movement in pages. YesNoN/A
8.1 Ensure scripts and applets are compatible with assistive technologies. YesNoN/A
9.2 Use both mouse & keyboard (ie. "onmousedown" & "onkeydown".) YesNoN/A
9.3 Events are not restricted to keystroke or mouse coordinates alone. YesNoN/A

General (W3C Priority 3)YesNoN/A
9.4 Create a logical tab order through links, form controls, and objects. YesNoN/A
9.5 Provide keyboard shortcuts to important links and controls. YesNoN/A
10.5 Seperate adjacent links by a non-link printable character. (AB | CD) YesNoN/A
13.5 Provide navigation bars that highlight. YesNoN/A
13.6 Group related links, and provide a way to bypass the group. YesNoN/A
13.7 If using a search engine, have a basic and advanced option. YesNoN/A
13.9 Document collections need a 'zip' file, or use the <link> tag. YesNoN/A
13.10 Provide a means to skip over multi-line ASCII art. YesNoN/A

If you use images and image maps.
1.5 Provide redundant text links for client-side image maps. YesNoN/A

If you use tables.
5.5 Provide summaries for tables. YesNoN/A
5.6 Provide abbreviations for header labels. YesNoN/A
10.3 Provide a linear text page for all tables that have text in columns. YesNoN/A

If you use forms.
10.4 Include default value for edit boxes and text areas. YesNoN/A