<?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:series="http://unfoldingneurons.com/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>AuctioneerTech &#187; web standards</title>
	<atom:link href="http://www.auctioneertech.com/tag/web-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.auctioneertech.com</link>
	<description>Technology, auctions and auctioneers - auction tech for the auction industry</description>
	<lastBuildDate>Mon, 19 Jul 2010 14:43:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<!-- podcast_generator="podPress/8.8" - maintenance_release="8.8.5.1" -->
	<copyright>2008 </copyright>
	<managingEditor>aaron@auctioneertech.com (AuctioneerTech)</managingEditor>
	<webMaster>aaron@auctioneertech.com (AuctioneerTech)</webMaster>
	<category>posts</category>
	<ttl>1440</ttl>
	<image>
		<url>http://www.auctioneertech.com/wp-content/uploads/AuctioneerTech_Auction_Podcast_small.jpg</url>
		<title>AuctioneerTech &#187; web standards</title>
		<link>http://www.auctioneertech.com</link>
		<width>144</width>
		<height>144</height>
	</image>
	<itunes:subtitle>Technology, auctions and auctioneers - auction tech for the auction industry</itunes:subtitle>
	<itunes:summary>Technology, auctions and auctioneers - auction tech for the auction industry</itunes:summary>
	<itunes:keywords>auction podcast, auction tech, auction industry, auctions, auctioneer, auctioneers</itunes:keywords>
	<itunes:category text="Technology" />
	<itunes:category text="Business" />
	<itunes:category text="Education" />
	<itunes:author>AuctioneerTech</itunes:author>
	<itunes:owner>
		<itunes:name>AuctioneerTech</itunes:name>
		<itunes:email>aaron@auctioneertech.com</itunes:email>
	</itunes:owner>
	<itunes:block>no</itunes:block>
	<itunes:explicit>no</itunes:explicit>
	<itunes:image href="http://www.auctioneertech.com/wp-content/uploads/AuctioneerTech_Auction_Podcast.jpg" />
		<item>
		<title>Amazon fail</title>
		<link>http://www.auctioneertech.com/2009/amazon-fail/</link>
		<comments>http://www.auctioneertech.com/2009/amazon-fail/#comments</comments>
		<pubDate>Tue, 29 Sep 2009 14:26:08 +0000</pubDate>
		<dc:creator>Aaron Traffas, CAI, ATS, CES</dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[theory]]></category>
		<category><![CDATA[websites]]></category>
		<category><![CDATA[Browsers]]></category>
		<category><![CDATA[Jeffrey Zeldman]]></category>
		<category><![CDATA[Web browser]]></category>
		<category><![CDATA[Web design]]></category>
		<category><![CDATA[web standards]]></category>

		<guid isPermaLink="false">http://www.auctioneertech.com/?p=1534</guid>
		<description><![CDATA[			
				
			
		
Recent website design work has caused us to do some research into the current design techniques and trends among website authors regarding web stanards. We looked into the definitive guide on the subject, Jeffrey Zeldman&#8216;s Designing with Web Standards, and were excited to find that a third edition is coming this year. While imagining how [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: left; margin-right: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.auctioneertech.com%2F2009%2Famazon-fail%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.auctioneertech.com%2F2009%2Famazon-fail%2F&amp;source=traffas&amp;style=compact" height="61" width="50" /><br />
			</a>
		</div>
<div id="attachment_1533" class="wp-caption alignright" style="width: 317px"><img class="size-full wp-image-1533" title="Web standards fail" src="http://www.auctioneertech.com/wp-content/uploads/2009/10/Screenshot-3.png" alt="Web standards fail" width="307" height="346" /><p class="wp-caption-text">Web standards fail</p></div>
<p>Recent website design work has caused us to do some research into the current design techniques and trends among website authors regarding web stanards. We looked into the definitive guide on the subject, <a href="http://www.zeldman.com/">Jeffrey Zeldman</a>&#8216;s <a href="http://www.zeldman.com/dwws/">Designing with Web Standards</a>, and were excited to find that a third edition is coming this year. While imagining how it would soon sit on the shelf next to the well-read first and second editions, we saw that <a class="zem_slink" title="Amazon" rel="homepage" href="http://amazon.com/">Amazon</a> had a graphic inviting us to preview part of the book. <em>Click to LOOK INSIDE!</em> it invited.</p>
<p>Shown to the right is the result of clicking to look inside. It shows what happens when you try to deliver content in something other than an open and, dare we say, web-standard method.</p>
<p><code>Your web browser does not support this feature. Please visit our <a href="http://www.auctioneertech.com/the-end-of-the-faq/">Frequently Asked Questions</a> for a list of compatible web browsers that support the Amazon Online Reader.</code></p>
<p>It&#8217;ll be a great book. For those curious readers who don&#8217;t have one of the previous editions, they&#8217;ll have to use a compatible browser to view the preview. It&#8217;s too bad that Amazon can&#8217;t figure out how to deliver content to everyone. Perhaps their designers might do well to actually read some of the books they&#8217;re selling.</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=ad33dfdc-dd4e-4956-a6aa-39b094beb729" alt="" /></div>
]]></content:encoded>
			<wfw:commentRss>http://www.auctioneertech.com/2009/amazon-fail/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Click here, don&#8217;t break the back button</title>
		<link>http://www.auctioneertech.com/2009/click-here-dont-break-the-back-button/</link>
		<comments>http://www.auctioneertech.com/2009/click-here-dont-break-the-back-button/#comments</comments>
		<pubDate>Mon, 23 Mar 2009 05:01:54 +0000</pubDate>
		<dc:creator>Aaron Traffas, CAI, ATS, CES</dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[websites]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[web standards]]></category>

		<guid isPermaLink="false">http://www.auctioneertech.com/?p=835</guid>
		<description><![CDATA[			
				
			
		
Veronica Belmont, geek goddess and co-host of the technology video podcast Tekzilla, started a new website called the Vintage Web. Listed on the site are examples of websites from days gone by, when designers were so excited to use the newest features offered by technologies like DHTML and JavaScript that they weren&#8217;t concerned with the [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: left; margin-right: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.auctioneertech.com%2F2009%2Fclick-here-dont-break-the-back-button%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.auctioneertech.com%2F2009%2Fclick-here-dont-break-the-back-button%2F&amp;source=traffas&amp;style=compact" height="61" width="50" /><br />
			</a>
		</div>
<p><a href="http://www.veronicabelmont.com/">Veronica Belmont</a>, <a href="http://thebestwho.com/2008/04/10/morgan-webb-versus-veronica-belmont-battle-of-the-geek-goddesses/">geek goddess</a> and co-host of the technology video podcast <a href="http://revision3.com/tekzilla/">Tekzilla</a>, started a new website called the <a href="http://www.thevintageweb.com/">Vintage Web</a>. Listed on the site are examples of websites from days gone by, when designers were so excited to use the newest features offered by technologies like <a class="zem_slink" title="Dynamic HTML" rel="wikipedia" href="http://en.wikipedia.org/wiki/Dynamic_HTML">DHTML</a> and <a class="zem_slink" title="JavaScript" rel="wikipedia" href="http://en.wikipedia.org/wiki/JavaScript">JavaScript</a> that they weren&#8217;t concerned with the implications these techniques had on accessibility and usability.</p>
<p>One of the <em>faux pas</em> that plagued these old sites – and unfortunately many current sites on the web – is the use of improper <a class="zem_slink" title="Anchor text" rel="wikipedia" href="http://en.wikipedia.org/wiki/Anchor_text">anchor text</a>. Anchors are the links that are fundamental to HTML. HTML stands for <a class="zem_slink" title="HTML" rel="wikipedia" href="http://en.wikipedia.org/wiki/HTML">Hyper-Text Markup Language</a> and text that is linked to another page is a hyperlink. While the nomenclature has gone away for the most part, the concept is still fundamental to the workings of the modern web. Unfortunately, one of the bad practices regarding the creation of <a class="zem_slink" title="Hyperlink" rel="wikipedia" href="http://en.wikipedia.org/wiki/Hyperlink">hyperlinks</a> still remains.</p>
<p><span class="pullquote">The goal of a designer should be to link the words that describe the destination of the link. Think of this goal as linking the nouns and not the verbs.</span> For example, if you&#8217;re linking to the AuctioneerTech website, the link should be as follows.</p>
<blockquote><p>Visit <a href="http://www.auctioneertech.com">AuctioneerTech</a> for information about auctions and technology.</p></blockquote>
<p>Unfortunately, we still see some designers electing to link verbs or, worse, adding extra and unnecessary text to create a hyperlink out of nothing as in the following examples.</p>
<blockquote><p><a href="http://www.auctioneertech.com">Visit</a> AuctioneerTech for information about auctions and technology.</p></blockquote>
<blockquote><p>To get information about auctions and technology from AuctioneerTech, <a href="http://www.auctioneertech.com">click here</a>.</p></blockquote>
<p>Both of these examples are wrong. While there is little debate that they are more confusing and not congruent with the workings of the modern web, there is no debate that they are absolutely worse for search engines which must now try to ascertain from the surrounding text the meaning of the link rather than having the contents of the linked text to use in making the association between the target and the target&#8217;s description. Read more from the W3C regarding <a href="http://www.w3.org/QA/Tips/noClickHere">proper link creation</a>.</p>
<p>Another common mistake designers make when constructing links is making the links open in a new window or tab. This practice sometimes comes at the behest of the boss, be it the owner or CEO or marketing department, who mistakenly believes that if the links are opened in a new window that it keeps the user on the site.</p>
<p>The modern web makes use of the back button. <span class="pullquote">Navigational history is a fundamental component to browsing, and users know it.</span> When a user follows a link and wants to return to the page from whence he came, he simply clicks the back button or, now more frequently, clicks the back button now included on many mice.</p>
<p>When links are set to open new windows or tabs, this back button functionality is broken, confusing the user and often causing him to close the browser and start anew. Other reasons to never launch new windows with links include problems with pop-up blockers and the fact that modern <a class="zem_slink" title="Web standards" rel="wikipedia" href="http://en.wikipedia.org/wiki/Web_standards">web standards</a> have actually prohibited the target=”_parent” function that allowed this bad practice in the first place. The only way to launch new windows without breaking modern web standards is to use JavaScript, which is a security risk that more and more users are electing to not enable in their browsers, which means that the links won&#8217;t work at all for them, confusing them even more. Read more about the importance of <a href="http://www.smashingmagazine.com/2008/07/01/should-links-open-in-new-windows/">avoiding opening links in new windows</a> from Smashing Magazine.</p>
<p>Don&#8217;t make it hard for users to come back to your site by opening links in new windows. Remember to link the target names when you&#8217;re building links and never, ever use “click here” as the content of a link. With your help, we can all make the web a better place.</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif" alt="" /><span class="zem-script more-related"><script src="http://static.zemanta.com/readside/loader.js" type="text/javascript"></script></span></div>
]]></content:encoded>
			<wfw:commentRss>http://www.auctioneertech.com/2009/click-here-dont-break-the-back-button/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>PDF should be optional on web</title>
		<link>http://www.auctioneertech.com/2008/pdf-should-be-optional-on-web/</link>
		<comments>http://www.auctioneertech.com/2008/pdf-should-be-optional-on-web/#comments</comments>
		<pubDate>Sat, 20 Sep 2008 14:09:59 +0000</pubDate>
		<dc:creator>Aaron Traffas, CAI, ATS, CES</dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[Acrobat]]></category>
		<category><![CDATA[Adobe]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[PDF]]></category>
		<category><![CDATA[plug-in]]></category>
		<category><![CDATA[Reader]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[web standards]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://www.auctioneertech.com/?p=146</guid>
		<description><![CDATA[			
				
			
		


Portable Document Format (PDF) is a file format created by Adobe in 1993. As of July 1, 2008, it&#8217;s an ISO standard, which means that the format is open and published so that anyone can create it or use it.
There are many misconceptions about the proper use of PDFs, and today I&#8217;m going to try [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: left; margin-right: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.auctioneertech.com%2F2008%2Fpdf-should-be-optional-on-web%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.auctioneertech.com%2F2008%2Fpdf-should-be-optional-on-web%2F&amp;source=traffas&amp;style=compact" height="61" width="50" /><br />
			</a>
		</div>
<div class="zemanta-img zemanta-action-click">
<div class="wp-caption alignright" style="width: 212px"><a href="http://en.wikipedia.org/wiki/Image:PDF.png"><img title="Latest PDF File Icon" src="http://upload.wikimedia.org/wikipedia/en/thumb/a/a6/PDF.png/202px-PDF.png" alt="Latest PDF File Icon" width="202" height="202" /></a><p class="wp-caption-text">Image via Wikipedia</p></div>
</div>
<p><a class="zem_slink" title="Portable Document Format" rel="wikipedia" href="http://en.wikipedia.org/wiki/Portable_Document_Format">Portable Document Format</a> (PDF) is a <a class="zem_slink" title="File format" rel="wikipedia" href="http://en.wikipedia.org/wiki/File_format">file format</a> created by <a class="zem_slink" title="Adobe Systems" rel="homepage" href="http://www.adobe.com">Adobe</a> in 1993. As of July 1, 2008, it&#8217;s an <a href="http://en.wikipedia.org/wiki/International_Organization_for_Standardization">ISO</a> standard, which means that the format is open and published so that anyone can create it or use it.</p>
<p>There are many misconceptions about the proper use of PDFs, and today I&#8217;m going to try to explain how to properly use PDFs on the Internet. Monday I&#8217;ll give a couple of faster, easier alternatives to Adobe&#8217;s bloated Reader product and discuss some tools to create PDFs without having to use Adobe&#8217;s obscenely expensive <a class="zem_slink" title="Adobe Acrobat" rel="homepage" href="http://www.adobe.com/acrobat">Acrobat</a> product.</p>
<p>The advantage that PDF has over other file formats is that it&#8217;s a good way to represent printed material exactly as the designer intended it. This advantage makes it good to use for contracts and brochures where the user doesn&#8217;t need to change the content and is willing to jump through some extra hoops to view the content in a layout that approximates the printed page. It&#8217;s a great format for designers to send to printers because it ensures that the content is displayed exactly as the designer intended.</p>
<p>The disadvantage that PDF has is on the Internet. <span class="pullquote">The Internet isn&#8217;t a format that is supposed to resemble the printed page</span>. Because the PDF format &#8211; for good reason &#8211; isn&#8217;t supported by any browser, the user must use a <a class="zem_slink" title="Plug-in (computing)" rel="wikipedia" href="http://en.wikipedia.org/wiki/Plug-in_%28computing%29">browser plug-in</a> to view the content, souring the browsing experience. For this reason, the use of PDFs on websites should be limited to an optional content delivery mechanism.</p>
<p>An example of a very bad use of PDF is for a website selling real estate. The designer used PDF to send the property information document to the printer. The PDF is uploaded to the website and a link is placed on a sparse page that says &#8220;download property information document&#8221; for information about this property. This breaks the first rule of accessible website design, which is <em>don&#8217;t force the user to use a plug-in or add-on to view content</em>. Most browsers with the plug-in installed open the page in a new tab, breaking another first rule of web design which is <em>don&#8217;t open new tabs or windows</em>. Search engines index PDFs, but if you click on a search result that is a PDF you&#8217;ll be taken straight to the PDF which lacks a navigational system for the user to get to your main website.</p>
<p>An example of a very good use of PDF is for the same website to have every piece of information within the property document delivered as valid <a class="zem_slink" title="XHTML" rel="wikipedia" href="http://en.wikipedia.org/wiki/XHTML">XHTML</a> / <a class="zem_slink" title="Cascading Style Sheets" rel="wikipedia" href="http://en.wikipedia.org/wiki/Cascading_Style_Sheets">CSS</a> on the website page with an optional download for users who want to physically print the information about the property. In this case, the user can browse the property information at browser speeds rather than having to wait for and be confused by the loading of a plugin. Even the example property contracts should be first delivered on the website and also made available as PDF for users who want that method as an option.</p>
<p>The very best use of PDF is to not use it at all, delivering the content by XHTML and the layout by two style sheets, one CSS for the screen and one print style sheet, so that the website looks one way on the screen but when the website is printed it looks like the property information document. This is a more advanced website design technique that I&#8217;ll try to cover later.</p>
<p>To summarize, PDF has its uses. Just remember that as a content delivery system on the Internet it falls short.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.auctioneertech.com/2008/pdf-should-be-optional-on-web/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
