<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>ATHENites:</p>
<p><br>
</p>
<p>I'm cross-posting this message via Mike Gifford, from the WebAIM
email list. Many of you may not see his post, and he's cited
several higher ed. resources including Ohio Washington, and
others. And as we know, higher ed. can be different in its
procurement practices as compared to state governments or Federal
agencies.</p>
<p><br>
</p>
<p>For the record/future tracking (in case people post further to
this WebAIM message), the list thread is here:</p>
<p><a class="moz-txt-link-freetext" href="http://webaim.org/discussion/mail_thread?thread=8033">http://webaim.org/discussion/mail_thread?thread=8033</a></p>
<p><br>
</p>
<p>I imagine Mike certainly welcomes worldwide contributions.</p>
<p><br>
</p>
<p>I also suspect Kara's recent LinkedIn post on this topic of
procurement might be of interest to folks who use that platform:</p>
<p><a class="moz-txt-link-freetext" href="https://www.linkedin.com/hp/update/6250017213194002432">https://www.linkedin.com/hp/update/6250017213194002432</a></p>
<p>I found it particularly clear. Thank you, Kara.<br>
</p>
<p><br>
</p>
<p>There's a bit of a discussion in the comments for that LinkedIn
post about VPATs (pros and cons), and I was reminded that a
version 2 is being worked on, but I'm not sure of the status of
that project. Here are the best two links I could find:</p>
<p><br>
</p>
<p><a class="moz-txt-link-freetext" href="https://www.itic.org/policy/accessibility/">https://www.itic.org/policy/accessibility/</a></p>
<p><br>
</p>
<p>and</p>
<p>the Beta (a Word document dated in February of 2017:</p>
<p><a class="moz-txt-link-freetext" href="https://www.itic.org/dotAsset/16a63f08-30ea-4f5d-997f-5c095aa3d345.docm">https://www.itic.org/dotAsset/16a63f08-30ea-4f5d-997f-5c095aa3d345.docm</a></p>
<p><br>
</p>
<p><br>
</p>
<p>I post to this list not to start a further thread on here, but
rather, perhaps, to facilitate the use of Mike's Git repo. and/or
his Wiki page (both cited below) to consolidate and streamline
efforts to help the community at large.<br>
</p>
<p><br>
</p>
<p>Best,</p>
<p>Jennifer</p>
<p><br>
</p>
<div class="moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
</th>
<td>[WebAIM] Improving Accessibility Procurement</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Thu, 30 Mar 2017 14:58:08 -0400</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td>Mike Gifford <a class="moz-txt-link-rfc2396E" href="mailto:mike@openconcept.ca"><mike@openconcept.ca></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Reply-To:
</th>
<td>WebAIM Discussion List
<a class="moz-txt-link-rfc2396E" href="mailto:webaim-forum@list.webaim.org"><webaim-forum@list.webaim.org></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:webaim-forum@list.webaim.org">webaim-forum@list.webaim.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>Hi,
Some of you may have seen this, but I’m trying to pull together some best practices for boiler-plate contracts & RFPs. I’ve got some examples up here:
<a class="moz-txt-link-freetext" href="https://github.com/mgifford/a11y-contracting">https://github.com/mgifford/a11y-contracting</a> <a class="moz-txt-link-rfc2396E" href="https://github.com/mgifford/a11y-contracting"><https://github.com/mgifford/a11y-contracting></a>
Generally, when I try to fix a problem, I find it useful to look upstream to see if it could be caused by something earlier in the system.
Procurement seems to be a common point of failure in improving accessibility. Often, it’s just another of a long list of issues in an RFP and everyone knows that it’s going to be left to the end (and overlooked).
What are the best practices to see that:
- the right product and the right people are selected to do the job
- that the process used to generate the IT follows best practices
- that updates to the software don’t break accessibility
Anyways, I’d love to have people submit suggestions of best practices. I’ve set up a wiki for links here:
<a class="moz-txt-link-freetext" href="https://github.com/mgifford/a11y-contracting/wiki">https://github.com/mgifford/a11y-contracting/wiki</a>
I found this very interesting orphaned page (last updated August 6, 2015):
<a class="moz-txt-link-rfc2396E" href="https://www.justice.gov/crt/508/report/content.htm"><https://www.justice.gov/crt/508/report/content.htm></a>
<a class="moz-txt-link-freetext" href="https://www.justice.gov/crt/increased-coordination">https://www.justice.gov/crt/increased-coordination</a>
It makes reference to other documents that look very interesting. I think with more digging & Archive.org <a class="moz-txt-link-rfc2396E" href="http://archive.org/"><http://archive.org/></a> it would be possible to find better resources. However, it wasn’t easy to find the text of the sample contract language and procurement practices which are alluded to.
Mike
--
Mike Gifford, President, OpenConcept Consulting Inc.
Drupal 8 Core Accessibility Maintainer - <a class="moz-txt-link-freetext" href="https://drupal.org/user/27930">https://drupal.org/user/27930</a>
Twitter: @mgifford @openconcept_ca
Open source web development for social change - <a class="moz-txt-link-freetext" href="http://openconcept.ca">http://openconcept.ca</a>
Drupal Association Member | Acquia Partner | Certified B Corporation
</pre>
</div>
</body>
</html>