<?xml version="1.0" encoding="iso-8859-1"?>
<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 Words &#187; Web Standards</title>
	<atom:link href="http://wizardev.ca/web-words/category/web-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://wizardev.ca</link>
	<description>Web development resources</description>
	<lastBuildDate>Fri, 04 Feb 2011 02:30:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>A Web Standards Checklist (MaxDesign)</title>
		<link>http://wizardev.ca/a-web-standards-checklist/</link>
		<comments>http://wizardev.ca/a-web-standards-checklist/#comments</comments>
		<pubDate>Fri, 21 Oct 2005 04:01:19 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/a-web-standards-checklist</guid>
		<description><![CDATA[The term web standards can mean different things to different people. For some, it is &#8216;table-free sites&#8217;, for others it is &#8216;using valid code&#8217;. However, web standards are much broader than that. A site built to web standards should adhere to standards (HTML, XHTML, XML, CSS, XSLT, DOM, MathML, SVG, etc.) and pursue best practices [...]]]></description>
			<content:encoded><![CDATA[<p>The term web standards can mean different things to different people. For some, it is &#8216;table-free sites&#8217;, for others it is &#8216;using valid code&#8217;. However, web standards are much broader than that. A site built to web standards should adhere to standards (HTML, XHTML, XML, CSS, XSLT, DOM, MathML, SVG, etc.) and pursue best practices (valid code, accessible code, semantically correct code, user-friendly URLs, etc.).  In other words, a site built to web standards should ideally be lean, clean, CSS-based, accessible, usable and search engine friendly.  <small>(Document updated: August 13, 2004)</small></p>
<p><a href="http://www.maxdesign.com.au/presentation/checklist.cfm" rel="external">Read the Document&#8230;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/a-web-standards-checklist/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AJAX, accessibility and the user</title>
		<link>http://wizardev.ca/ajax-accessibility-and-the-user/</link>
		<comments>http://wizardev.ca/ajax-accessibility-and-the-user/#comments</comments>
		<pubDate>Tue, 16 Oct 2007 21:03:08 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Web Tech]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/ajax-accessibility-and-the-user</guid>
		<description><![CDATA[One on the myths of accessibility is that it suppresses creativity and progress. People mistakenly think you can’t use innovative new technologies and your web sites have to remain flat and boring. This is not the case as accessibility is one part of the design process and works alongside, not against, innovative design. The only [...]]]></description>
			<content:encoded><![CDATA[<p>One on the myths of accessibility is that it suppresses creativity and progress. People mistakenly think you can’t use innovative new technologies and your web sites have to remain flat and boring. This is not the case as accessibility is one part of the design process and works alongside, not against, innovative design. The only difference is that you need to keep all users in mind and build to standards. <small>(Article dated: October 1, 2007)</small></p>
<p>Read <a href="http://www.rnib.org.uk/wacblog/javascript/ajax-accessibility-and-the-user/" rel="external">AJAX, accessibility and the user</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/ajax-accessibility-and-the-user/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bite Size Standards</title>
		<link>http://wizardev.ca/bite-size-standards/</link>
		<comments>http://wizardev.ca/bite-size-standards/#comments</comments>
		<pubDate>Sat, 22 Apr 2006 22:02:42 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/bite-size-standards</guid>
		<description><![CDATA[Bite Size Standards aims to offer concise web development tutorials, tips and tricks. Written by designers and developers who are passionate about web standards. View the Site&#8230;]]></description>
			<content:encoded><![CDATA[<p>Bite Size Standards aims to offer concise web development tutorials, tips and tricks. Written by designers and developers who are passionate about web standards. </p>
<p><a href="http://bitesizestandards.com/" rel="external">View the Site&#8230;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/bite-size-standards/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cleaning up Code with Semantic Anchors (Bite Size Standards)</title>
		<link>http://wizardev.ca/cleaning-up-code-with-semantic-anchors-bite-size-standards/</link>
		<comments>http://wizardev.ca/cleaning-up-code-with-semantic-anchors-bite-size-standards/#comments</comments>
		<pubDate>Tue, 25 Jul 2006 15:01:40 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/cleaning-up-code-with-semantic-anchors-bite-size-standards</guid>
		<description><![CDATA[The a element is all too common when building websites. We use it to create hyperlinks to other parts of our site and to external sites. We can also use it to link to specific sections on the current page, so a visitor can click on a link and jump to a footnote or to [...]]]></description>
			<content:encoded><![CDATA[<p>The <code>a</code> element is all too common when building websites. We use it to create hyperlinks to other parts of our site and to external sites. We can also use it to link to specific sections on the current page, so a visitor can click on a link and jump to a footnote or to a specific answer on a Frequently Asked Questions page. <small>(Article dated: July 13, 2006)</small></p>
<p><a href="http://bitesizestandards.com/bites/cleaning-up-code-with-semantic-anchors" rel="external">Read the Article&#8230;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/cleaning-up-code-with-semantic-anchors-bite-size-standards/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Corporate Web Standards (Digital Web)</title>
		<link>http://wizardev.ca/corporate-web-standards-digital-web/</link>
		<comments>http://wizardev.ca/corporate-web-standards-digital-web/#comments</comments>
		<pubDate>Thu, 19 Jul 2007 23:20:32 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/corporate-web-standards-digital-web</guid>
		<description><![CDATA[Now that web standards have become the norm for corporate websites, many in-house developers are discovering a new phase of acceptance and implementation within many large online organizations—corporate web standards. (Article dated: July 16, 2007) Read Corporate Web Standards]]></description>
			<content:encoded><![CDATA[<p>Now that web standards have become the norm for corporate websites, many in-house developers are discovering a new phase of acceptance and implementation within many large online organizations—corporate web standards. <small>(Article dated: July 16, 2007)</small></p>
<p>Read <a href="http://www.digital-web.com/articles/corporate_web_standards/" rel="external">Corporate Web Standards</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/corporate-web-standards-digital-web/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Developing with Web Standards – Recommendations and Best Practices (456 Berea Street)</title>
		<link>http://wizardev.ca/developing-with-web-standards-recommendations-and-best-practices/</link>
		<comments>http://wizardev.ca/developing-with-web-standards-recommendations-and-best-practices/#comments</comments>
		<pubDate>Fri, 21 Oct 2005 03:49:15 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/developing-with-web-standards-recommendations-and-best-practices</guid>
		<description><![CDATA[This document explains how and why using web standards will let you build websites in a way that saves time and money for the developer and provides a better experience for the visitor. Also discussed are other methods, guidelines and best practices that will help produce high-quality websites that are accessible to as many as [...]]]></description>
			<content:encoded><![CDATA[<p>This document explains how and why using web standards will let you build websites in a way that saves time and money for the developer and provides a better experience for the visitor. Also discussed are other methods, guidelines and best practices that will help produce high-quality websites that are accessible to as many as possible. <small>(Document updated:  July 31, 2005)</small></p>
<p><a href="http://www.456bereastreet.com/lab/developing_with_web_standards/" rel="external">Read the Document&#8230;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/developing-with-web-standards-recommendations-and-best-practices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Accessible Search Rewards Accessibility (456 Berea Street)</title>
		<link>http://wizardev.ca/google-accessible-search-rewards-accessibility-456-berea-street/</link>
		<comments>http://wizardev.ca/google-accessible-search-rewards-accessibility-456-berea-street/#comments</comments>
		<pubDate>Wed, 26 Jul 2006 13:30:15 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/google-accessible-search-rewards-accessibility-456-berea-street</guid>
		<description><![CDATA[Google Accessible Search is a new Google product that is under development. It is designed to prioritise search results that are more usable to blind and visually impaired people. (Article dated: July 26, 2006) Read the Article&#8230; I was curious to see how this site would rank. Presented below, the first number is my position [...]]]></description>
			<content:encoded><![CDATA[<p>Google Accessible Search is a new Google product that is under development. It is designed to prioritise search results that are more usable to blind and visually impaired people. <small>(Article dated: July 26, 2006)</small></p>
<p><a href="http://www.456bereastreet.com/archive/200607/google_accessible_search_rewards_accessibility/" rel="external">Read the Article&#8230;</a></p>
<p>I was curious to see how this site would rank. Presented below, the first number is my position using the Google Accessible Search engine and the second is with Google proper.</p>
<ul>
<li><a href="http://www.google.com/u/accessible?hl=en&#038;lr=&#038;ie=ISO-8859-1&#038;cx=accessible%21&#038;q=web+development+Ottawa" target="_blank">web development Ottawa</a> &#8211; 1 vs. 4</li>
<li><a href="http://www.google.com/u/accessible?hl=en&#038;lr=&#038;ie=ISO-8859-1&#038;cx=accessible%21&#038;q=web+developer+Ottawa" target="_blank">web developer Ottawa</a> &#8211; 1 vs. 5</li>
<li><a href="http://www.google.com/u/accessible?hl=en&#038;lr=&#038;ie=ISO-8859-1&#038;cx=accessible%21&#038;q=web+designer+Ottawa&#038;btnG=Search" target="_blank">web designer Ottawa</a> &#8211; 5 vs. 58</li>
<li><a href="http://www.google.com/u/accessible?hl=en&#038;lr=&#038;ie=ISO-8859-1&#038;cx=accessible%21&#038;q=search+engine+marketing+and+optimization+ottawa" target="_blank">search engine marketing and optimization ottawa</a> &#8211; 3 vs. 28</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/google-accessible-search-rewards-accessibility-456-berea-street/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Government of Canada, Common Look and Feel, CLF 2.0</title>
		<link>http://wizardev.ca/government-of-canada-common-look-and-feel-20/</link>
		<comments>http://wizardev.ca/government-of-canada-common-look-and-feel-20/#comments</comments>
		<pubDate>Sat, 06 Jan 2007 17:53:15 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/government-of-canada-common-look-and-feel-20</guid>
		<description><![CDATA[The Government of Canada (GoC) has released its Common Look and Feel (CLF) Guidelines (version 2.0). I&#8217;ll be reading through this over the next few days to get myself up to speed. It is a vast improvement and I look forward to seeing all government sites updated over the next couple of years. I hope [...]]]></description>
			<content:encoded><![CDATA[<p>The Government of Canada (GoC) has released its <a href="" rel="external">Common Look and Feel</a> (CLF) Guidelines (version 2.0).  </p>
<p>I&#8217;ll be reading through this over the next few days to get myself up to speed.  It is a vast improvement and I look forward to seeing all government sites updated over the next couple of years.  </p>
<p>I hope to be a part of the updating process too.  <img src='http://wizardev.ca/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/government-of-canada-common-look-and-feel-20/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>New elements in HTML 5 &#8211; Structure and semantics</title>
		<link>http://wizardev.ca/new-elements-in-html-5-structure-and-semantics/</link>
		<comments>http://wizardev.ca/new-elements-in-html-5-structure-and-semantics/#comments</comments>
		<pubDate>Thu, 23 Aug 2007 13:06:07 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Web Tech]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/new-elements-in-html-5-structure-and-semantics</guid>
		<description><![CDATA[HTML 5 introduces new elements to HTML for the first time since the last millennium. New structural elements include aside, figure, and section. New inline elements include time, meter, and progress. New embedding elements include video and audio. New interactive elements include details, datagrid, and command. (Article dated: August 7, 2007) Read New elements in [...]]]></description>
			<content:encoded><![CDATA[<p>HTML 5 introduces new elements to HTML for the first time since the last millennium. New structural elements include <code>aside</code>, <code>figure</code>, and <code>section</code>. New inline elements include <code>time</code>, <code>meter</code>, and <code>progress</code>. New embedding elements include <code>video</code> and <code>audio</code>. New interactive elements include <code>details</code>, <code>datagrid</code>, and <code>command</code>.<br />
<small>(Article dated: August 7, 2007)</small></p>
<p>Read <a href="http://www.ibm.com/developerworks/library/x-html5/?ca=dgr-lnxw01NewHTML" rel="external">New elements in HTML 5 &#8211; Structure and semantics</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/new-elements-in-html-5-structure-and-semantics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New W3C HTML Working Group launched (456 Berea Street)</title>
		<link>http://wizardev.ca/new-w3c-html-working-group-launched-456-berea-street/</link>
		<comments>http://wizardev.ca/new-w3c-html-working-group-launched-456-berea-street/#comments</comments>
		<pubDate>Wed, 21 Mar 2007 16:28:16 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/new-w3c-html-working-group-launched-456-berea-street</guid>
		<description><![CDATA[The W3C announced the official launch of the new HTML Working Group that has been in the news since October last year, when Tim Berners-Lee blogged about the need to reinvent HTML. (Article dated: March 7, 2007) Read New W3C HTML Working Group launched and W3C Relaunches HTML Activity]]></description>
			<content:encoded><![CDATA[<p>The W3C announced the official launch of the new HTML Working Group that has been in the news since October last year, when Tim Berners-Lee blogged about the need to reinvent HTML. <small>(Article dated: March 7, 2007)</small></p>
<p>Read <a href="http://www.456bereastreet.com/archive/200703/new_w3c_html_working_group_launched/" rel="external">New W3C HTML Working Group launched</a> and <a href="http://www.w3.org/2007/03/html-pressrelease" rel="external">W3C Relaunches HTML Activity</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/new-w3c-html-working-group-launched-456-berea-street/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

