<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Accessibility at Educational Institutions</title>
	<link>http://www.accessibilityblog.com/2006/10/09/accessibility-at-educational-institutions/</link>
	<description>Raising the awareness of Web Site Accessibility and Marketing.</description>
	<pubDate>Sun, 20 Jul 2008 14:23:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Joe Dolson</title>
		<link>http://www.accessibilityblog.com/2006/10/09/accessibility-at-educational-institutions/#comment-15100</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Mon, 16 Oct 2006 04:25:10 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/10/09/accessibility-at-educational-institutions/#comment-15100</guid>
		<description>Thanks for your comments, Jesse - actually, the only reason I'm specifically citing compliance with WCAG is because that is the baseline that the Hannon Hill study used to rate college websites.  And, although I don't in fact agree 100% with WCAG's ratings, some level of compliance is certainly necessary in order to provide a reasonably accessible site.

I wish I knew exactly what priority level the study was measuring; I searched around the site and couldn't find a specific document which contained the study's findings.

There are certainly many web developers who know something about web standards and accessibility: but there are even MORE colleges with webmasters who don't. 

Your comments about the lack of a comment preview are much appreciated: I've installed a plugin which provides a decent JavaScript live preview.  Won't work for non-js user agents, but the enhancement will at least help some users.

Thanks!

Joe</description>
		<content:encoded><![CDATA[<p>Thanks for your comments, Jesse - actually, the only reason I&#8217;m specifically citing compliance with <acronym title="Web Content Accessibility Guidelines">WCAG</acronym> is because that is the baseline that the Hannon Hill study used to rate college websites.  And, although I don&#8217;t in fact agree 100% with <acronym title="Web Content Accessibility Guidelines">WCAG</acronym>&#8217;s ratings, some level of compliance is certainly necessary in order to provide a reasonably accessible site.</p>
<p>I wish I knew exactly what priority level the study was measuring; I searched around the site and couldn&#8217;t find a specific document which contained the study&#8217;s findings.</p>
<p>There are certainly many web developers who know something about web standards and accessibility: but there are even MORE colleges with webmasters who don&#8217;t. </p>
<p>Your comments about the lack of a comment preview are much appreciated: I&#8217;ve installed a plugin which provides a decent JavaScript live preview.  Won&#8217;t work for non-js user agents, but the enhancement will at least help some users.</p>
<p>Thanks!</p>
<p>Joe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Rodgers</title>
		<link>http://www.accessibilityblog.com/2006/10/09/accessibility-at-educational-institutions/#comment-14926</link>
		<dc:creator>Jesse Rodgers</dc:creator>
		<pubDate>Fri, 13 Oct 2006 12:54:54 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/10/09/accessibility-at-educational-institutions/#comment-14926</guid>
		<description>I am sorry but I think you are exagerating the real problem even though I do agree with you that higher education web sites are messy at best. My real issue with what you are saying is that *compliance* with WCAG makes your site accessibile. I believe you have a site that is *accessible* but not following 100% of WCAG (which priority were they measuring against anyway?) recommendations. 

Colleges respond to complaints from people who can't access their content. If people aren't complaining, and no I am not saying 'this sucks' is a valid complaint, about specific issues in a constructive manner there is little for the web folks to do. 

I can certainly say with some confidence that University Web Developers list (has more than 14 people on it) is full of higher education web folks who care about accessibility and are actively doing something. 

http://www.usask.ca/web_project/uwebd/index.html

To back to the organizational mess that his academia... the real issue is that no one wants to take responsibility for the web or making decisions about it. Why? Staff, Faculty, Students, Alumni, etc all claim ownership and generally are not as enlightened about accessibility issues as the web folks are. Their complaints are generally about color, images, etc. All I am saying is that you being a little hard on the web folks and their skill set.

Now I have lost the rest of the text in my comment so please excuse typos. Without a preview anywhere I can't proof read (curse blogs and their poor usability) and all I can see are 5 lines of my submission.</description>
		<content:encoded><![CDATA[<p>I am sorry but I think you are exagerating the real problem even though I do agree with you that higher education web sites are messy at best. My real issue with what you are saying is that *compliance* with <acronym title="Web Content Accessibility Guidelines">WCAG</acronym> makes your site accessibile. I believe you have a site that is *accessible* but not following 100% of <acronym title="Web Content Accessibility Guidelines">WCAG</acronym> (which priority were they measuring against anyway?) recommendations. </p>
<p>Colleges respond to complaints from people who can&#8217;t access their content. If people aren&#8217;t complaining, and no I am not saying &#8216;this sucks&#8217; is a valid complaint, about specific issues in a constructive manner there is little for the web folks to do. </p>
<p>I can certainly say with some confidence that University Web Developers list (has more than 14 people on it) is full of higher education web folks who care about accessibility and are actively doing something. </p>
<p><a href="http://www.usask.ca/web_project/uwebd/index.html" >http://www.usask.ca/web_project/uwebd/index.html</a></p>
<p>To back to the organizational mess that his academia&#8230; the real issue is that no one wants to take responsibility for the web or making decisions about it. Why? Staff, Faculty, Students, Alumni, etc all claim ownership and generally are not as enlightened about accessibility issues as the web folks are. Their complaints are generally about color, images, etc. All I am saying is that you being a little hard on the web folks and their skill set.</p>
<p>Now I have lost the rest of the text in my comment so please excuse typos. Without a preview anywhere I can&#8217;t proof read (curse blogs and their poor usability) and all I can see are 5 lines of my submission.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.accessibilityblog.com/2006/10/09/accessibility-at-educational-institutions/#comment-14572</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Tue, 10 Oct 2006 00:45:37 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/10/09/accessibility-at-educational-institutions/#comment-14572</guid>
		<description>That's a great point - the sheer quantity of content produced very early on is a massive problem.  Add to that a problem which I distinctly remember - the transient nature of college website maintainers - and you can just imagine how difficult a job this must be.

I definitely remember an era where many departments and faculty depended on students to build and maintain their websites: those students graduated, moved on...the websites have stayed.  Unedited and inaccessible. (In both the "disabled can't read it" and the "gosh, I just don't know how to get into those pages to change them" manners...)</description>
		<content:encoded><![CDATA[<p>That&#8217;s a great point - the sheer quantity of content produced very early on is a massive problem.  Add to that a problem which I distinctly remember - the transient nature of college website maintainers - and you can just imagine how difficult a job this must be.</p>
<p>I definitely remember an era where many departments and faculty depended on students to build and maintain their websites: those students graduated, moved on&#8230;the websites have stayed.  Unedited and inaccessible. (In both the &#8220;disabled can&#8217;t read it&#8221; and the &#8220;gosh, I just don&#8217;t know how to get into those pages to change them&#8221; manners&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://www.accessibilityblog.com/2006/10/09/accessibility-at-educational-institutions/#comment-14571</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Tue, 10 Oct 2006 00:36:25 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/10/09/accessibility-at-educational-institutions/#comment-14571</guid>
		<description>My other company does business with probably 50% of the universities in the US and I'd have to say you're observations are right on the money. Frankly I'm surprised even though it amazes me how far behind the tech times they are. Not just as it concerns web accessibility but on all web practices in general. But there's probably a good reason for it: Many universities were some of the first to embrace the web, back when tables and font tags were king and they published copious amounts of content. Now, though, to get with it they have the deal with all of that content and are effectively stuck. The sheer volume of work it would entail to make such a transition is more than likely extremely daunting and probably what's holding them back.</description>
		<content:encoded><![CDATA[<p>My other company does business with probably 50% of the universities in the US and I&#8217;d have to say you&#8217;re observations are right on the money. Frankly I&#8217;m surprised even though it amazes me how far behind the tech times they are. Not just as it concerns web accessibility but on all web practices in general. But there&#8217;s probably a good reason for it: Many universities were some of the first to embrace the web, back when tables and font tags were king and they published copious amounts of content. Now, though, to get with it they have the deal with all of that content and are effectively stuck. The sheer volume of work it would entail to make such a transition is more than likely extremely daunting and probably what&#8217;s holding them back.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson Accessible Web Design &#124; New post at Accessibility Blog</title>
		<link>http://www.accessibilityblog.com/2006/10/09/accessibility-at-educational-institutions/#comment-14560</link>
		<dc:creator>Joe Dolson Accessible Web Design &#124; New post at Accessibility Blog</dc:creator>
		<pubDate>Mon, 09 Oct 2006 18:07:10 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/10/09/accessibility-at-educational-institutions/#comment-14560</guid>
		<description>[...] I was invited a couple weeks ago to redesign and contribute to Accessibility Blog, Matt Bailey&#8217;s blog on accessibility awareness and marketing. Today, I posted a brief article addressing the accessibility of college and university websites. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I was invited a couple weeks ago to redesign and contribute to Accessibility Blog, Matt Bailey&#8217;s blog on accessibility awareness and marketing. Today, I posted a brief article addressing the accessibility of college and university websites. [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.562 seconds -->
