Dan,<br><br>as one who works on EIT accessibility for a living I want to say this is an excellent plan. One of the best I have seen.<br><br>Let me know what I can do to help you once you are beginning to implement the plan. I have the Assistive Technology to test it.<br>
<br>Sincerely,<br>Mike Burks<br>919 349 6661<br><br><div class="gmail_quote">On Mon, Mar 4, 2013 at 12:29 PM, Dan Graham <span dir="ltr"><<a href="mailto:dan.graham@isoc.org" target="_blank">dan.graham@isoc.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi all,<br><br>Here's an update on the plan to ensure our site meets Web Content Accessibility Guidelines (WCAG) level 2.0.<br>
<br>Progress so far: Two accessibility audits were conducted last year. One focused on identifying specific issues that were preventing specific sections of the site from being WCAG 2.0 compliant. The second was conducted by a visually impaired person and provided valuable constructive criticism and great recommendations. <br>
<br>Two actions followed the above mentioned audits:<br><br><div><ol><li>A series of quick fixes to the site</li><li>The development of plan that will ensure our site is WCAG compliant - and stays that way moving forward</li>
</ol></div><br><font size="4"><span style="font-size:14px"><b>1. Quick Fixes</b><br></span></font><br><div><ul><li>The ability to control the image carousel with next, previous and pause buttons.</li><li>Underlined links as they help make our links more visible</li>
<li>The ability to navigate the site without a mouse (i.e. keyboard only)</li><li>Currently adding alternative text to all images on the site </li></ul></div><br><b><font size="4"><span style="font-size:14px">2. Accessibility Plan</span></font></b><br>
<br>As mentioned, the goal is to ensure that our site is WCAG 2.0. compliant (<a href="http://www.w3.org/WAI/WCAG20/glance/" target="_blank">http://www.w3.org/WAI/WCAG20/glance/</a>). Ideally, I'd like our website to be a flagship for accessibility. I've asked our main web developer (Balance Interactive) to develop plan to help us reach this goal. <br>
<br>It's important to note that this commitment to accessibility will require changes in our processes. Some of these changes will translate into longer development times and greater costs. In other words, the challenge of compliance will be, as stated in the WCAG summary: "To create content that can be presented in different ways, including by assistive technologies, without losing meaning".<br>
<br>The following items are expected to take 10 to 12 weeks to complete.<br><br>Here's an overview of the key components of the plan:<br><br><b>2.1 Changes to our Content Management System (CMS)</b><br>A key step to ensuring that our content is accessible is the addition of accessibility checks within our CMS workflow. We'll be adding a new component to our CMS (Drupal) that will provide our content creators/editors with the ability to check the accessibility of their content prior to it being published to the website - and allow them to make the necessary changes to ensure WCAG 2.0 compliance. <br>
<br><b>2.2 Content Strategy</b><br>Key sections of our site will be reviewed to identify content that may cause difficulties or barriers to people with disabilities. This review will be larger in scope than the audits that were done last year. This will result in further fixes to the site and will also inform documentation of guidelines and training for staff (see below)<br>
<br><b>2.3 Staff Training</b><br>This will be key to ensure the site continues to be WCAG 2.0. compliant. Accessibility workshops for staff (those who post content to the website) will be given by a team of accessibility experts from Balance Interactive. The sessions will focus on creating usable web pages that are WCAG 2.0 compliant. Both Lia and I will be trained on how to train staff in this area, ensuring that we can conduct this type of training on a regular basis moving forward.<br>
<br><b>2.4 Testing by People with Disabilities</b><br>To be a flagship for accessibility, it is critical to involve people with disabilities in the testing. We'll be using a vendor who specializes in this type of testing - Knowbility (<a href="http://www.knowbility.org/" target="_blank">http://www.knowbility.org/</a>). This testing ensures a representative variety of disabilities and assistive technology used. <br>
<br><b>2.5 Responsive Design</b><br>Accessibility is not just for people with disabilities. In a broader sense, accessible design also helps serve content to a variety of devices, across several connection speeds. The goal is to ensure that our site has different layouts for different devices. For accessibility purposes, we will be able to display alternative text, links to transcripts, and lower resolution for slower connections.<br>
<br>Let me know if you have any questions.<br><br>Best regards,<br><br>Dan<div><br><div>Dan Graham</div><div>Director, Online Marketing<br>Internet Society<br><br>Office: <a href="tel:%2B41%2022%20809%200368" value="+41228090368" target="_blank">+41 22 809 0368</a><br>
Mobile: <a href="tel:%2B41%2078%20757%209943" value="+41787579943" target="_blank">+41 78 757 9943</a><br><br><a href="http://www.internetsociety.org" target="_blank">www.internetsociety.org</a><br><a href="http://www.twitter.com/internetsociety" target="_blank">www.twitter.com/internetsociety</a><br>
<a href="http://www.youtube.com/internetsocietyvideo" target="_blank">www.youtube.com/internetsocietyvideo</a><br><br><br></div><br></div></div><br>_______________________________________________<br>
As an Internet Society Chapter Officer you are automatically subscribed<br>
to this list, which is regularly synchronized with the Internet Society<br>
Chapter Portal (AMS): <a href="https://portal.isoc.org" target="_blank">https://portal.isoc.org</a><br></blockquote></div><br>