<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.3.1" -->
<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: Suddenly Accessibility Is Beautiful</title>
	<link>http://www.alttags.org/accessibility/suddenly-accessibility-is-beautiful/</link>
	<description>Accessibility, Usability and Web Standards</description>
	<pubDate>Tue, 06 Jan 2009 00:25:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Elaine Nelson</title>
		<link>http://www.alttags.org/accessibility/suddenly-accessibility-is-beautiful/#comment-28</link>
		<dc:creator>Elaine Nelson</dc:creator>
		<pubDate>Tue, 04 May 2004 17:28:17 +0000</pubDate>
		<guid>http://www.alttags.org/accessibility/suddenly-accessibility-is-beautiful/#comment-28</guid>
		<description>We've made a committment to standards &#38; accessibility, mostly because of my own persistence :) at &lt;a href="http://www.pierce.ctc.edu/"&gt;Pierce College in Washington&lt;/a&gt;.  (forgive the flash navigation, it's a legacy piece.)

I guess I've been lucky; I picked up the standards/accessibilty bug of my own accord, and I've had good support from my boss and most of my internal clients.  

Here's what I see as the two biggest problems facing educational sites: fewer resources and distributed site development.

Colleges and universities, generally, have far smaller Web development staffs than your average corporation.  Our school serves something on the order of 30,000 individuals (10k FTE, IIRC) every year, and I'm our Web staff, along with a part-time assistant: for design, development, maintenance, and strategy.  So when you have a tiny staff trying to fill the needs of a large community, there often isn't time to climb the learning curve of standards &#38; accessibility.  (The same is true to some extent for non-profits; before this, I worked for a local non-profit -- the Web piece of my job was about 1/4.)  That, and even when you have time to learn, it's hard to find time to put that into practice, esp. at first when you're converting big chunks of Web.

This factor combines with the very nature of the educational enterprise -- in a lot of schools, many people are creating and maintaining Web sites, few of them with any depth of training.  (It can be like the Wild West!)  Some schools are turning to CMS's to rein in their development and to provide a common foundation; unfortunately, it can be hard to find a CMS that provides standards &#38; accessibility compliance out of the box.

One positive thing that I've noticed lately is that the &lt;a href="http://www.usask.ca/web_project/uwebd/"&gt;University Web Developers list&lt;/a&gt; seems to be getting a lot more traffic from people looking to go the standards/accessibility/CSS route.

I wish I knew whether going to the more "modern" mode of development had saved us any bandwidth -- we started going there several years ago (mid-2001), and I wasn't keeping good stats reports then.  I will say that it eases some tasks, more with sub-sites than the megalith which is the site's core.  (I was able to covert &lt;a href="http://www.pierce.ctc.edu/studentlife/slam/"&gt;our school's lit mag site&lt;/a&gt; to colors matching the new cover in about an hour...and that included picking the colors out of the cover that I wanted.  The only bit that isn't done is changing the tab borders.)

okay, so that was a long response...I suppose it's something that's been eating at my mind for a while.

(oh, nice site, too.  I found you by way of the CSS Vault, and I'll definitely be adding this to my aggregator.)</description>
		<content:encoded><![CDATA[<p>We&#8217;ve made a committment to standards &#38; accessibility, mostly because of my own persistence <img src='http://www.alttags.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> at <a href="http://www.pierce.ctc.edu/">Pierce College in Washington</a>.  (forgive the flash navigation, it&#8217;s a legacy piece.)</p>
<p>I guess I&#8217;ve been lucky; I picked up the standards/accessibilty bug of my own accord, and I&#8217;ve had good support from my boss and most of my internal clients.  </p>
<p>Here&#8217;s what I see as the two biggest problems facing educational sites: fewer resources and distributed site development.</p>
<p>Colleges and universities, generally, have far smaller Web development staffs than your average corporation.  Our school serves something on the order of 30,000 individuals (10k FTE, IIRC) every year, and I&#8217;m our Web staff, along with a part-time assistant: for design, development, maintenance, and strategy.  So when you have a tiny staff trying to fill the needs of a large community, there often isn&#8217;t time to climb the learning curve of standards &#38; accessibility.  (The same is true to some extent for non-profits; before this, I worked for a local non-profit &#8212; the Web piece of my job was about 1/4.)  That, and even when you have time to learn, it&#8217;s hard to find time to put that into practice, esp. at first when you&#8217;re converting big chunks of Web.</p>
<p>This factor combines with the very nature of the educational enterprise &#8212; in a lot of schools, many people are creating and maintaining Web sites, few of them with any depth of training.  (It can be like the Wild West!)  Some schools are turning to CMS&#8217;s to rein in their development and to provide a common foundation; unfortunately, it can be hard to find a CMS that provides standards &#38; accessibility compliance out of the box.</p>
<p>One positive thing that I&#8217;ve noticed lately is that the <a href="http://www.usask.ca/web_project/uwebd/">University Web Developers list</a> seems to be getting a lot more traffic from people looking to go the standards/accessibility/CSS route.</p>
<p>I wish I knew whether going to the more &#8220;modern&#8221; mode of development had saved us any bandwidth &#8212; we started going there several years ago (mid-2001), and I wasn&#8217;t keeping good stats reports then.  I will say that it eases some tasks, more with sub-sites than the megalith which is the site&#8217;s core.  (I was able to covert <a href="http://www.pierce.ctc.edu/studentlife/slam/">our school&#8217;s lit mag site</a> to colors matching the new cover in about an hour&#8230;and that included picking the colors out of the cover that I wanted.  The only bit that isn&#8217;t done is changing the tab borders.)</p>
<p>okay, so that was a long response&#8230;I suppose it&#8217;s something that&#8217;s been eating at my mind for a while.</p>
<p>(oh, nice site, too.  I found you by way of the CSS Vault, and I&#8217;ll definitely be adding this to my aggregator.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirk Biglione</title>
		<link>http://www.alttags.org/accessibility/suddenly-accessibility-is-beautiful/#comment-8</link>
		<dc:creator>Kirk Biglione</dc:creator>
		<pubDate>Tue, 23 Mar 2004 02:49:35 +0000</pubDate>
		<guid>http://www.alttags.org/accessibility/suddenly-accessibility-is-beautiful/#comment-8</guid>
		<description>I'll go first, with a site that I know very little about.  The University of Flordia faired very well during this year's "Accessibility Shootout".  It's quite a nice site that is primarily standards based, but also makes great use of Flash in a non-obtrusive way.  This site is really very well done.

&lt;a href="http://www.ufl.edu/"&gt;University of Florida&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I&#8217;ll go first, with a site that I know very little about.  The University of Flordia faired very well during this year&#8217;s &#8220;Accessibility Shootout&#8221;.  It&#8217;s quite a nice site that is primarily standards based, but also makes great use of Flash in a non-obtrusive way.  This site is really very well done.</p>
<p><a href="http://www.ufl.edu/">University of Florida</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
