<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Common accessibility blunders</title>
	<atom:link href="http://segala.com/blog/common-accessibility-blunders/feed" rel="self" type="application/rss+xml" />
	<link>http://segala.com/blog/common-accessibility-blunders/</link>
	<description>Enabling a Reliable, Consistent and Trusted Experience</description>
	<pubDate>Tue, 06 Jan 2009 21:49:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Aido</title>
		<link>http://segala.com/blog/common-accessibility-blunders/#comment-972498</link>
		<dc:creator>Aido</dc:creator>
		<pubDate>Fri, 07 Nov 2008 11:15:22 +0000</pubDate>
		<guid isPermaLink="false">http://segala.com/?p=1317#comment-972498</guid>
		<description>@Sine A University the Web site should be compliant. Most Universities have Ability Officers assigned to manage both online and offline access for all.

Accessibility is something that is often over looked.  It should be built in, not bolted on.  If done right the site ends up being easier to manage.

A revamp is the perfect time to address the Web sites accessibility.  Sit down with the team to discuss the benefits of accessibility. If the University has an officer get them involved.

Start out by looking at the current issues people face with the existing site, run a poll or survey.  Both students and other users may highlight usability and accessibility issues the team may have over looked. The amount of effort put in now will be a huge benefit to the final revamped Web site.

If the Web site is CMS managed, the University could have the new templates and designs independently audited. This is a service we offer.

Lastly, assign someone on the team to be responsible for the accessibility of the new site.  This person does not have to be an expert as the delivery is a joint effort but it is always good to have at least one person asking questions. 

Granted, some research my be required on their behalf but we're always happy to help. If only to answer a few questions or offer advice.

Please feel free to contact me adrian[at]segala[dot]com</description>
		<content:encoded><![CDATA[<p>@Sine A University the Web site should be compliant. Most Universities have Ability Officers assigned to manage both online and offline access for all.</p>
<p>Accessibility is something that is often over looked.  It should be built in, not bolted on.  If done right the site ends up being easier to manage.</p>
<p>A revamp is the perfect time to address the Web sites accessibility.  Sit down with the team to discuss the benefits of accessibility. If the University has an officer get them involved.</p>
<p>Start out by looking at the current issues people face with the existing site, run a poll or survey.  Both students and other users may highlight usability and accessibility issues the team may have over looked. The amount of effort put in now will be a huge benefit to the final revamped Web site.</p>
<p>If the Web site is CMS managed, the University could have the new templates and designs independently audited. This is a service we offer.</p>
<p>Lastly, assign someone on the team to be responsible for the accessibility of the new site.  This person does not have to be an expert as the delivery is a joint effort but it is always good to have at least one person asking questions. </p>
<p>Granted, some research my be required on their behalf but we&#8217;re always happy to help. If only to answer a few questions or offer advice.</p>
<p>Please feel free to contact me adrian[at]segala[dot]com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sine Haniefy</title>
		<link>http://segala.com/blog/common-accessibility-blunders/#comment-971025</link>
		<dc:creator>Sine Haniefy</dc:creator>
		<pubDate>Thu, 06 Nov 2008 09:53:46 +0000</pubDate>
		<guid isPermaLink="false">http://segala.com/?p=1317#comment-971025</guid>
		<description>I am NOT solely responsible for the University of Cincinnati's website, but have some input about how it looks and functions.  The team is just beginning to look at a revamp, so finding this blog is timely for me. 

As a public institution, we must keep accessibility issues in mind all the time, but to date, our web presence is not doing that very well.  I am interested in finding out more about how we can do a better job of that.  Suggested readings?</description>
		<content:encoded><![CDATA[<p>I am NOT solely responsible for the University of Cincinnati&#8217;s website, but have some input about how it looks and functions.  The team is just beginning to look at a revamp, so finding this blog is timely for me. </p>
<p>As a public institution, we must keep accessibility issues in mind all the time, but to date, our web presence is not doing that very well.  I am interested in finding out more about how we can do a better job of that.  Suggested readings?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
