<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">

<channel>
	<title>Curb Cut &#187; Community</title>
	<atom:link href="http://curbcut.net/category/community/feed/" rel="self" type="application/rss+xml" />
	<link>http://curbcut.net</link>
	<description>open and accessible</description>
	<lastBuildDate>Thu, 20 May 2010 06:07:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<cloud domain='curbcut.net' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
		<item>
		<title>Social Networking Accessibility</title>
		<link>http://curbcut.net/accessibility/social-networking-accessibility/</link>
		<comments>http://curbcut.net/accessibility/social-networking-accessibility/#comments</comments>
		<pubDate>Tue, 29 Jan 2008 07:36:45 +0000</pubDate>
		<dc:creator>Christopher Phillips</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Community]]></category>
		<category><![CDATA[Web 2.0]]></category>
		<category><![CDATA[Bebo]]></category>
		<category><![CDATA[disabilities]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[MySpace]]></category>
		<category><![CDATA[Yahoo]]></category>
		<category><![CDATA[YouTube]]></category>

		<guid isPermaLink="false">http://curbcut.net/accessibility/social-networking-accessibility/</guid>
		<description><![CDATA[Via Accesssites.org, a summary of a 21 page report on the accessibility of social networks from AbilityNet. The report analyzes Facebook, MySpace, YouTube, Yahoo and Bebo and reports that they all stink. Of those 5 sites, Yahoo was the only was to receive a two-star rating– that’s two starts out of five. The other four [...]]]></description>
			<content:encoded><![CDATA[<p>Via <a href="http://accessites.org/site/2008/01/social-networking-not-for-everyone/">Accesssites.org</a>, a summary of a 21 page report on <a href="http://www.abilitynet.org.uk/enation85">the accessibility of social networks</a> from AbilityNet. The report analyzes Facebook, MySpace, YouTube, Yahoo and Bebo and reports that they all stink. Of those 5 sites, Yahoo was the only was to receive a two-star rating– that’s two starts out of five. The other four all received one star indicating they are ‘very inaccessible’.</p>
<p>The <a href="http://dataportability.org/">Dataportability.org</a> group has been in the news of late as a number of major social networks have become involved. While their stated mission is not to make social networks accessible for users with disabilities, the goal that they are working towards should have that overall effect over time. They are working to promote the use of existing open standards to facilitate the sharing of social network user content outside of that network. Over time this will open the door to the creation of more accessible interfaces to access at least some of the data that is currently available only through proprietary, inaccessible systems.</p>
<p>Hopefully, the process of making user content more readily available will also lead to improvements in accessibility along the way. In the meantime, are users with disabilities being left out of the social networking revolution? Is anyone doing this right?</p>
]]></content:encoded>
			<wfw:commentRss>http://curbcut.net/accessibility/social-networking-accessibility/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Where to Discuss Accessibility– Forums, Mailing Lists and Blogs</title>
		<link>http://curbcut.net/accessibility/where-to-discuss-accessibility-forums-mailing-lists-and-blogs/</link>
		<comments>http://curbcut.net/accessibility/where-to-discuss-accessibility-forums-mailing-lists-and-blogs/#comments</comments>
		<pubDate>Wed, 12 Sep 2007 06:40:05 +0000</pubDate>
		<dc:creator>Christopher Phillips</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Community]]></category>

		<guid isPermaLink="false">http://curbcut.net/accessibility/where-to-discuss-accessibility-forums-mailing-lists-and-blogs/</guid>
		<description><![CDATA[Let’s say that you have a burning accessibility question that you are dying to ask someone and your roommate/spouse/pet are no help at all– where do you go? Here are a few good places to start: Accessify Forums from the good folks at Accessify. The forum has been around since August of 2003 and has [...]]]></description>
			<content:encoded><![CDATA[<p>Let’s say that you have a burning accessibility question that you are dying to ask someone and your roommate/spouse/pet are no help at all– where do you go? Here are a few good places to start:</p>
<ul>
<li><a href="http://www.accessifyforum.com/">Accessify Forums</a> from the <a href="http://www.accessify.com/about/">good folks at Accessify</a>. The forum has been around since August of 2003 and has over 6000 members and more than 50,000 posts. If your question hasn’t already been asked and answered, chances are there is someone hanging out over there who can answer it. The topics range from beginner to expert and runs on a <a href="http://www.accessifyforum.com/forum10/">modified version</a> of <a href="http://www.phpbb.com">phpBB</a>.</li>
<li><a href="http://www.webaim.org/discussion/">Web Accessibility E-mail Discussion List</a> from <a href="http://www.webaim.org">WebAIM</a>. The <a href="http://www.webaim.org/discussion/archives.php">list archives</a> show that the first posts showed up in November of 2003 and there have been hundreds of posts since then, with over <a href="http://www.webaim.org/search/?scope=archives&#038;q=pdf">1400 posts that include “pdf”</a> alone! If you are not a listserv person, you can also use their <a href="http://www.webaim.org/forums/">WebAIM Accessibility Forums</a> running on <a href="http://www.punbb.org/">PunBB</a>.<br />
(Update 9/13 The WebAIM List started in 1999)</li>
<li><a href="http://www.gawds.org/discuss/">The Guild of Accessible Web Developers</a> offers a few methods of communication, but they are primarily off-limits to anyone who is not a member. <acronym title="The Guild of Accessible Web Developers">GAWDS</acronym> has an IRC channel #gawds on irc.freenode.net as well as a forum and mailing list that are both for members only. I am not a member, so I don’t know how much any of these are used– anyone have more information on any of these resources?</li>
<li><a href="http://trace.wisc.edu:8080/mailman/listinfo/uaccess-l">The UACCESS-L listserv</a> from the <a href="http://trace.wisc.edu/">Trace Center</a> is perhaps more general as a “discussion of universal access to information systems” list with posts <a href="http://trace.wisc.edu:8080/mailarchive/uaccess-l/">in the archive</a> going back to December of 1998. They also have a <a href="http://trace.wisc.edu:8080/mailarchive/sec508/">separate Section 508 listserv</a>.</li>
<li><a href="http://www.w3.org/WAI/IG/Overview.html#Uselist">The Web Accessibility Initiative Interest Group (WAI IG) mailing list</a> may not be for everyone, but the archives there go back to April of 1997 with thousands of posts. The  <acronym title="Web Accessibility Initiative">WAI</acronym> also has <a href="http://www.w3.org/WAI/groups.html">a number of other groups</a>, including the <a href="http://www.w3.org/WAI/GL/participation.html"><acronym title="Web Content Accessibility Guidelines">WCAG</acronym> Working Group</a>.</li>
</ul>
<p>If none of those suit your fancy, there are a few other options. Some of the largest web developer communities have forums specifically for accessibility issues, such as <a href="http://www.webmasterworld.com/accessibility_usability/">the accessibility and usability forum</a> at the Webmaster World and the <a href="http://www.webdeveloper.com/forum/forumdisplay.php?s=8d090dda6c1b626ffaca75816702ca17&#038;f=30">accessibility forum</a> at Webdeveloper.com. Even if there isn’t a specific forum at your favorite web development form, people are likely still <a href="http://www.igrep.com/search.php?searchphrase=accessibility&#038;fds=on">talking about accessibility</a> (from Dev Shed).</p>
<p>Also, while you may not be able to initiate the discussion, there are always lots of great discussions happening at your <a href="http://www.webaim.org/blog/2007/05/14/blog-roundup/">favorite accessibility blog</a> (thanks Jared) or <a href="http://www.alistapart.com/topics/userscience/accessibility/">web magazine</a>.</p>
<p>If you are looking for a more specific category of accessibility, it may be out there somewhere as well.  For examples, check out the fairly active <a href="http://groups.yahoo.com/group/Captioning/">Yahoo! Group on Captioning</a> or the <a href="http://archives.java.sun.com/cgi-bin/wa?A0=java-access">Java Access listserv</a> from Sun Microsystems. Similarly, there are a number discussion lists and forums that are specific to a disability population, such as the <a href="http://listserv.uark.edu/scripts/wa.exe?A0=blind-l&#038;T=0">Computer Use by and for the Blind list</a></p>
<p>Lastly, don’t miss out on any local groups. There are a number of <a href="http://www.google.com/search?q=university+accessibility+mailing+list">university</a> and <a href="http://www.google.com/search?hl=en&#038;safe=off&#038;q=site%3A.gov+accessibility+listserv&#038;btnG=Search">government organizations</a> that provide venues to discuss accessibility issues with people in your own backyard– anyone from the <a href="http://tech.groups.yahoo.com/group/accessibleweb/">Phillipines</a>?</p>
<p>Where do you go to ask that burning accessibility question?</p>
]]></content:encoded>
			<wfw:commentRss>http://curbcut.net/accessibility/where-to-discuss-accessibility-forums-mailing-lists-and-blogs/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>
