<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" version="2.0">
<channel>
	<title>Comments for Nirak.net</title>
	
	<link>http://nirak.net</link>
	<description>Karin Dalziel</description>
	<lastBuildDate>Fri, 06 Nov 2009 14:16:55 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/CommentsNiraknet" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
		<title>Comment on The to do list – falling behind by Karin Dalziel</title>
		<link>http://nirak.net/2007/02/21/the-to-do-list-falling-behind/comment-page-1/#comment-128371</link>
		<dc:creator>Karin Dalziel</dc:creator>
		<pubDate>Fri, 06 Nov 2009 14:16:55 +0000</pubDate>
		<guid isPermaLink="false">http://nirak.net/testsite/?p=47#comment-128371</guid>
		<description>Hey, anonymous - I'm all done with school, no need for a.... what's a TUTORER?</description>
		<content:encoded><![CDATA[<p>Hey, anonymous &#8211; I&#8217;m all done with school, no need for a&#8230;. what&#8217;s a TUTORER?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The to do list – falling behind by Anonymous</title>
		<link>http://nirak.net/2007/02/21/the-to-do-list-falling-behind/comment-page-1/#comment-128337</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 06 Nov 2009 04:45:22 +0000</pubDate>
		<guid isPermaLink="false">http://nirak.net/testsite/?p=47#comment-128337</guid>
		<description>GET A TUTORER</description>
		<content:encoded><![CDATA[<p>GET A TUTORER</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility and Usability by Karin Dalziel</title>
		<link>http://nirak.net/2009/10/27/accessibility-and-usability/comment-page-1/#comment-128172</link>
		<dc:creator>Karin Dalziel</dc:creator>
		<pubDate>Tue, 03 Nov 2009 17:44:03 +0000</pubDate>
		<guid isPermaLink="false">http://nirak.net/?p=424#comment-128172</guid>
		<description>@Dr. Gunn Great Point! My talk was meant more for simpler websites, but data accessibility is important too. In addition to having an open API, I'm a proponent of putting your raw data (XML, databases, whatever) out there whenever possible.</description>
		<content:encoded><![CDATA[<p>@Dr. Gunn Great Point! My talk was meant more for simpler websites, but data accessibility is important too. In addition to having an open <acronym title="Application Programming Interface">API</acronym>, I&#8217;m a proponent of putting your raw data (<acronym title="eXtensible Markup Language">XML</acronym>, databases, whatever) out there whenever possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility and Usability by Dr. Gunn</title>
		<link>http://nirak.net/2009/10/27/accessibility-and-usability/comment-page-1/#comment-128171</link>
		<dc:creator>Dr. Gunn</dc:creator>
		<pubDate>Tue, 03 Nov 2009 17:32:13 +0000</pubDate>
		<guid isPermaLink="false">http://nirak.net/?p=424#comment-128171</guid>
		<description>Great article, Karin. One aspect of accessibility I think that's often overlooked is data accessibility.  It's important to make your website usable and accessible to everyone, but in this era of web services, it's also important to consider whether a user can get at the data any way they want, or can they only see the stuff you want to show them via the interface you provide.

Having an open API is a great way to build community. Given that 80+% of twitter usage is via third-party clients, it provides a great example of this.</description>
		<content:encoded><![CDATA[<p>Great article, Karin. One aspect of accessibility I think that&#8217;s often overlooked is data accessibility.  It&#8217;s important to make your website usable and accessible to everyone, but in this era of web services, it&#8217;s also important to consider whether a user can get at the data any way they want, or can they only see the stuff you want to show them via the interface you provide.</p>
<p>Having an open <acronym title="Application Programming Interface">API</acronym> is a great way to build community. Given that 80+% of twitter usage is via third-party clients, it provides a great example of this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why every Library Science student should learn programming by ade</title>
		<link>http://nirak.net/2008/12/12/why-every-library-science-student-should-learn-programming/comment-page-1/#comment-128127</link>
		<dc:creator>ade</dc:creator>
		<pubDate>Tue, 03 Nov 2009 08:06:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.nirak.net/?p=379#comment-128127</guid>
		<description>I definitely agree what John Fink has been said above. 
+-----------------
That said, I’m not sure that every librarian should be required to take a programming language. It should be an *option* in every library school, maybe coupled with some pleasant introductions to UNIX systems, but a requirement might be a bit extreme.
------------------------------+

It should be an optional for every students to study specific programming language. but for me, the very important thing is how to learn the algorithm/logical values so every students have the proper basis to learn programming, and imho what we called an operating system specifically on unix/like since its Free/Libre opensource software and famously known in the server/client environment. and the server/client knowledge is needed in the working environment.
Its happened in the library science curricula in Indonesia also. i thought that we're so leak in the ICT curricula and we learn it autodicactly from the community or books.

regards
ade from Jakarta, Indonesia</description>
		<content:encoded><![CDATA[<p>I definitely agree what John Fink has been said above.<br />
+&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br />
That said, I’m not sure that every librarian should be required to take a programming language. It should be an *option* in every library school, maybe coupled with some pleasant introductions to UNIX systems, but a requirement might be a bit extreme.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;+</p>
<p>It should be an optional for every students to study specific programming language. but for me, the very important thing is how to learn the algorithm/logical values so every students have the proper basis to learn programming, and imho what we called an operating system specifically on unix/like since its Free/Libre opensource software and famously known in the server/client environment. and the server/client knowledge is needed in the working environment.<br />
Its happened in the library science curricula in Indonesia also. i thought that we&#8217;re so leak in the ICT curricula and we learn it autodicactly from the community or books.</p>
<p>regards<br />
ade from Jakarta, Indonesia</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility and Usability – Part 3: Tools by Nirak.net » Accessibility and Usability</title>
		<link>http://nirak.net/2009/10/27/accessibility-and-usability-%e2%80%93-part-3-tools/comment-page-1/#comment-127528</link>
		<dc:creator>Nirak.net » Accessibility and Usability</dc:creator>
		<pubDate>Wed, 28 Oct 2009 02:13:43 +0000</pubDate>
		<guid isPermaLink="false">http://nirak.net/?p=446#comment-127528</guid>
		<description>[...] Part 3: Tools – A few tools you can use to help you do a mini accessibility study on your website, and some resources on doing more complete usability studies. [...]</description>
		<content:encoded><![CDATA[<p>[...] Part 3: Tools &#8211; A few tools you can use to help you do a mini accessibility study on your website, and some resources on doing more complete usability studies. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility and Usability – Part 2: Navigation and Design by Nirak.net » Accessibility and Usability – Part 3: Tools</title>
		<link>http://nirak.net/2009/10/27/accessibility-and-usability-%e2%80%93-part-2-design/comment-page-1/#comment-127527</link>
		<dc:creator>Nirak.net » Accessibility and Usability – Part 3: Tools</dc:creator>
		<pubDate>Wed, 28 Oct 2009 02:12:43 +0000</pubDate>
		<guid isPermaLink="false">http://nirak.net/?p=441#comment-127527</guid>
		<description>[...] that we have talked about Code and Navigation and Design, I’ll talk briefly about a few tools you can use to help you do a mini accessibility study on [...]</description>
		<content:encoded><![CDATA[<p>[...] that we have talked about Code and Navigation and Design, I&#8217;ll talk briefly about a few tools you can use to help you do a mini accessibility study on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility and Usability – Part 1: Code by Nirak.net » Accessibility and Usability – Part 3: Tools</title>
		<link>http://nirak.net/2009/10/27/accessibility-and-usability-part-1-code/comment-page-1/#comment-127526</link>
		<dc:creator>Nirak.net » Accessibility and Usability – Part 3: Tools</dc:creator>
		<pubDate>Wed, 28 Oct 2009 02:11:25 +0000</pubDate>
		<guid isPermaLink="false">http://nirak.net/?p=436#comment-127526</guid>
		<description>[...] that we have talked about Code and Navigation and Design, I’ll talk briefly about a few tools you can use to help you do a [...]</description>
		<content:encoded><![CDATA[<p>[...] that we have talked about Code and Navigation and Design, I&#8217;ll talk briefly about a few tools you can use to help you do a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility and Usability – Part 2: Navigation and Design by Bret Clement</title>
		<link>http://nirak.net/2009/10/27/accessibility-and-usability-%e2%80%93-part-2-design/comment-page-1/#comment-127501</link>
		<dc:creator>Bret Clement</dc:creator>
		<pubDate>Tue, 27 Oct 2009 21:39:45 +0000</pubDate>
		<guid isPermaLink="false">http://nirak.net/?p=441#comment-127501</guid>
		<description>Hi Karin, your presentation and these blogs are wonderfully thorough. 

As you point out, "trying to keep accessibility and usability in mind while designing a website is even harder."

Luckily, it's getting a bit easier, at least in terms of usability testing. Website Magazine did a nice review of some of the new online, low cost usability services that exist today (I work with UserTesting.com, but this article reviews a few of the good products on the market today): http://bit.ly/2RATxW.

Good luck on your presentation on Thursday!</description>
		<content:encoded><![CDATA[<p>Hi Karin, your presentation and these blogs are wonderfully thorough. </p>
<p>As you point out, &#8220;trying to keep accessibility and usability in mind while designing a website is even harder.&#8221;</p>
<p>Luckily, it&#8217;s getting a bit easier, at least in terms of usability testing. Website Magazine did a nice review of some of the new online, low cost usability services that exist today (I work with UserTesting.com, but this article reviews a few of the good products on the market today): <a href="http://bit.ly/2RATxW" rel="nofollow">http://bit.ly/2RATxW</a>.</p>
<p>Good luck on your presentation on Thursday!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Accessibility and Usability – Part 2: Navigation and Design by Nirak.net » Accessibility and Usability</title>
		<link>http://nirak.net/2009/10/27/accessibility-and-usability-%e2%80%93-part-2-design/comment-page-1/#comment-127497</link>
		<dc:creator>Nirak.net » Accessibility and Usability</dc:creator>
		<pubDate>Tue, 27 Oct 2009 21:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://nirak.net/?p=441#comment-127497</guid>
		<description>[...] Part 2: Design &amp; Navigation – Clear, concise navigation helps users that must use their keyboard to get around, and a clear, clean design helps users find your content with a minimum of fuss. [...]</description>
		<content:encoded><![CDATA[<p>[...] Part 2: Design &amp; Navigation &#8211; Clear, concise navigation helps users that must use their keyboard to get around, and a clear, clean design helps users find your content with a minimum of fuss. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
