<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Web Accessibility</title>
	<atom:link href="http://webs.purduecal.edu/webaccessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://webs.purduecal.edu/webaccessibility</link>
	<description>Purdue University Calumet</description>
	<lastBuildDate>Fri, 01 Mar 2013 11:37:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
		<item>
		<title>Tip of the Week &#8211; Where Did The Pictures Go?</title>
		<link>http://webs.purduecal.edu/webaccessibility/2013/01/27/tip-of-the-week-7t/</link>
		<comments>http://webs.purduecal.edu/webaccessibility/2013/01/27/tip-of-the-week-7t/#comments</comments>
		<pubDate>Sun, 27 Jan 2013 16:55:10 +0000</pubDate>
		<dc:creator>Pamela Riesmeyer</dc:creator>
				<category><![CDATA[Tip of the Week]]></category>

		<guid isPermaLink="false">http://webs.purduecal.edu/webaccessibility/?p=843</guid>
		<description><![CDATA[This tip builds on a previous one &#8211; what to do about images of text. Our Web Accessibility Partner of the Week for January 25th, provided us with a perfect example as well as one solution. The Challenge: So here&#8217;s the situation: you have a lot of information that you want to add to a [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_864" class="wp-caption alignright" style="width: 160px"><a href="http://webs.purduecal.edu/webaccessibility/files/screenshot_techgrad_before_noimg.jpg"><img class="size-full wp-image-864 " title="View Graduate Assistant page with no images and no alternate text" src="http://webs.purduecal.edu/webaccessibility/files/techgrad_noimgT.jpg" alt="View larger Version of Graduate Assistant page with no images and no alternate text" width="150" height="138" /></a><p class="wp-caption-text">Figure 2</p></div>
<div id="attachment_861" class="wp-caption alignright" style="width: 170px"><a href="http://webs.purduecal.edu/webaccessibility/files/screenshot_techgrad_before.jpg"><img class="size-full wp-image-861" title="View larger version of Graduate Assistants page with no alternate text" src="http://webs.purduecal.edu/webaccessibility/files/techgrad_beforeT.jpg" alt="View larger version of Graduate Assistants page with no alternate text" width="160" height="306" /></a><p class="wp-caption-text">Figure 1</p></div>
<p><a href="http://webs.purduecal.edu/techgrad/meet-our-graduate-assistants/"><img class="alignright size-full wp-image-860" style="clear: right;" title="Revised current Graduate Assistants Page " src="http://webs.purduecal.edu/webaccessibility/files/techgrad_afterT.jpg" alt="Revised Current Graduate Assistants Page" width="264" height="333" /></a></p>
<p>This tip builds on a previous one &#8211; <a href="http://webs.purduecal.edu/webaccessibility/2012/10/15/tip-of-the-week-2t/">what to do about images of text</a>.</p>
<p>Our <a href="http://webs.purduecal.edu/webaccessibility/2013/01/25/partner-01-25-13">Web Accessibility Partner of the Week for January 25th</a>, provided us with a perfect example as well as one solution.</p>
<h3>The Challenge:</h3>
<p>So here&#8217;s the situation: you have a lot of information that you want to add to a Web page, in this case, the names, photos and relevant details about the <a href="http://webs.purduecal.edu/techgrad/meet-our-graduate-assistants/">Graduate Assistants in the School of Technology Graduate Studies</a>. You&#8217;re also going to print a flyer, a hard copy,  with that information and have it available in the office.</p>
<p>So, thinking to get two outs with one pitch, so to speak, you create the flyer, save it as an image, and post that image  to your Web site as illustrated by <strong>Figure 1</strong>.</p>
<p>And you think to yourself, well, this flyer has all of the information anyone would need, it&#8217;s attractive and it was super-easy to post.</p>
<h3>Just One &#8211; BIG &#8211; Problem</h3>
<p>Except for one thing &#8211; anyone is visually-impaired, and anyone who has images turned off in the browser, has no idea what&#8217;s on that page. They can&#8217;t read any of your great information. It&#8217;s completely lost to them as illustrated by <strong>Figure 2</strong>.</p>
<p>In the case of the Graduate Assistants, there was another problem. What looked like 16 individual image blocks was actually two large images. So if one of the assistants left and their details needed to be removed, the entire image would need to be edited.</p>
<h3>What To Do? One Option</h3>
<p>For the Graduate Assistants, we decided that a table would be the most expedient way to position the information on the page. We discourage the use of tables for layout, but sometimes the limitations of the software make it difficult to add content without them. The important thing to remember is that with a layout table, we do NOT use header cells, captions, summaries and scope, as we do with a data table.</p>
<p>Step one was to create individual photos of each assistant, by cropping the larger image into smaller ones.</p>
<p>Step two was to create the table to position them on the page.</p>
<p>Step three was to add the image and details for each individual. The photos were inserted, using the person&#8217;s name as Alternate Text and then their information was typed in below their photo, so that both a person&#8217;s image and corresponding details were in the same table cell.</p>
<h3>The Result</h3>
<p>Now, when images are turned off, or a person uses screen reader software to access the page, everything is right there, available to them, just as it is for those who can see the images.</p>
<p>Sometimes you may want additional styling, like borders or backgrounds and that&#8217;s something that University Relations can help you with in a way that keeps your content accessible and still gives you the look and feel you want.</p>
<h2>What Do You Want To Know?</h2>
<p>These tips are designed to help us all better understand the requirements of <a href="http://webs.purduecal.edu/webaccessibility/web-accessibility-policy/">our Web Accessibility Policy</a> and to offer some shortcuts and hints that will help you as you create and update your Web sites.</p>
<p>Questions and suggestions for future hints are welcome! Just <a href="mailto:riesmeyerp@purduecal.edu?subject=Tip%20of%20the%20Week">send an email </a> or fill out <a href="http://webs.purduecal.edu/webaccessibility/contact/">our online form</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://webs.purduecal.edu/webaccessibility/2013/01/27/tip-of-the-week-7t/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Partner of the Week: Graduate Studies in Technology</title>
		<link>http://webs.purduecal.edu/webaccessibility/2013/01/25/partner-01-25-13/</link>
		<comments>http://webs.purduecal.edu/webaccessibility/2013/01/25/partner-01-25-13/#comments</comments>
		<pubDate>Fri, 25 Jan 2013 16:57:14 +0000</pubDate>
		<dc:creator>Pamela Riesmeyer</dc:creator>
				<category><![CDATA[Web Accessibility Partners]]></category>

		<guid isPermaLink="false">http://webs.purduecal.edu/webaccessibility/?p=836</guid>
		<description><![CDATA[Not every Web Accessibility Partner includes a site that&#8217;s reached a high level of compliance. Sometimes it&#8217;s a &#8220;Can Do!&#8221; spirit and an enthusiasm shown by the site&#8217;s owners and editors that makes them stand out. And that&#8217;s the case this week. We&#8217;re recognizing Kishan Saha, a graduate assistant for the School of Technology Graduate [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://webs.purduecal.edu/techgrad/"><img class="alignright size-full wp-image-840" title="School of Technology Graduate Studies Home Page" src="http://webs.purduecal.edu/webaccessibility/files/techgrad_home.jpg" alt="School of Technology Graduate Studies Home Page" width="271" height="220" /></a></p>
<p>Not every <strong>Web Accessibility Partner</strong> includes a site that&#8217;s reached a high level of compliance. Sometimes it&#8217;s a &#8220;Can Do!&#8221; spirit and an enthusiasm shown by the site&#8217;s owners and editors that makes them stand out. And that&#8217;s the case this week. We&#8217;re recognizing <strong>Kishan Saha</strong>, a graduate assistant for the <a href="http://webs.purduecal.edu/techgrad/">School of Technology Graduate Studies site</a>, working for <strong>Assistant Dean of Graduate Studies, Dr. Mohammad A. Zahraee</strong>, and <strong>Technology Administrator David McLees</strong>.</p>
<h3>Web Accessibility Training</h3>
<p><strong>Kishan</strong> was added as an editor this week, and we contacted him to talk about Web accessibility. We wanted to make sure, as we do with all editors, early on, that he had all the knowledge and information he needed to assure that any content he added meets the <a href="http://webs.purduecal.edu/webaccessibility/web-accessibility-policy/">Web Accessibility Policy</a> guidelines.</p>
<p>One primary advantage to having the training *before* starting to edit a site is that editors don&#8217;t have to waste time going back to redo their work if something fails the compliance tests. Plus, the information is available and accessible sooner to a wider audience.</p>
<h3>How Soon Can We Start?</h3>
<p>Kishan&#8217;s response was an enthusiastic request for an immediate appointment. We met and talked with him about accessibility and the <a href="http://webs.purduecal.edu/webaccessibility/best-practices/">four easy things to consider &#8211; images, links, tables and page structure</a>.</p>
<p>We also helped him address a major problem on one of the Web pages he is to edit &#8211; the content consisted of just a heading and two large images with a lot of information but no alternate text. (That issue and the solution we came up with are the subject of <a href=" http://webs.purduecal.edu/webaccessibility/2013/01/25/tip-of-the-week-7t/">our Tip of the Week.</a>)</p>
<p>It&#8217;s that enthusiasm and that determination to learn how to create accessible content from the beginning, that we applaud in Kishan and in the School of Technology Graduate Studies.</p>
<h3>Busy Schedules Make Things Tough</h3>
<p>We know that it can be difficult to attend an in-person &#8220;Introduction to Web Accessibility&#8221; workshop, what with busy schedules and conflicting meetings. We want to make this as easy as possible for everyone to get the information they need.</p>
<p>So we set up <a href="http://webs.purduecal.edu/webaccessibility/">our Web Accessibility site</a> with a variety of resources including contact information. And we are happy to set up individual meetings as we did with Kishan.</p>
<h3>Try a Webinar!</h3>
<p>We also have had good experiences with Webinars, using screen-sharing software so that you can &#8220;attend&#8221; from the comfort of your own office.</p>
<p>We&#8217;re meeting with departments and offices, groups of editors, and individuals, and we are ready to help you in any way we can. If we have yet to reach out to you, please feel free to reach out to us!</p>
]]></content:encoded>
			<wfw:commentRss>http://webs.purduecal.edu/webaccessibility/2013/01/25/partner-01-25-13/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Partner of the Week: Anthony Marszalek and Tim Hurtt</title>
		<link>http://webs.purduecal.edu/webaccessibility/2013/01/18/partner-1-18-13/</link>
		<comments>http://webs.purduecal.edu/webaccessibility/2013/01/18/partner-1-18-13/#comments</comments>
		<pubDate>Fri, 18 Jan 2013 16:51:28 +0000</pubDate>
		<dc:creator>Pamela Riesmeyer</dc:creator>
				<category><![CDATA[Web Accessibility Partners]]></category>

		<guid isPermaLink="false">http://webs.purduecal.edu/webaccessibility/?p=831</guid>
		<description><![CDATA[For the week of January 18th, we have chosen our two temporary workers, Anthony Marszalek and Tim Hurtt as our Web Accessibility Partners. Anthony is a 2010 graduate of Purdue University Calumet and Tim graduated in May of 2012. Both have been working on the Web Accessibility Initiative since April of 2012, and together, they [...]]]></description>
			<content:encoded><![CDATA[<p>For the week of January 18th, we have chosen our two temporary workers, <strong>Anthony Marszalek</strong> and <strong>Tim Hurtt</strong> as our <strong>Web Accessibility Partners</strong>. Anthony is a 2010 graduate of Purdue University Calumet and Tim graduated in May of 2012. Both have been working on the Web Accessibility Initiative since April of 2012, and together, they have retrofitted over 16 hundred documents and forms and captioned over 50 videos for various departments and offices. So far.</p>
<h3>Meeting the Challenge</h3>
<p>Creating accessible versions of PDFs and Office documents can be time consuming and sometimes frustrating, as anyone who has worked on these will tell you. And there are thousands of documents on the Purdue Calumet Web sites. Anthony and Tim have learned to do this well and efficiently.</p>
<p>When they tag a document, they approach it from the point of view of someone using assistive technology such as screen reader software, making sure that it&#8217;s accessible, while still maintaining the visual appeal. In some cases, if the document can&#8217;t be made accessible without changing the look, they&#8217;ll provide an alternative, accessible version so that both are available.</p>
<p>They have also helped by creating Web pages from PDFs and documents, to provide another accessible alternative.</p>
<p>Anthony has done all of the captioning for videos which are under 20 minutes in length and focused mainly on marketing. He&#8217;s efficient and that allows us to provide a quick turnaround.</p>
<h3>Providing a Service</h3>
<p>Anthony and Tim allow us to offer a service and a level of support which we wouldn&#8217;t otherwise be able to provide, due to a lack of person-power. We are working with several departments at the moment to get their documents in shape, and providing training for anyone who wants to learn to do the work themselves.</p>
<p>The dedication and commitment evident in these two Purdue Calumet graduates are the reasons that we are proud to name them our <strong>Web Accessibility Partners for the Week</strong>!</p>
]]></content:encoded>
			<wfw:commentRss>http://webs.purduecal.edu/webaccessibility/2013/01/18/partner-1-18-13/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Partner of the Week: Administrative and Professional Staff Advisory Committee (APSAC)</title>
		<link>http://webs.purduecal.edu/webaccessibility/2013/01/11/partner-01-11-13/</link>
		<comments>http://webs.purduecal.edu/webaccessibility/2013/01/11/partner-01-11-13/#comments</comments>
		<pubDate>Fri, 11 Jan 2013 19:27:45 +0000</pubDate>
		<dc:creator>Pamela Riesmeyer</dc:creator>
				<category><![CDATA[Web Accessibility Partners]]></category>

		<guid isPermaLink="false">http://webs.purduecal.edu/webaccessibility/?p=821</guid>
		<description><![CDATA[The January 11th Web Accessibility Partner of the Week honor goes to the Administrative and Professional Staff Advisory Committee (APSAC)! Documents Pose a Challenge The Web site for APSAC isn&#8217;t all that large, but it does pose a serious challenge to accessibility: the site has archives of dozens of downloadable documents, most of them in [...]]]></description>
			<content:encoded><![CDATA[<p>The January 11th <strong>Web Accessibility Partner of the Week</strong> honor goes to the <a href="http://webs.purduecal.edu/apsac/">Administrative and Professional Staff Advisory Committee (APSAC)</a>!</p>
<div id="attachment_825" class="wp-caption alignright" style="width: 260px"><img class="size-full wp-image-825" title="Screenshot of the Administrative and Professional Staff Advisory Committee  Web site" src="http://webs.purduecal.edu/webaccessibility/files/APSAC_screenshota.jpg" alt="Screenshot of the Administrative and Professional Staff Advisory Committee  Web site" width="250" height="382" /><p class="wp-caption-text">The APSAC Web Site</p></div>
<h3>Documents Pose a Challenge</h3>
<p>The Web site for <abbr title="Administrative and Professional Staff Advisory Committee ">APSAC </abbr>isn&#8217;t all that large, but it does pose a serious challenge to accessibility: the site has archives of dozens of downloadable documents, most of them in PDF format.</p>
<p>These include</p>
<ul>
<li>Meeting Minutes,</li>
<li>Newsletters</li>
<li>Governing documents &#8211; the memos establishing the committee, the bylaws, and the strategic plan</li>
</ul>
<h3>Everyone Benefits from Accessible PDFs</h3>
<p>In order to be accessible, a PDF must be tagged which can be a long and complicated process, depending on the way the source document was constructed. The advantages are that an accessible PDF benefits everyone. Documents can then be indexed by search engines; they are easier to navigate and are more available to mobile devices.</p>
<p><abbr title="Administrative and Professional Staff Advisory Committee ">APSAC </abbr>Secretary Susan Gianni met with us in the late summer to create a template source document for the meeting minutes that results in more accessible PDFs.  And <abbr title="Administrative and Professional Staff Advisory Committee ">APSAC </abbr>Web editors are in the process of retrofitting all of the existing documents, so that they are compliant with our <a href="http://webs.purduecal.edu/webaccessibility/web-accessibility-policy/">Web Accessibility Policy</a>.</p>
<h3>Commitment to Accessibility</h3>
<p>We applaud <abbr title="Administrative and Professional Staff Advisory Committee ">APSAC</abbr>&#8216;s commitment to making sure that their site and documents meet the standards to provide equal access and equal opportunities to people with and without disabilities!</p>
]]></content:encoded>
			<wfw:commentRss>http://webs.purduecal.edu/webaccessibility/2013/01/11/partner-01-11-13/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Partner of the Week: Jennifer Muha</title>
		<link>http://webs.purduecal.edu/webaccessibility/2013/01/04/partner-01-04-13/</link>
		<comments>http://webs.purduecal.edu/webaccessibility/2013/01/04/partner-01-04-13/#comments</comments>
		<pubDate>Fri, 04 Jan 2013 22:14:03 +0000</pubDate>
		<dc:creator>Pamela Riesmeyer</dc:creator>
				<category><![CDATA[Web Accessibility Partners]]></category>

		<guid isPermaLink="false">http://webs.purduecal.edu/webaccessibility/?p=797</guid>
		<description><![CDATA[The Mushroom Factor Sometimes when we&#8217;re working with a Web site content editor, we encounter what might be referred to as the &#8220;Mushroom Factor&#8220;. Owners of old houses are familiar with this: you start what should be a small project, like painting a room. The next thing you know, the job has mushroomed to the [...]]]></description>
			<content:encoded><![CDATA[<h3>The Mushroom Factor</h3>
<p><br class="spacer_" /></p>
<div id="attachment_798" class="wp-caption alignright" style="width: 229px"><img class="size-full wp-image-798" title="Academic Outreach &amp; Contract Training site - screen shot" src="http://webs.purduecal.edu/webaccessibility/files/AOCT_Jennifer_Muha.jpg" alt="screen shot for Academic Outreach &amp; Contract Training site" width="219" height="442" /><p class="wp-caption-text">Academic Outreach &amp; Contract Training Web site</p></div>
<p><br class="spacer_" /></p>
<p>Sometimes when we&#8217;re working with a Web site content editor, we encounter what might be referred to as the &#8220;<strong>Mushroom Factor</strong>&#8220;. Owners of old houses are familiar with this: you start what should be a small project, like painting a room. The next thing you know, the job has mushroomed to the point where you&#8217;re tearing out the plaster and lathe, replacing the electrical wiring along with a few studs and the insulation and putting up dry wall.</p>
<p>In Web site terms, you may have a few new lines of copy or a new PDF to publish and link to from an existing page. You check the PDF for accessibility, make a few adjustments and you&#8217;re ready to upload. The page where the link to the document will reside was created some time ago, so there&#8217;s a good chance that parts of it may not meet our <a href="http://webs.purduecal.edu/webaccessibility/web-accessibility-policy/">Web Accessibility Policy Guidelines</a>. You take a look at the page, and you realize just how far short it falls. Your update goes from the addition of a simple new link, to reworking the page.</p>
<p>But the good news is that, unlike an old house, a Web page is just HTML, and fixing what&#8217;s wrong most likely won&#8217;t take all that long, when you know what to do and why you&#8217;re doing it.</p>
<h3>Partner of the Week &#8211; Jennifer Muha</h3>
<p>Our <strong>Web Accessibility Partner for the Week of January 4th</strong> found herself in just that position. <strong>Jennifer Muha</strong> is the graduate assistant who edits the <a href="http://webs.purduecal.edu/aoct/">Academic Outreach &amp; Contract Training  site</a>. She had an updated registration form in PDF format which needed to be linked to from the <a href="http://webs.purduecal.edu/aoct/traditional-instruction/exam-preps-and-reviews/fundamentals-of-engineering-exam-review/ ">Fundamentals of Engineering exam page</a>.</p>
<h3>Typical Issues</h3>
<p>The page itself was first created in 2010, so there were a number of issues:</p>
<ul>
<li>A lack of structure.
<ul>
<li>What should have been a heading was a bold paragraph</li>
<li>What should have been a bold paragraph with styling to make it stand out, was a heading</li>
</ul>
</li>
<li>The PDF was not identified as a PDF so that a visitor might expect to have the link open another Web page</li>
<li>Several links opened new windows without warning &#8211; confusing to someone with cognitive difficulties</li>
<li>Large blocks of text were in italics which can be extremely hard to read</li>
<li>Some text which was not a link was underlined which can be confusing since we&#8217;re conditioned to expect that any underlined text on a Web page is a link.</li>
<li>Visitors were told to look for a link later in the copy when it would have been easier to just provide the link when it was first mentioned.</li>
<li>The text for one line was red, making it difficult to read against a white background.</li>
<li>Several links were written out as URLs rather than in human readable form,  which can be very difficult for a screen reader user to listen to. For example:
<ul>
<li>
<p>Here is the original link text and a recording of that text as read by the JAWS screen reader software: <br />
 <a href="https://engineering.purdue.edu/Engr/Academics/FE_FS_Exams/?pp=1" target="_blank">https://engineering.purdue.edu/Engr/Academics/FE_FS_Exams/?pp=1</a><br />
 <a href="http://webs.purduecal.edu/webaccessibility/files/jaws_rawURL_010713.mp3">Raw URL link text as read by the JAWS screen reader</a></p>
</li>
<li>
<p>Here is the revised link text, in a more human readable form, and a recording of that link as read by the JAWS screen reader software: <br />
 <a rel="external" href="https://engineering.purdue.edu/Engr/Academics/FE_FS_Exams/?pp=1" target="_blank">Register for the exam and learn more about the National Council of Examiners for Engineering and Surveying<span class="new-window"> [Opens in New Window]</span></a> <br />
 <a href="http://webs.purduecal.edu/webaccessibility/files/jaws_LinkText_010713.mp3"></a></p>
<p>As you can tell, in the human readable version, the screen reader user is also alerted to the fact that the link will open a new window, unlike with the raw URL version.</p>
</li>
</ul>
</li>
</ul>
<p>We want to stress that these issues are not all that unusual. They show up on many of the legacy pages that we review for compliance with our <a href="http://webs.purduecal.edu/webaccessibility/web-accessibility-policy/">Web Accessibility Policy</a>. They&#8217;re the result of outdated practices and archaic information and just need to be brought up to date.</p>
<h3>Fast Response!</h3>
<p>And that&#8217;s just what Jennifer did. We helped Jennifer update the PDF, and then sat down with her to talk about the rest of the content and the changes required. Within 20 minutes of our conversation, Jennifer had brought the page into compliance,  making it more accessible to everyone!  Her quick response and her understanding of what needed to be done are just two of the reasons why we&#8217;re proud to name <strong>Jennifer Muha our Web Accessibility Partner of the Week</strong>!</p>
]]></content:encoded>
			<wfw:commentRss>http://webs.purduecal.edu/webaccessibility/2013/01/04/partner-01-04-13/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
<enclosure url="http://webs.purduecal.edu/webaccessibility/files/jaws_rawURL_010713.mp3" length="163447" type="audio/mpeg" />
<enclosure url="http://webs.purduecal.edu/webaccessibility/files/jaws_LinkText_010713.mp3" length="135026" type="audio/mpeg" />
		</item>
		<item>
		<title>Partner of the Week and of the Month: Office of Institutional Research and Assessment and Dell Dumas</title>
		<link>http://webs.purduecal.edu/webaccessibility/2012/12/28/partner-12-28-12/</link>
		<comments>http://webs.purduecal.edu/webaccessibility/2012/12/28/partner-12-28-12/#comments</comments>
		<pubDate>Fri, 28 Dec 2012 16:04:39 +0000</pubDate>
		<dc:creator>Pamela Riesmeyer</dc:creator>
				<category><![CDATA[Web Accessibility Partners]]></category>

		<guid isPermaLink="false">http://webs.purduecal.edu/webaccessibility/?p=783</guid>
		<description><![CDATA[We&#8217;re doing a two for one for the final week of December. We are recognizing the Office of Institutional Research and Assessment, under the direction of Gillian Leonard, as our Partner of the Week for December 28th, and an important part of that office, Secretary Dell Dumas, as our Partner of the Month for December. [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;re doing a two for one for the final week of December.</p>
<div id="attachment_786" class="wp-caption alignright" style="width: 268px"><a href="http://webs.purduecal.edu/oira/data-snapshot-volume-two-august-2012/"><img class="size-full wp-image-786" title="Screenshot of the OIRA Data Snapshot Web Page for August 2012" src="http://webs.purduecal.edu/webaccessibility/files/oira_snapshot_a.jpg" alt="Screenshot of the OIRA Data Snapshot Web Page for August 2012" width="258" height="378" /></a><p class="wp-caption-text">Web Page Screenshot</p></div>
<p>We are recognizing the <a href="http://webs.purduecal.edu/oira">Office of Institutional Research and Assessment</a>, under the direction of Gillian Leonard, as our <strong>Partner of the Week</strong> for December 28th, and an important part of that office, <strong>Secretary Dell Dumas</strong>, as our <strong>Partner of the Month</strong> for December.</p>
<h3>Data Presents Special Challenges</h3>
<p>Here&#8217;s why: The <abbr title="office of institutional research and assessment">OIRA</abbr> faces major challenges due to the nature of the information that it puts on its Web site. Its job is to provide data about Purdue Calumet and charts and graphs and numbers can be difficult to present in an accessible fashion, even for those who do not use assistive technology.</p>
<h3>Proactive Efforts</h3>
<div style="float: right; clear: right; padding: 1em 0 1em 1em; width: 258px; margin-left: 2em;">
<div id="attachment_787" class="wp-caption alignright" style="width: 268px"><a href="http://webs.purduecal.edu/oira/files/2012/10/IRA-News-Brief-FINAL.pdf"><img class="size-full wp-image-787" title="Screen shot of the OIRA Data Snapshot PDF  for August 2012" src="http://webs.purduecal.edu/webaccessibility/files/oira_snapshot_pdf_a.jpg" alt="Screen shot of the OIRA Data Snapshot PDF  for August 2012" width="258" /></a><p class="wp-caption-text">PDF Screenshot</p></div>
</div>
<p>The office has met with University Relations on several occasions over the past few months, to talk about the <a href="http://webs.purduecal.edu/webaccessibility/web-accessibility-policy/">Web Accessibility Policy</a> and guidelines. One success story is the <a href="http://webs.purduecal.edu/oira/data-snapshot-volume-two-august-2012/">Data Snapshot</a>, a periodic news brief published as a PDF by the OIRA, containing interesting information about the history of Purdue Calumet, or how the campus matches up against other schools. As with most PDFs, the document requires a great deal of work to make it accessible. Beginning in the fall, we began helping the OIRA retrofit the PDFs. We also helped to create Web pages duplicating those PDFs, to make sure that the information is available to everyone, since HTML is the most accessible format.</p>
<h3>Partner of the Month</h3>
<p>Every year, the <abbr id="Office of Institutional Research and Assessment" title="Office of Institutional Research and Assessment">OIRA </abbr>publishes a Data Digest which is a compilation of statistics about Purdue Calumet. And this year, it is being produced in an accessible form — published as Web pages and as a PDF. Much of the credit for this effort goes to <strong>Dell Dumas</strong>. She is responsible for putting together the Data Digest and the Data Snapshot. We have worked closely with Dell to produce the accessible versions and we could not have done this without her dedication and focused efforts.</p>
<h3>Still Challenges Ahead</h3>
<p>The <abbr id="Office of Institutional Research and Assessment" title="Office of Institutional Research and Assessment">OIRA </abbr>still has much work to do on the site, due to the sheer volume of archived documents which must be retrofitted and link text which needs to be changed to be more screen — reader friendly. But the office is committed to getting that work done. This is why we are proud to recognize the <abbr id="Office of Institutional Research and Assessment" title="Office of Institutional Research and Assessment"><strong>OIRA </strong></abbr>as our <strong>Web Accessibility Partner of the Week</strong> and <strong>Dell Dumas</strong> as our <strong>Web Accessibility Partner for the month of December</strong>!</p>
]]></content:encoded>
			<wfw:commentRss>http://webs.purduecal.edu/webaccessibility/2012/12/28/partner-12-28-12/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Partner of the Week: John Talaga</title>
		<link>http://webs.purduecal.edu/webaccessibility/2012/12/21/partner-12-21-12/</link>
		<comments>http://webs.purduecal.edu/webaccessibility/2012/12/21/partner-12-21-12/#comments</comments>
		<pubDate>Fri, 21 Dec 2012 21:31:35 +0000</pubDate>
		<dc:creator>Pamela Riesmeyer</dc:creator>
				<category><![CDATA[Web Accessibility Partners]]></category>

		<guid isPermaLink="false">http://webs.purduecal.edu/webaccessibility/?p=777</guid>
		<description><![CDATA[Our Web Accessibility Partner of the Week is John Talaga, Enterprise Systems Server Administrator! John is a member of the hard working team responsible for keeping the servers on which our Web sites and applications are hosted, humming. Accessibility from the Start John was assigned a project recently, to activate an online application for a [...]]]></description>
			<content:encoded><![CDATA[<p>Our <strong>Web Accessibility Partner of the Week</strong> is <strong>John Talaga</strong>, Enterprise Systems Server Administrator! John is a member of the hard working team responsible for keeping the servers on which our Web sites and applications are hosted, humming.</p>
<h3>Accessibility from the Start</h3>
<p>John was assigned a project recently, to activate an online application for a department, hoping to make life easier for students and for staff in filling out forms. He contacted us right away, asking that we check the application to see if it met our <a href="http://webs.purduecal.edu/webaccessibility/web-accessibility-policy/">Web Accessibility Policy Guidelines</a>.</p>
<p>We evaluated the site and quickly found that it fell far short of our guidelines.</p>
<p>John got in touch with the company that sold Purdue University Calumet the software, and brought us into the conversation. His contacts there assured us that an accessible version was available. They worked with John to set up that version to test. We evaluated this version of the application and it looks as if it&#8217;s going to work out well for everyone involved &#8211; the department which requested the application, the students and staff members who will be using it, whether or not  they require assistive technology.</p>
<h3>Do it Right the First Time</h3>
<p>What we appreciate most about John&#8217;s effort is that he helped us all do this right the first time. He reached out to us early in the process and he allowed us to be part of the conversation with the vendor. In this way, we can help assure that a project is accessible from the beginning, before time and effort are put into developing it. And we don&#8217;t have to spend more time and effort in retrofitting or remediating the application, potentially delaying the project.</p>
<h3>A Timely Choice</h3>
<p>When Purdue Calumet&#8217;s Enterprise Systems develops an application or we create a Web site or a Web page, we can assure that we are meeting the accessibility guidelines outlined in our policy.</p>
<p>But when we buy software from a vendor, we don&#8217;t have that same confidence, unless we insist on it. And we don&#8217;t always know what questions to ask, or what steps to take to make sure that the software is accessible. <a href="http://www.purdue.edu/webaccessibility/"></a></p>
<p><a href="http://www.purdue.edu/webaccessibility/">Purdue West Lafayette&#8217;s Web Accessibility Committee</a> has provided a page of  <a href="http://webs.purduecal.edu/webaccessibility/files/Tips_for_Procuring_Universally_Accessible_Software.pdf">Tips for Procuring Universally Accessible Software(PDF)</a>. The advice is simple and straightforward and it includes links to resources for more information.</p>
<h2>Another Partner Next Week</h2>
<p>Next Friday, we&#8217;ll recognize the final <strong>Web Accessibility Partner of the Week</strong> for 2012, and name a <strong>Web Accessibility Partner of the Month for December</strong>!</p>
]]></content:encoded>
			<wfw:commentRss>http://webs.purduecal.edu/webaccessibility/2012/12/21/partner-12-21-12/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Partner of the Week: Staci Trekles</title>
		<link>http://webs.purduecal.edu/webaccessibility/2012/12/14/partner-of-the-week-12-14-12/</link>
		<comments>http://webs.purduecal.edu/webaccessibility/2012/12/14/partner-of-the-week-12-14-12/#comments</comments>
		<pubDate>Fri, 14 Dec 2012 20:56:00 +0000</pubDate>
		<dc:creator>Pamela Riesmeyer</dc:creator>
				<category><![CDATA[Web Accessibility Partners]]></category>

		<guid isPermaLink="false">http://webs.purduecal.edu/webaccessibility/?p=767</guid>
		<description><![CDATA[Congratulations to our Web Accessibility Partner of the Week, Staci Trekles, Clinical Associate Professor, Instructional Technology of the School of Education! Building on a Strong Foundation Staci is Web master with primary responsibility for the School of Education site. She had already built some accessibility features into the pages, and has been focused on bringing [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.purduecal.edu/education/"><img class="alignright size-full wp-image-770" title="Screenshot of the School of Education Web Page" src="http://webs.purduecal.edu/webaccessibility/files/screenshot_education_1.jpg" alt="Screenshot of the School of Education Web Page" width="206" height="437" /></a></p>
<p>Congratulations to our <strong>Web Accessibility Partner of the Week, Staci Trekles</strong>, Clinical Associate Professor, Instructional Technology of the School of Education!</p>
<h3>Building on a Strong Foundation</h3>
<p>Staci is Web master with primary responsibility for <a href="http://www.purduecal.edu/education/">the School of Education site</a>. She had already built some accessibility features into the pages, and has been focused on bringing them into even greater compliance with <a href="http://webs.purduecal.edu/webaccessibility/web-accessibility-policy/">our Web Accessibility Policy</a>.</p>
<h3>Tackling the Legacy Pages</h3>
<p>One of the most time-consuming tasks in making a site compliant with accessibility guidelines is reviewing and re-mediating the existing pages, especially if the site was built some time ago. As all of us are, Staci has been going through the School of Education site, cleaning up the code and making improvements as she goes. Her success is evident both in our automated Compliance Sheriff scans, as well as manual evaluation of the pages.</p>
<h3>Added Benefits for Her Students</h3>
<p>Staci teaches a class in Human Issues in Technology which focuses on assistive technology in the classroom. She also teaches Web Design, including techniques for making sites accessible, so she understands the requirements  to meet the standards. She also gives her students a good grounding in accessible electronic and information technology which gives them an additional skill to list on their resumés as well as an advantage over other aspiring Web designers / developers when they enter the job market.</p>
<h2>What’s Ahead</h2>
<p>We will announce another Web Accessibility Partner of the Week next Friday – along with the Web Accessibility Partner for December. The issues which those Partners face may be ones with which you&#8217;re struggling on your site, and the solution they found may help you solve your issue! We’re all in this together, making the Purdue Calumet Web site accessible to everyone!</p>
]]></content:encoded>
			<wfw:commentRss>http://webs.purduecal.edu/webaccessibility/2012/12/14/partner-of-the-week-12-14-12/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Partner of the Week: Office of Academic Affairs</title>
		<link>http://webs.purduecal.edu/webaccessibility/2012/12/07/partner-12-07-12/</link>
		<comments>http://webs.purduecal.edu/webaccessibility/2012/12/07/partner-12-07-12/#comments</comments>
		<pubDate>Fri, 07 Dec 2012 19:04:00 +0000</pubDate>
		<dc:creator>Pamela Riesmeyer</dc:creator>
				<category><![CDATA[Web Accessibility Partners]]></category>

		<guid isPermaLink="false">http://webs.purduecal.edu/webaccessibility/?p=743</guid>
		<description><![CDATA[Our Web Accessibility Partners of the Week are the content editors for the Office of Academic Affairs Web site.  Under the direction of Vice Chancellor for Academic Affairs, Dr. Ralph Rogers, Administrative Assistant Deborah McGlashan, and Content Editors Rebecca DeYoung and Cindy Huntoon are responsible, directly, for two sites: Academic Affairs and New Faculty Orientation. [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_746" class="wp-caption alignright" style="width: 360px"><a href="http://webs.purduecal.edu/acadaffrs"><img class="size-full wp-image-746" title="Screen shot of the home page of the Academic Affairs Web site" src="http://webs.purduecal.edu/webaccessibility/files/AcadAffrs_120712a.jpg" alt="Screen shot of the home page of the Academic Affairs Web site" width="350" height="276" /></a><p class="wp-caption-text">Academic Affairs Web site</p></div>
<p>Our <strong>Web Accessibility Partners of the Week</strong> are the content editors for the <strong>Office of Academic Affairs</strong> Web site.  Under the direction of Vice Chancellor for Academic Affairs, Dr. Ralph Rogers, Administrative Assistant Deborah McGlashan, and Content Editors Rebecca DeYoung and Cindy Huntoon are responsible, directly, for two sites: <a href="http://webs.purduecal.edu/acadaffrs">Academic Affairs</a> and <a href="http://webs.purduecal.edu/nfo">New Faculty Orientation</a>.</p>
<h3>What Makes Them Special</h3>
<p>This team is proactive when it comes to accessibility. All three attended the Web Accessibility Awareness sessions as well as one-on-one training in accessible documents.</p>
<p>From the time they learned about <a href="http://webs.purduecal.edu/webaccessibility/web-accessibility-policy/">the Web Accessibility Policy</a>, they began assessing the content of their sites. They worked with <a href="http://webs.purduecal.edu/advancement/university-relations/">University Relations</a> to edit and reformat pages with accessibility in mind.</p>
<p>For example, subheadings have been added to a page that would otherwise be a blob of text, to make it easier for screen reader users to navigate.  And the pages from the New Faculty Orientation handbook have been published in a much more accessible format (<abbr title="Hypertext Markup Language">HTML</abbr>) rather than just offered as a PDF.</p>
<div style="clear: right; width: 375px; float: right;">
<div id="attachment_747" class="wp-caption alignright" style="width: 359px"><a href="http://webs.purduecal.edu/nfo"><img class="size-full wp-image-747" title="Screen shot of the home page for the New Faculty Orientation Web site" src="http://webs.purduecal.edu/webaccessibility/files/NFO_120712.jpg" alt="Screen shot of the home page for the New Faculty Orientation Web site" width="349" height="260" /></a><p class="wp-caption-text">New Faculty Orientation Web site</p></div>
</div>
<h3>Compliance Sheriff Scores</h3>
<p>As a result of the work these editors are doing, scans of the Academic Affairs site by our automated evaluation software, Compliance Sheriff, show the site to be nearly 100% compliant with our Web Accessibility Policy Guidelines.  The New Faculty Orientation site is improving as well, as the team continues to work on the content to make it more accessible.</p>
<h3>Dedication and Commitment</h3>
<p>It’s this type of dedication and commitment from content editors like Deb, Rebecca and Cindy, that moves us closer to our goal of 100% compliance by March of 2014. And we are proud to recognize their accomplishments!</p>
<h2>Just a Few Easy Things</h2>
<p>As our content editors continue to discover, making a Web page compliant with our policy is easy. There are just a few <a href="http://webs.purduecal.edu/webaccessibility/best-practices/">Standards</a> to remember :</p>
<ul>
<li>Adding meaningful alternate text to images; </li>
<li>Using headings and lists instead of bold paragraphs; </li>
<li>Adding extra information to tables;</li>
<li> Thinking of links as signposts, telling a visitor where they are about to go.</li>
<li>And sometimes, putting aside “the way we have always done things”. </li>
</ul>
<p>Next Friday, we’ll recognize another <strong>Web Accessibility Partner of the Week</strong> &#8211; an office, a department, a school or individuals who are working hard to make the Purdue Calumet Web site accessible to everyone!</p>
]]></content:encoded>
			<wfw:commentRss>http://webs.purduecal.edu/webaccessibility/2012/12/07/partner-12-07-12/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Partner of the Month: Bienjen Kortmann</title>
		<link>http://webs.purduecal.edu/webaccessibility/2012/11/30/partner-of-the-month-11-12/</link>
		<comments>http://webs.purduecal.edu/webaccessibility/2012/11/30/partner-of-the-month-11-12/#comments</comments>
		<pubDate>Fri, 30 Nov 2012 22:32:50 +0000</pubDate>
		<dc:creator>Pamela Riesmeyer</dc:creator>
				<category><![CDATA[Web Accessibility Partners]]></category>

		<guid isPermaLink="false">http://webs.purduecal.edu/webaccessibility/?p=724</guid>
		<description><![CDATA[Our Web Accessibility Partner for the Month of November is Information Services Web Communications Coordinator Bienjen Kortmann. Bienjen is responsible for the Library and the Information Services Web sites, two very large sites with many complicated components. She also works to help develop other Web applications and projects. Putting the Policy into Practice Bienjen has [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_728" class="wp-caption alignright" style="width: 256px"><a href="http://webs.purduecal.edu/library"><img class="size-full wp-image-728" title="Screen shot of Library Web site home page" src="http://webs.purduecal.edu/webaccessibility/files/libraryv1a.jpg" alt="Purdue University Calumet Library home page" width="246" height="214" /></a><p class="wp-caption-text">Purdue University Calumet Library Home Page</p></div>
<p><strong>Our Web Accessibility Partner for the Month of November</strong> is Information Services Web Communications Coordinator <strong>Bienjen Kortmann</strong>.</p>
<p>Bienjen is responsible for <a href="http://webs.purduecal.edu/library">the Library</a> and <a href="http://webs.purduecal.edu/infosvcs">the Information Services Web sites</a>, two very large sites with many complicated components. She also works to help develop other Web applications and projects.</p>
<h3>Putting the Policy into Practice</h3>
<div class="alignright" style="clear: right; width: 246px; margin-left: 2em;">
<div id="attachment_727" class="wp-caption alignright" style="width: 256px"><a href="http://webs.purduecal.edu/infosvcs"><img class="size-full wp-image-727" title="Screen shot of Information Services Web site home page" src="http://webs.purduecal.edu/webaccessibility/files/infosvcs_v1a.jpg" alt="Information Services Web site home page" width="246" height="303" /></a><p class="wp-caption-text">Information Services Home Page</p></div>
</div>
<p>Bienjen has been a member of the Electronic &amp; Information Technology Accessibility Action and Strategic Committees since they were formed in the summer of 2011. She has a good understanding of the Web Accessibility Policy guidelines and she puts those guidelines into practice for every project on which she works.</p>
<h3>Retrofitting a Site is More Expensive</h3>
<p>Bienjen makes sure that accessibility is baked in at the beginning of a project, understanding that it is so much harder and so much more expensive in terms of time and people-hours to retrofit a site or an application, rather than to start with accessibility in mind.  As experts in the field of accessibility, Brian Wentz, Paul T. Jaeger,  and Jonathan Lazar wrote regarding <a href="http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/3666/3077">the cost of retrofitting a Web site</a> in the online journal <em>First Monday</em>:</p>
<p class="indent">The cost of accessibility when carefully planned and designed is almost zero. However, extreme challenges and significant expenses are often involved in the process of retrofitting an existing website for accessibility.</p>
<h3>Sharing Her Wealth of Knowledge</h3>
<p>She also is willing to share her knowledge and to offer support to others who need assistance, which is a key characteristic of a Partner.</p>
<p>We are proud to have Bienjen on our team and happy to name her our <strong>Web Accessibility Partner of the Month for November</strong>!</p>
]]></content:encoded>
			<wfw:commentRss>http://webs.purduecal.edu/webaccessibility/2012/11/30/partner-of-the-month-11-12/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
