[ATcoord] New Software Purchases...after March 31st.

[Casile, Lori]

Except that it’s not just WA state – it’s federal – and it’s not just higher ed.  But, you’re right, the vendors do not get it yet.

____________________________________
Lori Casile
Chief Information Officer
South Puget Sound Community College
(360) 596-5353
(360) 970-4052 (M)


From: ATcoord <atcoord-bounces at lists.ctc.edu<mailto:atcoord-bounces at lists.ctc.edu>> on behalf of "Rovner, Amy" <arovner at shoreline.edu<mailto:arovner at shoreline.edu>>
Date: Saturday, February 18, 2017 at 7:08 PM
To: Rosalie Madison <rmadison at everettcc.edu<mailto:rmadison at everettcc.edu>>, "atcoord at lists.ctc.edu<mailto:atcoord at lists.ctc.edu>" <atcoord at lists.ctc.edu<mailto:atcoord at lists.ctc.edu>>
Subject: Re: [ATcoord] New Software Purchases...after March 31st.

Hi Rosalie,

I guess my first question back is "what do you need this tech to do for you" and then dig deeper to find out if this one is truly the  "only tech" that will truly meet their needs.  If that's the case, then I'd ask them to call the vendor back, explain that WA state policy does not allow for purchase of non-compliant tech and that your institution will not be able to purchase it unless there is a VPAT in place with plans added to make it compliant in the future. You can also add that no one in WA state will be able to purchase it either.

Honestly any vendor with products for education is going to have to address accessibility very soon.

You can also call upon the collective power of this group to help "educate" vendors on what our state needs are.

Good luck to you!

Best,
Amy


Get Outlook for iOS<https://aka.ms/o0ukef>

________________________________
From: ATcoord <atcoord-bounces at lists.ctc.edu<mailto:atcoord-bounces at lists.ctc.edu>> on behalf of Rosalie Madison <rmadison at everettcc.edu<mailto:rmadison at everettcc.edu>>
Sent: Friday, February 17, 2017 1:54:17 PM
To: atcoord at lists.ctc.edu<mailto:atcoord at lists.ctc.edu>
Subject: [ATcoord] New Software Purchases...after March 31st.

Good Afternoon,
How is everyone addressing this?
In reading (and re-reading) Policy #188, you can submit a waiver for existing software that has be prioritized with corrective action plan.

I have been asked " What if (for educational purposes) software x is the only one that meets all of the curriculum requirements. But it is not ADA Compliant on its own. And there is no road map for development in the future.

This does not mean the purchase of it is blocked, but that as coordinator;  would submit a waiver for approval. - Correct?
Per:

  1.  For each instance of non-compliance of a new covered technology <https://ocio.wa.gov/definition-terms-used-ocio-policies-and-reports#CovTech> [6], a waive<https://ocio.wa.gov/policies/policy-103-technology-policy-standards-waiver-request>r [7] must be requested and approved.

     *   The waiver request must include a corrective action plan for each area of noncompliance.

        *   The corrective action plan must describe the access barriers expected to result from the non- compliance, identify the information, activities and functions compromised by those access barriers, and describe the steps the agency will implement to ensure that people with disabilities will be afforded equivalent access to the information, activities and functions through alternative means of access.

What is the turn around time for this? This needs to be built into our review and purchasing process.

Rose

Rosalie (Rose) Madison
Everett Community College
IT4, IT Business Analyst/Project Manager
IT Accessibility Coordinator (ITAC)
Email: rmadison at everettcc.edu<mailto: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ctc.edu/pipermail/atcoord_lists.ctc.edu/attachments/20170219/30a342c5/attachment-0002.html>