One obvious list of 10 is the WAI ten quick tips.  See attachment.
At 02:33 PM 7/9/2002 -0500, you wrote:

>Hello all,
>
>I need your assistance.  I will be presenting a session on accessibility
>issues at a workshop on Thursday.  If you could identify 10 key points to
>get across to faculty as they learn to develop web courses about persons
>with access issues what would they be?  I am considering a demonstration
>of software and hardware but I want to blend that with a little
>pedagogy.  Please send me your top ten suggestions so that I can include
>them in the presentation.  BTW.. this is my first presentation on this
>topic by myself.
>
>Susan K. Slaybaugh,
>
>Instructional Development Specialist,
>
>Office for Professional Development,
>
>755 W. Michigan St.,
>
>UL1125D,
>
>Indianapolis, IN 46202.
>
>Phone:  (317) 274-3104
>


                 Norman Coombs, Ph.D.
CEO, EASI (Equal Access to Software and Information)
http://www.rit.edu/~easi
Professor Emeritus, Rochester Institute of Technology
E-mail: [log in to unmask]
         Cell (949) 922-5992
http://www.rit.edu/~nrcgsh
22196 Caminito Tasquillo
Laguna Hills CA 92653



Quick tips to make accessible Web sites
FOR COMPLETE GUIDELINES & CHECKLIST: WWW.W3.ORG/WAI

1.  Images & animations. Use the alt attribute to describe the function of all
    visuals.

2.  Image maps. Use client-side MAP and text for hotspots.

3.  Multimedia. Provide captioning and transcripts of audio, descriptions of
    video, and accessible versions in case inaccessible formats are used.

4.  Hypertext links. Use text that makes sense when read out of context. For
    instance, do not use "click here."

5.  Page organization. Use headings, lists, and consistent structure. Use CSS
    for layout and style where possible.

6.  Graphs & charts. Summarize or use the longdesc attribute.

7.  Scripts, applets, & plug-ins. Provide alternative content in case active
    features are inaccessible or unsupported.

8.  Frames. Label with the title or name attribute.

9.  Tables. Make line by line reading sensible. Summarize. Avoid using tables
    for column layout.

10. Check your work. Validate the HTML. Use evaluation tools and text-only
    browsers to verify accessibility.