<?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>Web Do&#039;s &#38; Don&#039;ts</title>
	<atom:link href="http://webdosanddonts.com/feed" rel="self" type="application/rss+xml" />
	<link>http://webdosanddonts.com</link>
	<description>Tips&#38;Tricks for the modern day web designer</description>
	<lastBuildDate>Sun, 07 Mar 2010 20:43:14 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Don’t use HTTP based resources on a HTTPS page</title>
		<link>http://webdosanddonts.com/dont-use-http-based-resources-on-a-https-page</link>
		<comments>http://webdosanddonts.com/dont-use-http-based-resources-on-a-https-page#comments</comments>
		<pubDate>Sun, 07 Mar 2010 20:35:27 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Don'ts]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[Optimization]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=944</guid>
		<description><![CDATA[Internet Explorer interrupts the download and displays a confirmation dialog whenever it detects the use of mixed content on a secure page.
In IE 7 and ealier, this dialog would cause annoyance to users but generally didn’t cause any other significant problems because most users would click on the Yes button and allow non-secure content to [...]]]></description>
			<content:encoded><![CDATA[<p>Internet Explorer interrupts the download and displays a confirmation dialog whenever it detects the use of mixed content on a secure page.</p>
<p>In <strong>IE 7 and ealier</strong>, this dialog would cause annoyance to users but generally didn’t cause any other significant problems because most users would click on the <strong>Yes button</strong> and allow non-secure content to be downloaded. However, the wording in the <strong>IE 8</strong> version of this dialog has changed and to download the content a user would now have to click on the <strong>No button</strong>.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/dont-use-http-based-resources-on-a-https-page/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Specify a text colour for img elements</title>
		<link>http://webdosanddonts.com/specify-a-text-colour-for-img-elements</link>
		<comments>http://webdosanddonts.com/specify-a-text-colour-for-img-elements#comments</comments>
		<pubDate>Wed, 03 Mar 2010 08:59:09 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=936</guid>
		<description><![CDATA[Some browsers display the alt text when an img element is not displayed. The alt text can sometimes be invisible or hard to read, if the color of the text is similar to the background color. Therefore, specify the color(s) and check how it looks in the browser.
]]></description>
			<content:encoded><![CDATA[<p>Some browsers display the alt text when an <code>img</code> element is not displayed. The alt text can sometimes be invisible or hard to read, if the color of the text is similar to the background color. Therefore, specify the color(s) and check how it looks in the browser.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/specify-a-text-colour-for-img-elements/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t use protocol relative paths to CSS files</title>
		<link>http://webdosanddonts.com/dont-use-protocol-relative-paths-to-css-files</link>
		<comments>http://webdosanddonts.com/dont-use-protocol-relative-paths-to-css-files#comments</comments>
		<pubDate>Wed, 24 Feb 2010 18:53:03 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Don'ts]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[Optimization]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=942</guid>
		<description><![CDATA[Internet Explorer 7 &#038; 8 will download stylesheets twice if the http(s) protocol is missing.
]]></description>
			<content:encoded><![CDATA[<p>Internet Explorer 7 &#038; 8 will download stylesheets twice if the http(s) protocol is missing.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/dont-use-protocol-relative-paths-to-css-files/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Plan the absence of Javascript</title>
		<link>http://webdosanddonts.com/plan-the-absence-of-javascript</link>
		<comments>http://webdosanddonts.com/plan-the-absence-of-javascript#comments</comments>
		<pubDate>Mon, 15 Feb 2010 19:38:05 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[Javascript]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=938</guid>
		<description><![CDATA[The fact is that some of your website’s visitors will have JavaScript disabled. Should hidden content remain hidden even if JavaScript is disabled? Should all content be available to screen readers and search engines? If a piece of content becomes visible only after an AJAX call, how do you adequately fill that space when JavaScript [...]]]></description>
			<content:encoded><![CDATA[<p>The fact is that some of your website’s visitors will have JavaScript disabled. Should hidden content remain hidden even if JavaScript is disabled? Should all content be available to screen readers and search engines? If a piece of content becomes visible only after an AJAX call, how do you adequately fill that space when JavaScript is disabled?</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/plan-the-absence-of-javascript/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Always provide an alt text in img elements</title>
		<link>http://webdosanddonts.com/always-provide-an-alt-text-in-img-elements</link>
		<comments>http://webdosanddonts.com/always-provide-an-alt-text-in-img-elements#comments</comments>
		<pubDate>Wed, 03 Feb 2010 09:24:11 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Beginner]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[alt]]></category>
		<category><![CDATA[HTML]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=873</guid>
		<description><![CDATA[The alt attribute is a textual replacement for the image which is not being displayed. It must always be used, even if the image in question is purely decorative&#8211;in that case, the alt attribute should be an empty string.
]]></description>
			<content:encoded><![CDATA[<p>The <code>alt</code> attribute is a textual replacement for the image which is not being displayed. It must always be used, even if the image in question is purely decorative&#8211;in that case, the <code>alt</code> attribute should be an empty string.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/always-provide-an-alt-text-in-img-elements/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Use tables in HTML email</title>
		<link>http://webdosanddonts.com/use-tables-in-html-email</link>
		<comments>http://webdosanddonts.com/use-tables-in-html-email#comments</comments>
		<pubDate>Fri, 08 Jan 2010 08:59:28 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[e-mail]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[Tables]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=898</guid>
		<description><![CDATA[Tables are inappropriate for layout, but a necessary evil in HTML e-mail. Mail clients have bad CSS support which means we must use tables when coding newsletters to ensure consistent display across clients. 
]]></description>
			<content:encoded><![CDATA[<p>Tables are <a href="http://webdosanddonts.com/never-use-html-tables-for-layout">inappropriate for layout</a>, but a necessary evil in HTML e-mail. Mail clients have bad CSS support which means we must use tables when coding newsletters to ensure consistent display across clients. </p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/use-tables-in-html-email/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Get familiar with CSS escape sequences</title>
		<link>http://webdosanddonts.com/get-familiar-with-css-escape-sequences</link>
		<comments>http://webdosanddonts.com/get-familiar-with-css-escape-sequences#comments</comments>
		<pubDate>Sat, 02 Jan 2010 11:38:43 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Escape]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=901</guid>
		<description><![CDATA[Escape sequences are useful because they allow style sheet authors to represent characters that would normally be ignored or interpreted differently by traditional CSS parsing rules.
]]></description>
			<content:encoded><![CDATA[<p>Escape sequences are useful because they allow style sheet authors to represent characters that would normally be ignored or interpreted differently by traditional CSS parsing rules.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/get-familiar-with-css-escape-sequences/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t be skipping heading levels</title>
		<link>http://webdosanddonts.com/dont-be-skipping-heading-levels</link>
		<comments>http://webdosanddonts.com/dont-be-skipping-heading-levels#comments</comments>
		<pubDate>Sat, 26 Dec 2009 12:55:53 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Don'ts]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Heading]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[Markup]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=912</guid>
		<description><![CDATA[One of the benefits of a proper and consistent heading structure in an HTML page is that they can be repurposed to improve access to the content. Also keep in mind that skipping a heading level makes navigating by headers less usable for screenreader users.
]]></description>
			<content:encoded><![CDATA[<p>One of the benefits of a proper and consistent heading structure in an HTML page is that they can be repurposed to improve access to the content. Also keep in mind that skipping a heading level makes navigating by headers less usable for screenreader users.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/dont-be-skipping-heading-levels/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Use the title attribute on form elements</title>
		<link>http://webdosanddonts.com/use-the-title-attribute-on-form-elements</link>
		<comments>http://webdosanddonts.com/use-the-title-attribute-on-form-elements#comments</comments>
		<pubDate>Mon, 21 Dec 2009 18:43:58 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Forms]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[Title]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=904</guid>
		<description><![CDATA[The title attribute offers an extra avenue for associating text to a form field. It should not be used as the first means of associating a label text with a corresponding form field. In situations where supplementary information is useful, the title attribute is helpful. 
]]></description>
			<content:encoded><![CDATA[<p>The <code>title</code> attribute offers an extra avenue for associating text to a form field. It should not be used as the first means of associating a label text with a corresponding form field. In situations where supplementary information is useful, the <code>title</code> attribute is helpful. </p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/use-the-title-attribute-on-form-elements/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Skip navigation links</title>
		<link>http://webdosanddonts.com/skip-navigation-links</link>
		<comments>http://webdosanddonts.com/skip-navigation-links#comments</comments>
		<pubDate>Mon, 07 Dec 2009 10:00:43 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Beginner]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=878</guid>
		<description><![CDATA[Provide a link to skip over navigation links, helping keyboard and screen reader users to jump to the main content of the page.
]]></description>
			<content:encoded><![CDATA[<p>Provide a link to skip over navigation links, helping keyboard and screen reader users to jump to the main content of the page.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/skip-navigation-links/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
