[ATcoord] contract language for inaccessible technologies

Fri Apr 28 11:43:29 PDT 2017

Yeah -  but then it falls on college IT departments to pay for this -
instead of it being a college initiative not just an IT department thing.

Rosalie (Rose) Madison
Everett Community College
IT4, IT Business Analyst/Project Manager
IT Accessibility Coordinator (ITAC)
Email: rmadison at everettcc.edu
Phone: (425) 259-8719
--Believe in the power of hard questions and honest answers

Please take a minute to help us improve our IT service by completing the IT
Feedback Survey <http://goo.gl/J3nGC> - http://goo.gl/J3nGC

On Fri, Apr 28, 2017 at 11:04 AM, Kukuk, Jacob <Jacob.Kukuk at lwtech.edu>
wrote:

> Just an idea, but if we got every college to agree to take ownership of
> let’s say the domain datawa.edu and have each college contribute let’s
> say $5 to pay for the cost of a cloud based server, we could allow shared
> access to designated coordinators where wavers would be stored and
> processed then setup a committee that handles the acceptance of such
> waivers. The committee would vote on how funds and the server are used, but
> it would close that silo gap that exists between colleges for this type of
> thing and would not place a specific responsibility on sbctc or any single
> college.
>
>
>
>
>
>
>
> *Jacob Kukuk** | Developer/DBA*
>
> Lake Washington Institute of Technology
>
> *Phone.* (425) 739-8350 *Mobile.* (425) 583-4921
>
> Jacob.Kukuk at lwtech.edu | http://lwtech.edu
>
> [image: cid:image003.jpg at 01D1CE23.EA30A9D0]
>
>
>
>
>
> *From:* ATcoord [mailto:atcoord-bounces at lists.ctc.edu] *On Behalf Of *Jess
> Thompson
> *Sent:* Friday, April 28, 2017 10:49 AM
> *To:* Andrew Glass <andrew.glass at ghc.edu>; 'Rosalie Madison' <
> rmadison at everettcc.edu>
>
> *Cc:* atcoord at lists.ctc.edu
> *Subject:* Re: [ATcoord] contract language for inaccessible technologies
>
>
>
> This is fabulous Andrew! Thanks for sharing!
>
>
>
> Yes - I'm in agreement that figuring out how to address this gap is a
> need. I think the examples you all are providing are great.
>
>
>
> Jess
>
>
>
> *Jess Thompson*
>
> Program Administrator, eLearning & Open Education
>
> Washington State Board for Community & Technical Colleges
>
> p: 360.704.4327 | c: 253.229.8591
>
> Current Projects
> <https://docs.google.com/document/d/1KXjxctpTAa2R06iRksMrjaeiCkphAJzqkwX-awvJh9g/edit?usp=sharing>
>
>
> ------------------------------
>
> *From:* Andrew Glass <andrew.glass at ghc.edu>
> *Sent:* Friday, April 28, 2017 10:45:32 AM
> *To:* 'Rosalie Madison'; Jess Thompson
> *Cc:* atcoord at lists.ctc.edu
> *Subject:* RE: [ATcoord] contract language for inaccessible technologies
>
>
>
> I feel this fills where a hole exists, from “approved” to “wavier
> required” as organizations start to implement accessibility into their
> software.  Just like we cannot make our technology and colleges accessible
> overnight, nor can software companies who have release cycles, etc.
>
>
>
> Similar to Ward, and in the spirt of UoM’s procedures, we’re adopting the
> “provisional use” section that meets demand in the middle, from our draft
> procedures:
>
>
>
>    1. EITA recommendations are submitted to the CIO for final
>    determination of “provisional use” or “exception.”
>
>
>    1. “Provisional Use” agreements are recommended for 1-3 year period,
>       if the vendor provides evidence of genuine accessibility efforts, and
>       periodically reviewed.
>       2. “Exceptions” are infrequently, based on substantial research as
>       indicated above
>
>
>    1. If either a provisional use or exception is granted, the requestor
>    will be required to describe the measure(s) which will ensure that
>    individuals with disabilities have equally effective accessible alternate
>    EIT.
>
>
>
> Provisional use designations are temporary.  A “provisional use”
> designation does not automatically roll into “approved for purchase”
> category.  Their status should be reviewed by the EITA work group at the
> end of the agreement period.
>
>
>
>
>
>
>
> *Andrew J. Glass*
>
> *Chief Executive of Information Technology*
> *__________________________________*
> *Grays Harbor College*
>
> phone: 360-538-2500
> email: andrew.glass at ghc.edu
> online: web <http://www.ghc.edu/> :: twitter
> <https://twitter.com/graysharbor> :: facebook
> <https://www.facebook.com/graysharborcollege>
>
>
>
> *From:* ATcoord [mailto:atcoord-bounces at lists.ctc.edu
> <atcoord-bounces at lists.ctc.edu>] *On Behalf Of *Rosalie Madison
> *Sent:* Friday, April 28, 2017 10:32 AM
> *To:* Jess Thompson <jess.thompson at sbctc.edu>
> *Cc:* atcoord at lists.ctc.edu
> *Subject:* Re: [ATcoord] contract language for inaccessible technologies
>
>
>
> What would this be for exactly?
>
>
>
> It is my understanding from Policy#188 that all purchased software if
> non-compliant has to have a waiver from the state.
>
>
>
> Is this for existing software?
>
>
> Rosalie (Rose) Madison
> Everett Community College
> IT4, IT Business Analyst/Project Manager
> IT Accessibility Coordinator (ITAC)
> Email: rmadison at everettcc.edu
> Phone: (425) 259-8719
> --Believe in the power of hard questions and honest answers
>
> Please take a minute to help us improve our IT service by completing the IT
> Feedback Survey <http://goo.gl/J3nGC> - http://goo.gl/J3nGC
>
>
>
> On Fri, Apr 28, 2017 at 10:23 AM, Jess Thompson <jess.thompson at sbctc.edu>
> wrote:
>
> Hello!
>
>
>
> Ward Naf at Whatcom has been trying to figure out how to handle situations
> where an office insists on purchasing a technology that is not fully
> compliant. He decided to allow a one year pilot with contract language that
> allows them to terminate the pilot if the product does not get into
> compliance within that pilot time frame.
>
>
>
> Sample contract language:
>
>
>
> TERMINATION
>
> This Agreement and all rights granted herein may be terminated upon thirty
> (30) days of written notice from either Party, provided, however, that
> Licensor may terminate this Agreement immediately upon any breach of this
> Agreement by Licensee. The Licensee may terminate this Agreement
> immediately should the Software not meet Federal 508 accessibility
> standards show on a VPAT or not meet WGAC 2.0 AA accessibility standards;
> per Washington State OCIO Policy 188 requirements. Upon such termination
> for breach or noncompliance with accessibility standards, all of Licensee’s
> rights under this Agreement and Licensee’s right to the use of the Software
> shall terminate immediately.
>
>
>
> In addition to the contract language, there's a letter to the vendor
> spelling out the agreement. I've attached a generic version where you
> insert specific info where the red text in brackets is.
>
>
>
> Big shout out to Ward at Whatcom -- this is a fabulous resource and I
> already know a few folks in similar positions that will find this very
> useful.
>
>
>
>
>
> Jess
>
>
>
>
>
> *Jess Thompson*
>
> Program Administrator, eLearning & Open Education
>
> Washington State Board for Community & Technical Colleges
>
> p: 360.704.4327 | c: 253.229.8591
>
> Current Projects
> <https://docs.google.com/document/d/1KXjxctpTAa2R06iRksMrjaeiCkphAJzqkwX-awvJh9g/edit?usp=sharing>
>
>
>
>
> _______________________________________________
> ATcoord mailing list
> ATcoord at lists.ctc.edu
> http://lists.ctc.edu/mailman/listinfo/atcoord_lists.ctc.edu
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ctc.edu/pipermail/atcoord_lists.ctc.edu/attachments/20170428/6b18a3ec/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2840 bytes
Desc: not available
URL: <http://lists.ctc.edu/pipermail/atcoord_lists.ctc.edu/attachments/20170428/6b18a3ec/attachment-0002.jpg>