<?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/"
	>

<channel>
	<title>These things are far too hard &#187; accessibility</title>
	<atom:link href="http://leadingedgescripts.co.uk/tag/accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://leadingedgescripts.co.uk</link>
	<description></description>
	<lastBuildDate>Fri, 16 Oct 2009 09:14:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Accessibility and Popup Links</title>
		<link>http://leadingedgescripts.co.uk/web-development/accessibility-and-popup-links/</link>
		<comments>http://leadingedgescripts.co.uk/web-development/accessibility-and-popup-links/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 13:55:03 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[target="_blank"]]></category>

		<guid isPermaLink="false">http://www.leadingedgescripts.co.uk/?p=204</guid>
		<description><![CDATA[Ok, I&#8217;m sure this has probably been posted about elsewhere, but I&#8217;m starting to think that some of the guidelines and XHTML specs shouldn&#8217;t be treated as strict rules. For example, I seem to get this a lot, you build a website using a Strict XHTML doctype and then clients start to ask you to [...]]]></description>
			<content:encoded><![CDATA[<p>Ok, I&#8217;m sure this has probably been posted about elsewhere, but I&#8217;m starting to think that some of the guidelines and XHTML specs shouldn&#8217;t be treated as strict rules.</p>
<p>For example, I seem to get this a lot, you build a website using a Strict XHTML doctype and then clients start to ask you to put popup links in (target=&#8221;_blank&#8221;) now we all know that this goes against the strict doctype and doesn&#8217;t validate, but when I object to my clients, well, they still want this feature.</p>
<p>On reflection perhaps it&#8217;s not such a bad thing anyway, a lot of times a link will open a pdf and lots of users close the window expecting to return to their web browser, but actually end up closing their browser altogether.</p>
<p>Instead of putting the focus on web developers, perhaps we should ban these browser add-ins as a worse barrier to usability than target=&#8221;_blank&#8221; links, which in this example may improve usability&#8230;</p>
<p>I know I can switch to the transitional doctype to get round this, but generally I&#8217;d prefer not to have to.</p>
<p>I also understand that XHTML was developed to work across a number of applications / devices and therefore target=&#8221;_blank&#8221; may not be great for pdas or mobile phones, but neither is a pdf document which most mobile phone users can&#8217;t (yet) open.</p>
]]></content:encoded>
			<wfw:commentRss>http://leadingedgescripts.co.uk/web-development/accessibility-and-popup-links/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
