Quick HTML tips to make your site accessible

See http://www.w3.org/WAI for the complete Guidelines & Techniques

1. Images & Animations Use the alt attribute to concisely describe the function of all images.
2. Image Maps Use client-side MAP and provide text links for hotspots.
3. Multimedia Provide captioning and transcripts of audio, and descriptions of video.
4. Page Organization Use headings, lists, lang attribute, for structure. Use CSS for layout and style. Be consistent

5. Hypertext Links Use link text that makes sense when read out of context.
6. Graphs & Charts Summarize content or use the longdesc attribute.
7. Scripts, Applets, & Plug-ins Provide alternative representations in case active content is inaccessible or unsupported.
8. Frames Use title or name attribute and NOFRAMES element to allow access to individual pages.
9. Tables Don't use tables to layout columnar pages. Organize data to make sense when read row by row. Provide a summary.
10. Check your work Validate the HTML & CSS of your site. Use evaluation tools to verify accessibility.

Notes...

I shortened the Heading. ( I think the same as Daniel had)

1. changed visuals to images. The assumption is that people will interpret this as 'things which are inserted as images' - and is therefore more likely to trigger an ALT for pictures of words.
2. Removed rationale
3. Fine as discussed
4. I moved 'table summaries' (belongs in tables). The other things are about structure - it wasn't clear enough that headings/lists were for structure as opposed to layout.
5. fine as is
6. If there is another important point, the longdesc bit could happily be added to 1, which might make it look less like all we care about is ALT text.
7. I would like to shorten this. But I am not sure how. Maybe by using a point about W3C standards (as per Guideline A 14
8. NOFRAMES seems to me an important design principle. Daniel (among others) disagrees. This is close to being a 'religious' issue.
9. The accessibility issue for tables is that they can only be read line by line. Otherwise they wouldn't be much of a problem. It should simply read 'Ensure that tables make sense when read line by line' (If I could think of a better way to describe what I mean.
10. Removed the different test techniques - turning off images/sounds/etc is a tool, the same as lynx is a tool, the same as Bobby is a tool. And it is not really a very good one - browser differences are too difficult for most people to keep track of (eg me) so they end up going for what works in their own again and we're only a bit further forward. Better to get people looking at tools first, and falling back on their other browser / turning stuff off as a second-rate but available option I think.