Accessibility Technology Initiative
(Greensheet Workshop)

Chris Pollett

cpollett@gmail.com

April 23 and April 24, 2009.

Agenda

I am Chris Pollett, the Faculty-in-Residence for the Accessible Technology Initiative for the College of Science.
The Accessible Technology Initiative (ATI) came about because of Calstate Coded Memoranda AA-2007-04-PDF which requires that all administrative and instructional materials be made accessible by 2012.
All new greensheets are supposed to be accessible beginning Fall 2008.
Today, we are going to talk about what is needed to make greensheets accessible.
If you have questions on this initiative you want me to try to answer after I am gone, please feel free to contact me at: chris@pollett.org.
I also have a website on the ATI on which you can find these slides:
http://www.cs.sjsu.edu/faculty/pollett/accessibility/.

In addition to myself, the College of Science has one student-in-residence (SIR) who has been trained in how to make Word, PowerPoint, PDF documents accessible.
For the College of Science, the SIR also knows HTML.
Faculty and staff can send documents they would like to have converted to the FIR either by e-mail or snail mail and they will be forwarded to the student.
If a reasonable due date, reasonable document, and reasonable instructions are given, the student will make the document accessible return it to the FIR, and thence onto the faculty member.
If someone asks you to make a document accessible and you don't know how to do it, feel free to forward the document along to me, and I'll try to get the SIR to look at it.

I'd like to now briefly describe what kinds of things you should keep in mind when making your greensheet.
The Center for Faculty Development regularly schedules workshops on how to make Word, PowerPoint, and PDF documents accessible.
The next few slides give general things to watch for split according to part of the document:
- Heading of sections
- Images
- Tables
- Lists
- Links
- Text

Scanned documents have been optically character recognized and the results proofread.
Headings in the document are properly nested. Level 1 then level 2 then level 3; don't skip heading levels.
Headings should be used rather than changing font-size as screen-readers use these to generate table of contents
All images either have alternative text or captions

Tables should have captions in Word or Powerpoint; in HTML, you should use the summary attribute.
Repeat table headings if there is a page break.
Beware of nested tables as the reading order of screen readers will often be confused.
If you are listing items, for some visual impairments the list is very confusing if it is all on one line: Use a vertical list.

Link text should be descriptive of where the link goes: Not "click me."
For documents which may be printed have the link text be the actual url.
Between hypertext links you should have at least one character that is not a hypertext link.
Links should warn people if they go off site/document, or if they will require a plug-in to use. For example, the link text might end with: -offsite ; or -PDF; or -PPT; etc.

Text versus background should have sufficient contrast.
A reading flow between text boxes has been set up. (If you only have one text box, this is not a problem.)
Beware of character encodings: If possible always choose utf-8 for the web.
Ligatures sometimes confuse screen readers.