<?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://adactio.com/journal/5208/"/>
	<rdf:li rdf:resource="http://mike.teczno.com/notes/screen-readers.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://adactio.com/journal/5208/">
    <title>Adactio: Journal—Image-y nation</title>
    <dc:date>2012-02-03T10:37:12+00:00</dc:date>
    <link>http://adactio.com/journal/5208/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["I remember when Ajax was getting popular, all the problems associated with frames rose from the grave: bookmarking, breaking the back button, etc. Now that we’re in a time of small-screen devices on low-bandwidth networks, we’re rediscovering a lot of the same issues we had when we were developing for 640 pixel wide screens with 28K or 56K modems." This is the thing.]]></description>
<dc:subject>web design doingitright performance jeremykeith</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:493dff28b541/</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:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:doingitright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:jeremykeith"/>
</rdf:Bag></taxo:topics>
</item>
<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>
</rdf:RDF>