How ADA compliant are CTL's services?

We consider a number of factors when we choose new "best of breed" tools to bring to faculty.  Some of our considerations are:
  • How well does the tool integrate with Columbia's class rostering and sign-in systems?  Can we add "single sign on" so that students and faculty can easily access the tool?
  • How portable is the content that students and faculty create during a semester? Can that content be re-used in other tools or systems? Can they get that content out and take it with them?
  • How accessible are the tools? Can users with disabilities access and use the tools?  These accessibility considerations can offer improved performance for all users (e.g. "key commands" which allow visually impaired users to skip directly to the first main content block or navigation... this can also help sighted users who wish to use them).
Here's a quick run-down of ADA compliance for some of CUIT's and CTL's services:

Sakai: There has been some activity on ADA compliance and Sakai.  Sakai's Accessibility Working Group.  

Google Docs: See this list of google docs features and their respective accessibility status.Sakai's current accessibility statement.

YouTube: See this support article on using YouTube with a screenreader.

Wikispaces: No documentation available, but we have made a request to wikispaces.com for information.

iTunes U: See this document on iTunes U and accessibility.

EdBlogs: Since EdBlogs is based on Wordpress, there are a number of themes and plugins that can be employed when needed.

Feedback and Knowledge Base