<?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>DigiKev &#187; Dino Esposito</title>
	<atom:link href="/tag/dino-esposito/feed/" rel="self" type="application/rss+xml" />
	<link>http://digikev.co.uk</link>
	<description>Building experiences &#124; Web design, interface design, information architecture and user experience</description>
	<lastBuildDate>Thu, 05 Nov 2009 22:06:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Why aren&#8217;t experts like Microsoft being expert?</title>
		<link>http://digikev.co.uk/03-05-2008/why-arent-experts-like-microsoft-being-expert/</link>
		<comments>http://digikev.co.uk/03-05-2008/why-arent-experts-like-microsoft-being-expert/#comments</comments>
		<pubDate>Sat, 03 May 2008 22:32:54 +0000</pubDate>
		<dc:creator>Kevin Rapley</dc:creator>
				<category><![CDATA[Web design]]></category>
		<category><![CDATA[Web development]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[ASP NET]]></category>
		<category><![CDATA[authorities]]></category>
		<category><![CDATA[click here]]></category>
		<category><![CDATA[Dino Esposito]]></category>
		<category><![CDATA[experts]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[Microsoft]]></category>

		<guid isPermaLink="false">http://www.digikev.co.uk/digikevwp/?p=21</guid>
		<description><![CDATA[It shocks me to see web programming examples breaking the rules of accessibility and common practices in published books. I don’t feel it sets the greatest of examples to anyone trying to get a foot in the industry when supposed authorities on subjects cannot even get it correct in their own publications. Take Microsoft Press [...]]]></description>
			<content:encoded><![CDATA[<p>It shocks me to see web programming examples breaking the rules of accessibility and common practices in published books. I don’t feel it sets the greatest of examples to anyone trying to get a foot in the industry when supposed authorities on subjects cannot even get it correct in their own publications. Take Microsoft Press for instance. Programming Microsoft ASP.NET 3.5, published 2008. This is written by Dino Esposito, an authority on ASP.NET and AJAX. When it comes to writing HTML he seems to have forgotten the fact that we keep the code in lowercase. All of his HTML examples begin with a capital letter. Now I understand that ASP.NET is different and uses some uppercase characters for server side controls, but please let us not forget the industry standard for writing static HTML. Long have the days passed when HTML tags were written in complete uppercase and contained now deprecated elements such as FONT and CENTER.Furthermore another example I have spotted failed to include a DOCTYPE and the appropriate XML format for closing a HR tag. I realise this is not the purpose of the book and that the level of reader will most likely have a full understanding of how we conduct ourselves as web designer and developers in 2008. But why do experts insist on writing poor examples?<br />
<span id="more-79"></span><br />
Let me take this even further. Being an organisation that should be getting this correct, Microsoft will bear the brunt of this again for not. There are plenty of examples within the Microsoft website where use of inaccessible and erroneous terms such as ‘click here’. Going back to the Microsoft Press example too, I was studying a script for SilverLight where it would display a message if a user did not have the plugin installed on their machine. This was again ‘click here to…’. If these are such expert guides to the technology for developing next-generation websites, then I think more care should be put in to eradicating these poor phrases and terms so that the next generation of web designers know not to do it.</p>
]]></content:encoded>
			<wfw:commentRss>http://digikev.co.uk/03-05-2008/why-arent-experts-like-microsoft-being-expert/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

