<?xml version="1.0"?>
<rss version="2.0">
 <channel>
  <title>robertdot.org</title>
  <link>http://robertdot.org</link>
  <description>The Complete Robertdot Blog Feed.</description>
  <language>en-us</language>
  <lastBuildDate>Tue, 04 Mar 2008 20:03:11 GMT</lastBuildDate>
  <generator>Custom script based on LiveJournal RSS feed</generator>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2008/03/04/internet-explorer-version-targeting-finally-makes-sense.html</guid>
   <pubDate>Tue, 04 Mar 2008 20:03:11 GMT</pubDate>
   <title>Internet Explorer Version Targeting Finally Makes Sense</title>
   <link>http://robertdot.org/2008/03/04/internet-explorer-version-targeting-finally-makes-sense.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/geek.html" rel="tag">Geek</a>,  
     <a href="http://robertdot.org/tags/internet-explorer.html" rel="tag">Internet Explorer</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     I kept mum about Internet Explorer 8's version targeting to see how things played out.  It looks like Microsoft did the right thing for real web developers.
    </p>
    <p>
     Continue Reading &#34;Internet Explorer Version Targeting Finally Makes Sense&#34; on <a href="http://robertdot.org/2008/03/04/internet-explorer-version-targeting-finally-makes-sense.html">Robertdot</a> &hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2008/03/04/internet-explorer-version-targeting-finally-makes-sense.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2008/02/11/element-swapping-with-unobtrusive-javascript.html</guid>
   <pubDate>Mon, 11 Feb 2008 02:02:25 GMT</pubDate>
   <title>Element Swapping with Unobtrusive JavaScript</title>
   <link>http://robertdot.org/2008/02/11/element-swapping-with-unobtrusive-javascript.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/html.html" rel="tag">HTML</a>,  
     <a href="http://robertdot.org/tags/javascript.html" rel="tag">JavaScript</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     There may come a time when you need to show different content on one page based on a user-selected option.  Here's a quick tutorial.
    </p>
    <p>
     Continue Reading &#34;Element Swapping with Unobtrusive JavaScript&#34; on <a href="http://robertdot.org/2008/02/11/element-swapping-with-unobtrusive-javascript.html">Robertdot</a> &hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2008/02/11/element-swapping-with-unobtrusive-javascript.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2007/09/24/easier-image-replacement.html</guid>
   <pubDate>Mon, 24 Sep 2007 06:09:57 GMT</pubDate>
   <title>Easier Image Replacement</title>
   <link>http://robertdot.org/2007/09/24/easier-image-replacement.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/css.html" rel="tag">CSS</a>,  
     <a href="http://robertdot.org/tags/geek.html" rel="tag">Geek</a>,  
     <a href="http://robertdot.org/tags/html.html" rel="tag">HTML</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     If you didn't hear, text on a website is better than an image.  Images have their place, but many people use images where text should be.  In recent times, people have been using a technique called image replacement to replace text with an image.  Typically, there are crazy hacks that involve embedded elements, but there is an easier way.
    </p>
    <p>
     Continue Reading &#34;Easier Image Replacement&#34; on <a href="http://robertdot.org/2007/09/24/easier-image-replacement.html">Robertdot</a> or <a href="http://robertdot.livejournal.com/12402.html" rel="nofollow">LiveJournal</a>&hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2007/09/24/easier-image-replacement.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2007/09/21/who-the-hell-is-domain-design-shop.html</guid>
   <pubDate>Fri, 21 Sep 2007 17:09:24 GMT</pubDate>
   <title>Who the Hell is Domain Design Shop?</title>
   <link>http://robertdot.org/2007/09/21/who-the-hell-is-domain-design-shop.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/geek.html" rel="tag">Geek</a>,  
     <a href="http://robertdot.org/tags/spam.html" rel="tag">Spam</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     I ordered a couple domains from GoDaddy a few days ago.  I wasn't really surprised when I found an e-mail with the subject <q>Important information about your domain.</q>  I was surprised at what was inside.
    </p>
    <p>
     Continue Reading &#34;Who the Hell is Domain Design Shop?&#34; on <a href="http://robertdot.org/2007/09/21/who-the-hell-is-domain-design-shop.html">Robertdot</a> or <a href="http://robertdot.livejournal.com/12156.html" rel="nofollow">LiveJournal</a>&hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2007/09/21/who-the-hell-is-domain-design-shop.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2007/09/14/ipod-touch-pushing-the-mobile-web.html</guid>
   <pubDate>Fri, 14 Sep 2007 17:09:20 GMT</pubDate>
   <title>iPod Touch Pushing the Mobile Web</title>
   <link>http://robertdot.org/2007/09/14/ipod-touch-pushing-the-mobile-web.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/apple.html" rel="tag">Apple</a>,  
     <a href="http://robertdot.org/tags/hardware.html" rel="tag">Hardware</a>,  
     <a href="http://robertdot.org/tags/html.html" rel="tag">HTML</a>,  
     <a href="http://robertdot.org/tags/iphone.html" rel="tag">iPhone</a>,  
     <a href="http://robertdot.org/tags/ipod.html" rel="tag">iPod</a>,  
     <a href="http://robertdot.org/tags/phones.html" rel="tag">Phones</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a>,  
     <a href="http://robertdot.org/tags/webkit.html" rel="tag">WebKit</a> 
    </p>
    <p>
     As most know, Apple released a new line up of iPods, and possibly a major improvement for the mobile web.
    </p>
    <p>
     Continue Reading &#34;iPod Touch Pushing the Mobile Web&#34; on <a href="http://robertdot.org/2007/09/14/ipod-touch-pushing-the-mobile-web.html">Robertdot</a>,  <a href="http://robertdot.livejournal.com/11657.html" rel="nofollow">LiveJournal</a>, or <a href="http://blog.myspace.com/index.cfm?fuseaction=blog.view&amp;friendID=18355253&amp;blogID=309919782" rel="nofollow">MySpace</a>&hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2007/09/14/ipod-touch-pushing-the-mobile-web.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2007/04/24/easy-clearing-of-floats.html</guid>
   <pubDate>Tue, 24 Apr 2007 22:04:29 GMT</pubDate>
   <title>Easy Clearing Of Floats</title>
   <link>http://robertdot.org/2007/04/24/easy-clearing-of-floats.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/css.html" rel="tag">CSS</a>,  
     <a href="http://robertdot.org/tags/html.html" rel="tag">HTML</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     Web standards designers often need to make use of <code>display:float</code> to handle things like columns, navigation lists, and more.  Usually these floats are followed by something like <code>&lt;div style="clear:both"&gt;&lt;/div&gt;</code>.  It turns out there is an easier way.
    </p>
    <p>
     Continue Reading &#34;Easy Clearing Of Floats&#34; on <a href="http://robertdot.org/2007/04/24/easy-clearing-of-floats.html">Robertdot</a> or <a href="http://robertdot.livejournal.com/10633.html" rel="nofollow">LiveJournal</a>&hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2007/04/24/easy-clearing-of-floats.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2007/03/08/html-5-whatwg-versus-w3c.html</guid>
   <pubDate>Thu, 08 Mar 2007 18:03:20 GMT</pubDate>
   <title>HTML 5: WHATWG versus W3C</title>
   <link>http://robertdot.org/2007/03/08/html-5-whatwg-versus-w3c.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/geek.html" rel="tag">Geek</a>,  
     <a href="http://robertdot.org/tags/html.html" rel="tag">HTML</a>,  
     <a href="http://robertdot.org/tags/w3c.html" rel="tag">W3C</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a>,  
     <a href="http://robertdot.org/tags/whatwg.html" rel="tag">WHATWG</a> 
    </p>
    <p>
     The new <acronym title="World Wide Web Consortium">W3C</acronym> <acronym title="HyperText Markup Language">HTML</acronym> working group launched.  The charter states that they'll attempt convergence with the <acronym title="Web Hypertext Application Technology Working Group">WHATWG</acronym>'s recommendation.  I remain a little confused with how the browser vendors will handle this.
    </p>
    <p>
     Continue Reading &#34;HTML 5: WHATWG versus W3C&#34; on <a href="http://robertdot.org/2007/03/08/html-5-whatwg-versus-w3c.html">Robertdot</a>,  <a href="http://robertdot.livejournal.com/9699.html" rel="nofollow">LiveJournal</a>, or <a href="http://blog.myspace.com/index.cfm?fuseaction=blog.view&amp;friendID=18355253&amp;blogID=238747854" rel="nofollow">MySpace</a>&hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2007/03/08/html-5-whatwg-versus-w3c.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2007/01/12/how-to-do-modern-web-design.html</guid>
   <pubDate>Fri, 12 Jan 2007 00:01:37 GMT</pubDate>
   <title>How To Do Modern Web Design</title>
   <link>http://robertdot.org/2007/01/12/how-to-do-modern-web-design.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/accessibility.html" rel="tag">Accessibility</a>,  
     <a href="http://robertdot.org/tags/css.html" rel="tag">CSS</a>,  
     <a href="http://robertdot.org/tags/geek.html" rel="tag">Geek</a>,  
     <a href="http://robertdot.org/tags/html.html" rel="tag">HTML</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     I've been trying to figure out the best way to explain how to do modern, semantic, standards compliant web design.  I've been trying to make the point to my current protege that one should first look at a website like a term paper and move on from there.  I've formulated a method now that I'd like to outline.
    </p>
    <p>
     Continue Reading &#34;How To Do Modern Web Design&#34; on <a href="http://robertdot.org/2007/01/12/how-to-do-modern-web-design.html">Robertdot</a>,  <a href="http://robertdot.livejournal.com/8886.html" rel="nofollow">LiveJournal</a>, or <a href="http://blog.myspace.com/index.cfm?fuseaction=blog.view&amp;friendID=18355253&amp;blogID=216326046" rel="nofollow">MySpace</a>&hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2007/01/12/how-to-do-modern-web-design.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2006/12/29/markup-not-safe-for-work-content.html</guid>
   <pubDate>Fri, 29 Dec 2006 17:12:53 GMT</pubDate>
   <title>Markup Not Safe For Work Content</title>
   <link>http://robertdot.org/2006/12/29/markup-not-safe-for-work-content.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/geek.html" rel="tag">Geek</a>,  
     <a href="http://robertdot.org/tags/html.html" rel="tag">HTML</a>,  
     <a href="http://robertdot.org/tags/microformats.html" rel="tag">Microformats</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     Some guy named PJ Doland <a href="http://pj.doland.org/archives/041571.php">suggested</a> we use <code>rel="NSFW"</code> to markup content that is <acronym title="Not Safe For Work">NSFW</acronym>.
    </p>
    <p>
     Continue Reading &#34;Markup Not Safe For Work Content&#34; on <a href="http://robertdot.org/2006/12/29/markup-not-safe-for-work-content.html">Robertdot</a> &hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2006/12/29/markup-not-safe-for-work-content.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2006/11/19/the-great-acronym-title-multipurpose-internet-mail-extensions-mime-acronym-type-swindle.html</guid>
   <pubDate>Sun, 19 Nov 2006 21:11:51 GMT</pubDate>
   <title>The Great <acronym title="Multipurpose Internet Mail Extensions">MIME</acronym>-Type Swindle</title>
   <link>http://robertdot.org/2006/11/19/the-great-acronym-title-multipurpose-internet-mail-extensions-mime-acronym-type-swindle.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/geek.html" rel="tag">Geek</a>,  
     <a href="http://robertdot.org/tags/html.html" rel="tag">HTML</a>,  
     <a href="http://robertdot.org/tags/w3c.html" rel="tag">W3C</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a>,  
     <a href="http://robertdot.org/tags/xhtml.html" rel="tag">XHTML</a> 
    </p>
    <p>
     It's a really old subject, but I haven't said my piece on the <acronym title="Extensible HyperText Markup Language">XHTML</acronym> 1.0 versus <acronym title="HyperText Markup Language">HTML</acronym> 4.01 debate.  While commenting on Roger Johansson's blog, 456 Berea Street, I said a little bit about what I think.  I figured I ought to go ahead and say my fill.
    </p>
    <p>
     Continue Reading &#34;The Great <acronym title="Multipurpose Internet Mail Extensions">MIME</acronym>-Type Swindle&#34; on <a href="http://robertdot.org/2006/11/19/the-great-acronym-title-multipurpose-internet-mail-extensions-mime-acronym-type-swindle.html">Robertdot</a>,  <a href="http://robertdot.livejournal.com/7489.html" rel="nofollow">LiveJournal</a>, or <a href="http://blog.myspace.com/index.cfm?fuseaction=blog.view&amp;friendID=18355253&amp;blogID=195182391" rel="nofollow">MySpace</a>&hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2006/11/19/the-great-acronym-title-multipurpose-internet-mail-extensions-mime-acronym-type-swindle.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2006/10/28/w3c-listens-incremental-update-to-html-on-the-way.html</guid>
   <pubDate>Sat, 28 Oct 2006 19:10:31 GMT</pubDate>
   <title>W3C Listens, Incremental Update to HTML On The Way</title>
   <link>http://robertdot.org/2006/10/28/w3c-listens-incremental-update-to-html-on-the-way.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/geek.html" rel="tag">Geek</a>,  
     <a href="http://robertdot.org/tags/html.html" rel="tag">HTML</a>,  
     <a href="http://robertdot.org/tags/w3c.html" rel="tag">W3C</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     Surprisingly, SlashDot scooped all the web design websites I normally read on Tim Berners-Lee's announcement that <acronym title="HyperText Markup Language">HTML</acronym> will be incrementally updated (as well as things such as the <acronym title="World Wide Web Consortium">W3C</acronym>'s HTML validator)
    </p>
    <p>
     Continue Reading &#34;W3C Listens, Incremental Update to HTML On The Way&#34; on <a href="http://robertdot.org/2006/10/28/w3c-listens-incremental-update-to-html-on-the-way.html">Robertdot</a>,  <a href="http://robertdot.livejournal.com/6012.html" rel="nofollow">LiveJournal</a>, or <a href="http://blog.myspace.com/index.cfm?fuseaction=blog.view&amp;friendID=18355253&amp;blogID=185995123" rel="nofollow">MySpace</a>&hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2006/10/28/w3c-listens-incremental-update-to-html-on-the-way.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2006/10/20/stand-up-for-your-rights-but-sit-down-and-listen-too.html</guid>
   <pubDate>Fri, 20 Oct 2006 20:10:37 GMT</pubDate>
   <title>Stand Up For Your Rights, But Sit Down And Listen, Too!</title>
   <link>http://robertdot.org/2006/10/20/stand-up-for-your-rights-but-sit-down-and-listen-too.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/geek.html" rel="tag">Geek</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     Eric Meyer wrote a piece on Vitamin called <cite>Stand Up For Your Rights!</cite>.  I totally misread it the first time, but it gave me a few ideas.  I have mentored a few people in web design.  Meyer's article made me think a bit harder about how I usually mentor people, and made me realize one good idea for mentoring.
    </p>
    <p>
     Continue Reading &#34;Stand Up For Your Rights, But Sit Down And Listen, Too!&#34; on <a href="http://robertdot.org/2006/10/20/stand-up-for-your-rights-but-sit-down-and-listen-too.html">Robertdot</a> &hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2006/10/20/stand-up-for-your-rights-but-sit-down-and-listen-too.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2006/09/20/web-standards-still-matter.html</guid>
   <pubDate>Wed, 20 Sep 2006 20:09:41 GMT</pubDate>
   <title>Web Standards Still Matter</title>
   <link>http://robertdot.org/2006/09/20/web-standards-still-matter.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/geek.html" rel="tag">Geek</a>,  
     <a href="http://robertdot.org/tags/podcasting.html" rel="tag">Podcasting</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     I want to do a podcast.  If you are on my site and you look at the navigation bar, you'll see a heading for it.  I just haven't had the time yet, and I've been questioning my original intent.  Now, I don't question it as much.
    </p>
    <p>
     Continue Reading &#34;Web Standards Still Matter&#34; on <a href="http://robertdot.org/2006/09/20/web-standards-still-matter.html">Robertdot</a>,  <a href="http://robertdot.livejournal.com/4350.html" rel="nofollow">LiveJournal</a>, or <a href="http://blog.myspace.com/index.cfm?fuseaction=blog.view&amp;friendID=18355253&amp;blogID=170367821" rel="nofollow">MySpace</a>&hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2006/09/20/web-standards-still-matter.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2006/01/28/near-misses-ajax-and-accessibility.html</guid>
   <pubDate>Sat, 28 Jan 2006 01:01:44 GMT</pubDate>
   <title>Near Misses, AJAX, And Accessibility</title>
   <link>http://robertdot.org/2006/01/28/near-misses-ajax-and-accessibility.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/accessibility.html" rel="tag">Accessibility</a>,  
     <a href="http://robertdot.org/tags/ajax.html" rel="tag">Ajax</a>,  
     <a href="http://robertdot.org/tags/geek.html" rel="tag">Geek</a>,  
     <a href="http://robertdot.org/tags/javascript.html" rel="tag">JavaScript</a>,  
     <a href="http://robertdot.org/tags/personal.html" rel="tag">Personal</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     There is nothing like starting my day by looking over my shoulder to see a green Jeep (1990-1996), tires squealing, sliding towards me. My natural reflexes propelled my body quickly to the other corner despite my brain knowing that the Jeep would come to a stop well before it collided with me. The guy in the Jeep wasn't so sure. I just kept walking. It wasn't the first time I'd almost gotten hit, and it wasn't the closest. It was the loudest. I looked back after I had walked twenty or thirty feet and couldn't tell if the guy in the Jeep was pissed or shaken. He was still sitting there. That means something.
    </p>
    <p>
     Continue Reading &#34;Near Misses, AJAX, And Accessibility&#34; on <a href="http://robertdot.org/2006/01/28/near-misses-ajax-and-accessibility.html">Robertdot</a> &hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2006/01/28/near-misses-ajax-and-accessibility.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2005/03/22/some-notes-on-web-accessibility.html</guid>
   <pubDate>Tue, 22 Mar 2005 04:03:52 GMT</pubDate>
   <title>Some Notes On Web Accessibility</title>
   <link>http://robertdot.org/2005/03/22/some-notes-on-web-accessibility.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/accessibility.html" rel="tag">Accessibility</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     Every once in awhile, my mind circles back to accessibility. The first time I approached Web accessibility was back in '00. It was the summer after my Freshman year. Mike at Trussville Utilities asked me to research web accessibility and make a version of their website for the disabled. At the time, <a href="http://www.w3.org/TR/WAI-WEBCONTENT/">Web Content Accessibility Guidelines 1.0</a> was relatively new. The WACG was pretty rudimentary because the web was still quite immature in some areas due to its (relative) youth and hadn't exactly gotten around to accessibility controls. At the time, it was enough that one use alt text with images, use explanatory text for video and sounds, be careful with tables, use CSS, etc. Today, things are quite a bit different.
    </p>
    <p>
     Continue Reading &#34;Some Notes On Web Accessibility&#34; on <a href="http://robertdot.org/2005/03/22/some-notes-on-web-accessibility.html">Robertdot</a> &hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2005/03/22/some-notes-on-web-accessibility.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2005/01/07/clients-and-the-html-dom.html</guid>
   <pubDate>Fri, 07 Jan 2005 00:01:27 GMT</pubDate>
   <title>Clients And The HTML DOM</title>
   <link>http://robertdot.org/2005/01/07/clients-and-the-html-dom.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/dom.html" rel="tag">DOM</a>,  
     <a href="http://robertdot.org/tags/javascript.html" rel="tag">JavaScript</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a>,  
     <a href="http://robertdot.org/tags/work.html" rel="tag">Work</a> 
    </p>
    <p>
     There are two sides to working for clients: the bad side and the good side.
    </p>
    <p>
     Continue Reading &#34;Clients And The HTML DOM&#34; on <a href="http://robertdot.org/2005/01/07/clients-and-the-html-dom.html">Robertdot</a> &hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2005/01/07/clients-and-the-html-dom.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2004/05/27/the-caption.html</guid>
   <pubDate>Thu, 27 May 2004 19:05:48 GMT</pubDate>
   <title>The Caption</title>
   <link>http://robertdot.org/2004/05/27/the-caption.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/reflect.html" rel="tag">Reflect</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     <em>Most of you will probably not be interested in the following post, as it is pure CSS geekiness. In fact, I don't even want to proofread it because I don't want to think about it again.</em>
    </p>
    <p>
     Continue Reading &#34;The Caption&#34; on <a href="http://robertdot.org/2004/05/27/the-caption.html">Robertdot</a> &hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2004/05/27/the-caption.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2004/03/18/flash-anyone.html</guid>
   <pubDate>Thu, 18 Mar 2004 19:03:04 GMT</pubDate>
   <title>Flash, anyone?</title>
   <link>http://robertdot.org/2004/03/18/flash-anyone.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/flash.html" rel="tag">Flash</a>,  
     <a href="http://robertdot.org/tags/loveorderlight.html" rel="tag">Love Order Light</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     Many sites are operating with Flash only designs. I started thinking about a flash only site, but then I started wondering about the implications. 
    </p>
    <p>
     Continue Reading &#34;Flash, anyone?&#34; on <a href="http://robertdot.org/2004/03/18/flash-anyone.html">Robertdot</a> &hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2004/03/18/flash-anyone.html</comments>
  </item>
  <item>
   <guid isPermaLink='true'>http://robertdot.org/2004/02/20/css-and-span-width.html</guid>
   <pubDate>Fri, 20 Feb 2004 17:02:36 GMT</pubDate>
   <title>CSS and SPAN width</title>
   <link>http://robertdot.org/2004/02/20/css-and-span-width.html</link>
   <author>Robert &lt;rss@robertdot.org&gt;</author>
   <description><![CDATA[
    <p>
     Tags:
     <a href="http://robertdot.org/tags/css.html" rel="tag">CSS</a>,  
     <a href="http://robertdot.org/tags/loveorderlight.html" rel="tag">Love Order Light</a>,  
     <a href="http://robertdot.org/tags/web-design.html" rel="tag">Web Design</a>,  
     <a href="http://robertdot.org/tags/web-standards.html" rel="tag">Web Standards</a> 
    </p>
    <p>
     Apparently, the SPAN, an inline element in [x]HTML, has no width attribute. That is, the spec has no place for assigning width to inline elements, therefore SPAN's have no width. There is a &quot;bug&quot; or something that allows Gecko/Mozilla to do width if float is set to left. However, it ends up being an ugly hack. Now, it's safe to say that Microsoft didn't comply. I can tell a SPAN to have a width in IE and it gives the SPAN that width (if I don't specify a DTD). Apparently, this &quot;bug&quot; is a fowled implementation of the inline-block, which allows for inline rendering (e.g. no line breaks after) with block formatting. So, for CSS 2.1, Microsoft is a step ahead... sort of.
    </p>
    <p>
     Continue Reading &#34;CSS and SPAN width&#34; on <a href="http://robertdot.org/2004/02/20/css-and-span-width.html">Robertdot</a> &hellip;
    </p>
    ]]></description>
   <comments>http://robertdot.org/2004/02/20/css-and-span-width.html</comments>
  </item>
 </channel>
</rss>