Many of us have been dealing with the new accessibility requirements that take effect in late-April. I have been a member of a special Accessibility Taskforce on my campus since this fall. Our webmaster headed up the effort, the taskforce members helped flesh out a strategy for compliance, needed policy changes, the cataloging of all web-hosted software so as to find out where we were with new accessibility requirements, and a strategic plan for implementation of the new standards. We met today and took something of a victory lap as the materials were presented to the President’s Council this week for the 1st policy reading – and was well-received. There is still more to do but we are on track to be ready in time for the April deadline.
I’ve been the academic representative on our campus taskforce. Our WebCollege is also represented as is our Disability Resource Center and the Leadership team. At today’s taskforce meeting, I embraced my role as something of a contrarian. I had avoided the wordsmithing of the various documents – we had plenty of cooks in that kitchen. I focused on our potential vulnerability as an institution once the new requirements take effect. I assume many institutions expect there will be a grace period to allow for software exceptions that will not be compliant. However, the Federal government has normally seen the deadline date as THE compliance date. In other words, there are institution-related risks for not being fully compliant on day 1. Those of us that have been involved in online learning long-term, will remember the American Society for the Blind lawsuits leveled at a surprising number of higher ed institutions for failing to have every classroom ADA compliant. That type of advocacy likely will quickly re-emerge. After all, the tactic is effective and more rapidly advanced full compliance of institutions which in turn greatly benefits statements needing accessibility solutions.

