<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: A Command of Headings: Usage and Styling</title>
	<link>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/</link>
	<description>The Art of Accessibility</description>
	<pubDate>Thu, 24 Jul 2008 16:30:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Craig</title>
		<link>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2470</link>
		<pubDate>Wed, 16 Apr 2008 22:05:12 +0000</pubDate>
		<guid>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2470</guid>
					<description>As a website designer, I work closely with copywriters and a few marketing consultants, the one thing that everyone of us agrees on is that "it's all in the header". If it's not in the header, it's not that important. I am always looking for ways to make unique header designs that are seo friendly.  Great Article!</description>
		<content:encoded><![CDATA[<p>As a website designer, I work closely with copywriters and a few marketing consultants, the one thing that everyone of us agrees on is that &#8220;it&#8217;s all in the header&#8221;. If it&#8217;s not in the header, it&#8217;s not that important. I am always looking for ways to make unique header designs that are seo friendly.  Great Article!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Irfanullah</title>
		<link>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2388</link>
		<pubDate>Tue, 01 Apr 2008 10:42:09 +0000</pubDate>
		<guid>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2388</guid>
					<description>Your Site home page allignment is problem when i use FIRE BUG  just check it......</description>
		<content:encoded><![CDATA[<p>Your Site home page allignment is problem when i use FIRE BUG  just check it&#8230;&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mike Cherim</title>
		<link>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2340</link>
		<pubDate>Fri, 21 Mar 2008 03:39:46 +0000</pubDate>
		<guid>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2340</guid>
					<description>&lt;blockquote cite="#comment-2339"&gt;
if that’s okay with you
&lt;/blockquote&gt;

By all means Jordon. :)</description>
		<content:encoded><![CDATA[<blockquote cite="#comment-2339"><p>
if that’s okay with you
</p></blockquote>
<p>By all means Jordon. <img src='http://accessites.org/site/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jordan Clark</title>
		<link>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2339</link>
		<pubDate>Fri, 21 Mar 2008 02:44:51 +0000</pubDate>
		<guid>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2339</guid>
					<description>&lt;a href="#comment-2155" title="Comment posted on February 17th, 2008 at 10:31 am" rel="nofollow"&gt;@ Mike&lt;/a&gt;:

Great article... Oh, I really like your idea about combining the site name and the content title in the &lt;code&gt;h1&lt;/code&gt; element - what a great idea! 

I too have often agonised over the &lt;code&gt;h1&lt;/code&gt; "site name versus article name" dilemma, and I think your approach let's you have the penny &lt;em&gt;and&lt;/em&gt; the bun, so to speak.

In future, I think I might "borrow" this technique (if that's okay with you)!</description>
		<content:encoded><![CDATA[<p><a href="#comment-2155" title="Comment posted on February 17th, 2008 at 10:31 am" rel="nofollow">@ Mike</a>:</p>
<p>Great article&#8230; Oh, I really like your idea about combining the site name and the content title in the <code>h1</code> element - what a great idea! </p>
<p>I too have often agonised over the <code>h1</code> &#8220;site name versus article name&#8221; dilemma, and I think your approach let&#8217;s you have the penny <em>and</em> the bun, so to speak.</p>
<p>In future, I think I might &#8220;borrow&#8221; this technique (if that&#8217;s okay with you)!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Max Design - standards based web design, development and training &#187; Some links for light reading (18/3/08)</title>
		<link>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2311</link>
		<pubDate>Tue, 18 Mar 2008 10:35:01 +0000</pubDate>
		<guid>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2311</guid>
					<description>[...] A Command of Headings: Usage and Styling [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] A Command of Headings: Usage and Styling [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Christian</title>
		<link>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2292</link>
		<pubDate>Fri, 14 Mar 2008 16:35:26 +0000</pubDate>
		<guid>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2292</guid>
					<description>Good post. At my job I always wonder why I'm coming across old code that others programmed that has fake headers made by span tags with classes attached to them. Don't these people know there's such a thing as header tags? And I have several sites where I have drilled down to using level 6 headers, including my personal site.</description>
		<content:encoded><![CDATA[<p>Good post. At my job I always wonder why I&#8217;m coming across old code that others programmed that has fake headers made by span tags with classes attached to them. Don&#8217;t these people know there&#8217;s such a thing as header tags? And I have several sites where I have drilled down to using level 6 headers, including my personal site.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jermayn Parker</title>
		<link>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2162</link>
		<pubDate>Tue, 19 Feb 2008 06:40:56 +0000</pubDate>
		<guid>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2162</guid>
					<description>Just for arguments sake
"Think parents, children, grandchildren, and so on, as the content’s organization will dictate."

So are you saying that the children are all single-parented? Keeping up with todays generation :P</description>
		<content:encoded><![CDATA[<p>Just for arguments sake<br />
&#8220;Think parents, children, grandchildren, and so on, as the content’s organization will dictate.&#8221;</p>
<p>So are you saying that the children are all single-parented? Keeping up with todays generation <img src='http://accessites.org/site/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mike Cherim</title>
		<link>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2155</link>
		<pubDate>Sun, 17 Feb 2008 15:31:17 +0000</pubDate>
		<guid>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2155</guid>
					<description>@Anup: 

&lt;blockquote cite="#comment-2153"&gt;
On many sites, you get the home page have the site's name/logo in an H1. On the sub-sites (e.g. articles, blog posts etc), many continue to use H1 for the same logo/name, and H2 then becomes used as the page heading. Other sites I have seen then use two H1s. What would you suggest?
&lt;/blockquote&gt;

Here on this site we use the &lt;code&gt;h1&lt;/code&gt; as a combo. On the home page it is for the name of the site followed by the tagline. On other pages it is the name of the site followed by the page's main content title, as echoed by the &lt;code&gt;h2&lt;/code&gt;. I don't have a huge preference either way. If someone uses it as a site title followed with a &lt;code&gt;h2&lt;/code&gt; for the page title, as long as they use their &lt;code&gt;title&lt;/code&gt; element smartly it won't impact &lt;abbr title="Search Engine Optimization"&gt;SEO&lt;/abbr&gt; or the accessibility of the page semantics are still intact, just different. So I'm cool with it either way. Even if someone has two &lt;code&gt;h1&lt;/code&gt;s, I'm not dead set against, it just doesn't seem right to me. Like a book with two titles.</description>
		<content:encoded><![CDATA[<p>@Anup: </p>
<blockquote cite="#comment-2153"><p>
On many sites, you get the home page have the site&#8217;s name/logo in an H1. On the sub-sites (e.g. articles, blog posts etc), many continue to use H1 for the same logo/name, and H2 then becomes used as the page heading. Other sites I have seen then use two H1s. What would you suggest?
</p></blockquote>
<p>Here on this site we use the <code>h1</code> as a combo. On the home page it is for the name of the site followed by the tagline. On other pages it is the name of the site followed by the page&#8217;s main content title, as echoed by the <code>h2</code>. I don&#8217;t have a huge preference either way. If someone uses it as a site title followed with a <code>h2</code> for the page title, as long as they use their <code>title</code> element smartly it won&#8217;t impact <abbr title="Search Engine Optimization">SEO</abbr> or the accessibility of the page semantics are still intact, just different. So I&#8217;m cool with it either way. Even if someone has two <code>h1</code>s, I&#8217;m not dead set against, it just doesn&#8217;t seem right to me. Like a book with two titles.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: David Zemens - 1955 Design</title>
		<link>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2154</link>
		<pubDate>Sun, 17 Feb 2008 13:23:19 +0000</pubDate>
		<guid>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2154</guid>
					<description>Thanks for the primer on the correct way to use the various heading elements, Mike.  It's easy to get sloppy and use them in the incorrect way.  I agree with you that I have rarely, if ever, used &lt;code&gt;h5&lt;/code&gt; or &lt;code&gt;h6&lt;/code&gt; in my projects.

Your suggestions on ways to style the headings are also a great reminder of the flexibility we all have with our stylesheet.  Your tips always leave me with a new idea on how to approach the styling on one of my projects!</description>
		<content:encoded><![CDATA[<p>Thanks for the primer on the correct way to use the various heading elements, Mike.  It&#8217;s easy to get sloppy and use them in the incorrect way.  I agree with you that I have rarely, if ever, used <code>h5</code> or <code>h6</code> in my projects.</p>
<p>Your suggestions on ways to style the headings are also a great reminder of the flexibility we all have with our stylesheet.  Your tips always leave me with a new idea on how to approach the styling on one of my projects!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Anup</title>
		<link>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2153</link>
		<pubDate>Sun, 17 Feb 2008 11:08:52 +0000</pubDate>
		<guid>http://accessites.org/site/2008/02/a-command-of-headings-usage-and-styling/#comment-2153</guid>
					<description>Good post! Headings are really important as you outline. I still come across a few people who say they don't like to use H2; they prefer H3 or something because of the size etc...

One question for you: a while back (I don't know if it is still the case), the RNIB used to insist that the H1 had to be a) the first heading, b) the only H1 allowed on a page.

For different pages this may or may not make sense (Eric Meyer had a good case of using H1's for each slide title in his S5 slide system, which was built on semantic HTML + JavaScript for the slide effects.)

On many sites, you get the home page have the site's name/logo in an H1. On the sub-sites (e.g. articles, blog posts etc), many continue to use H1 for the same logo/name, and H2 then becomes used as the page heading. Other sites I have seen then use two H1s. What would you suggest?</description>
		<content:encoded><![CDATA[<p>Good post! Headings are really important as you outline. I still come across a few people who say they don&#8217;t like to use H2; they prefer H3 or something because of the size etc&#8230;</p>
<p>One question for you: a while back (I don&#8217;t know if it is still the case), the RNIB used to insist that the H1 had to be a) the first heading, b) the only H1 allowed on a page.</p>
<p>For different pages this may or may not make sense (Eric Meyer had a good case of using H1&#8217;s for each slide title in his S5 slide system, which was built on semantic HTML + JavaScript for the slide effects.)</p>
<p>On many sites, you get the home page have the site&#8217;s name/logo in an H1. On the sub-sites (e.g. articles, blog posts etc), many continue to use H1 for the same logo/name, and H2 then becomes used as the page heading. Other sites I have seen then use two H1s. What would you suggest?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
