<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (infovore)</title>
    <link>https://pinboard.in/u:infovore/public/</link>
    <description>recent bookmarks from infovore</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://mike.teczno.com/notes/screen-readers.html"/>
	<rdf:li rdf:resource="http://www.brainygamer.com/the_brainy_gamer/2008/08/is-this-what-we.html"/>
	<rdf:li rdf:resource="http://www.isolani.co.uk/blog/access/FallacyOfTooMuchAccessibility"/>
	<rdf:li rdf:resource="http://www.adaptivepath.com/ideas/essays/archives/000328.php"/>
	<rdf:li rdf:resource="http://www.sitepoint.com/blogs/2007/10/16/why-accessibility-because-its-our-job/"/>
	<rdf:li rdf:resource="http://www.cameronmoll.com/archives/000428.html"/>
	<rdf:li rdf:resource="http://www.456bereastreet.com/archive/200410/bring_on_the_tables/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://mike.teczno.com/notes/screen-readers.html">
    <title>we are all screen readers now (tecznotes)</title>
    <dc:date>2009-06-29T10:11:53+00:00</dc:date>
    <link>http://mike.teczno.com/notes/screen-readers.html</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["Fast-forward ten years, and I'm now using all those accessibility features on a daily basis. At some point during the dot-com bust it turned out that the written word was the payload, and regular people started using alternative (browsing) devices to access text from the web. Arguments about device-independent, semantic markup and graceful degradation suddenly have an additional halo of legitimacy because they affect everyone."
]]></description>
<dc:subject>text web reading mikemigurski words information accessibility content semanticmarkup doingitright</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:815f6a06bc67/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:reading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:mikemigurski"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:words"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:content"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:semanticmarkup"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:doingitright"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.brainygamer.com/the_brainy_gamer/2008/08/is-this-what-we.html">
    <title>The Brainy Gamer: Is this what we want?</title>
    <dc:date>2008-08-25T09:31:31+00:00</dc:date>
    <link>http://www.brainygamer.com/the_brainy_gamer/2008/08/is-this-what-we.html</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["It's a shame to me that a game with Braid's narrative, artistic, and aesthetic aspirations is inaccessible to so many people hungry for exactly those things." Yes. Much as I adore it, Braid can be awful hard at times. A smart game for smart gamers, alas.
]]></description>
<dc:subject>videogames play criticism art braid difficulty accessibility</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:ad3711ee8ae4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:videogames"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:play"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:criticism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:art"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:braid"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:difficulty"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.isolani.co.uk/blog/access/FallacyOfTooMuchAccessibility">
    <title>isolani - Web Accessibility: The fallacy of too much accessibility</title>
    <dc:date>2008-02-13T15:18:35+00:00</dc:date>
    <link>http://www.isolani.co.uk/blog/access/FallacyOfTooMuchAccessibility</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["There is no such thing as too much accessibility, and its ludicrous to suggest that too much accessibility actually reduces the accessibility of a site... What we are [actually] seeing is a non-understanding of web accessibility". Great article.
]]></description>
<dc:subject>web accessibility development design</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:37e7b83f0ad6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.adaptivepath.com/ideas/essays/archives/000328.php">
    <title>adaptive path » 90% of all usability testing is useless</title>
    <dc:date>2008-01-19T13:39:56+00:00</dc:date>
    <link>http://www.adaptivepath.com/ideas/essays/archives/000328.php</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["Instead, user research for the Web should delve into the qualitative aspects of design to understand how and why people respond to what has been created, and, more importantly, how to apply that insight to future work." Lane Becker on fine form.
]]></description>
<dc:subject>usability testing accessibility hci experiencedesign design users web</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:3cb0d72ecda8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:hci"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:experiencedesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:users"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:web"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.sitepoint.com/blogs/2007/10/16/why-accessibility-because-its-our-job/">
    <title>SitePoint Blogs » Why Accessibility? Because It’s Our Job!</title>
    <dc:date>2007-10-16T10:24:37+00:00</dc:date>
    <link>http://www.sitepoint.com/blogs/2007/10/16/why-accessibility-because-its-our-job/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["If we call ourselves professionals, we owe it to our clients, their clients, and ourselves, to do our job properly. A chef must care about health, a builder must care about safety, and we must care about accessibility."
]]></description>
<dc:subject>web accessibility html development</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:e65b4898be9a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cameronmoll.com/archives/000428.html">
    <title>Mobile Web Design: Methods to the Madness ~ Authentic Boredom</title>
    <dc:date>2007-04-20T09:59:43+00:00</dc:date>
    <link>http://www.cameronmoll.com/archives/000428.html</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["You’re considering retrofitting an existing website/web app to be more accessible to mobile users. What are your options?"
]]></description>
<dc:subject>mobile design accessibility usability markup web</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:bd9010da72d2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:markup"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:web"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.456bereastreet.com/archive/200410/bring_on_the_tables/">
    <title>Bring on the tables | 456 Berea Street</title>
    <dc:date>2005-01-03T22:08:45+00:00</dc:date>
    <link>http://www.456bereastreet.com/archive/200410/bring_on_the_tables/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[Great article on decent, accessible, standards-compliant tables
]]></description>
<dc:subject>webdev accessibility webdesign css</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:f00585e68dee/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:webdev"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:css"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>