<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: 5 basic rules to better accessibility in web design.</title>
	<atom:link href="http://www.daynw.com/5-basic-rules-to-better-accessibility-in-web-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.daynw.com/5-basic-rules-to-better-accessibility-in-web-design/</link>
	<description>I am a web presence strategist, graphic designer, UX nut, and proponent of social media influence marketing. These are my notes.</description>
	<lastBuildDate>Thu, 02 Sep 2010 10:11:11 -0400</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Joey Yax</title>
		<link>http://www.daynw.com/5-basic-rules-to-better-accessibility-in-web-design/comment-page-1/#comment-191</link>
		<dc:creator>Joey Yax</dc:creator>
		<pubDate>Fri, 20 Jun 2008 19:03:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.daynw.com/?p=77#comment-191</guid>
		<description>Great post Dayn!

Couple things worth adding...

Structure: Use Header tags (h1, h2, etc...) and use them in the right order. H1 is used for the primary header on the page and should only be used once as the title of the page. H2 is used for sub-categories, followed by h3 and so on... Other tags can be used repeatedly, but use them in order of relevance. 

Clean Code: Order your sections properly. Header, Navigation, Content, Footer. Then style accordingly with CSS. Unless you want a screen reader to read what in your sidebar first, then you need to have the primary content for the page BEFORE the sidebar content. It doesn&#039;t matter if visually you want the sidebar on the left. It should still come after the primary content, then styled (floated) with CSS to where you want it.

Accessibility marks and &quot;jump to&quot; links: Provide hidden markers and links for screen readers. Label your navigation, label your content area, label your sidebar and assign them ids. These don&#039;t have to be visible in the visual layout but makes it worlds easier for the screen readers to visualize where they are on the page.

Re the &quot;jump to&quot; link: at the top of the page provide a few links (again only visible when stylesheet is turned off) that will allow a user to &quot;jump&quot; to navigation, content area, sidebar, etc... on the page.

Hope those help (or at least make sense)

Lastly, here&#039;s another good blog post re: SEO for designers that I think would make for a good extended read of this one:
http://justcreativedesign.com/2008/06/09/10-seo-rules-for-designers/

(that got long. Sorry. This list could almost go on forever.)</description>
		<content:encoded><![CDATA[<p>Great post Dayn!</p>
<p>Couple things worth adding&#8230;</p>
<p>Structure: Use Header tags (h1, h2, etc&#8230;) and use them in the right order. H1 is used for the primary header on the page and should only be used once as the title of the page. H2 is used for sub-categories, followed by h3 and so on&#8230; Other tags can be used repeatedly, but use them in order of relevance. </p>
<p>Clean Code: Order your sections properly. Header, Navigation, Content, Footer. Then style accordingly with CSS. Unless you want a screen reader to read what in your sidebar first, then you need to have the primary content for the page BEFORE the sidebar content. It doesn&#8217;t matter if visually you want the sidebar on the left. It should still come after the primary content, then styled (floated) with CSS to where you want it.</p>
<p>Accessibility marks and &#8220;jump to&#8221; links: Provide hidden markers and links for screen readers. Label your navigation, label your content area, label your sidebar and assign them ids. These don&#8217;t have to be visible in the visual layout but makes it worlds easier for the screen readers to visualize where they are on the page.</p>
<p>Re the &#8220;jump to&#8221; link: at the top of the page provide a few links (again only visible when stylesheet is turned off) that will allow a user to &#8220;jump&#8221; to navigation, content area, sidebar, etc&#8230; on the page.</p>
<p>Hope those help (or at least make sense)</p>
<p>Lastly, here&#8217;s another good blog post re: SEO for designers that I think would make for a good extended read of this one:<br />
<a href="http://justcreativedesign.com/2008/06/09/10-seo-rules-for-designers/" rel="nofollow">http://justcreativedesign.com/2008/06/09/10-seo-rules-for-designers/</a></p>
<p>(that got long. Sorry. This list could almost go on forever.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
