<?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>Paul Randall &#187; 960</title>
	<atom:link href="https://paulrandall.com/tag/960/feed/" rel="self" type="application/rss+xml" />
	<link>https://paulrandall.com</link>
	<description>Experimenting for a living.</description>
	<lastBuildDate>Sat, 15 Mar 2025 15:32:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.41</generator>
	<item>
		<title>The H1 Debate</title>
		<link>https://paulrandall.com/2009/02/06/the-h1-debate/</link>
		<comments>https://paulrandall.com/2009/02/06/the-h1-debate/#comments</comments>
		<pubDate>Fri, 06 Feb 2009 23:14:58 +0000</pubDate>
		<dc:creator><![CDATA[Paul]]></dc:creator>
				<category><![CDATA[semantics]]></category>
		<category><![CDATA[960]]></category>
		<category><![CDATA[h1]]></category>
		<category><![CDATA[html]]></category>
		<category><![CDATA[web design]]></category>

		<guid isPermaLink="false">http://prandall.com/?p=33</guid>
		<description><![CDATA[My tweet last week sparked a large discussion , and so I decided to try and find some opinions, and hopefully definitive answers to the H1 debate. The debate seems to polarise the web community, with many web designers using differing methods. Some tag the logo as an H1 element whilst others using the H1 [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>My <a title="H1 Debate" href="http://twitter.com/paulrandall/status/1161430931" target="_blank">tweet last week</a> sparked a large discussion , and so I decided to try and find some opinions, and hopefully definitive answers to the H1 debate.</p>
<p>The debate seems to polarise the web community, with many web designers using differing methods. Some tag the logo as an H1 element whilst others using the H1 for the page title.</p>
<h2>Twitter Opinions</h2>
<p>During the weekend, I spent a few hours with serial Twitter developer<a title="Ollie Parsley's Twitter Page" href="http://www.twitter.com/ollieparsley" target="_blank"> Ollie Parsley</a> and we created <a title="The H1 Debate" href="http://www.h1debate.com" target="_blank">www.h1debate.com</a>. The website was massively more popular than either of us imagined which in the space of a week, had been featured on over 20 websites, visited over 3,000 times and has had over 300 unique votes on the subject.</p>
<p>As of 6th Feb 2009, the ratio is split 70/30, with 70% of people preferring to use the H1 tag for the main heading, and 30% opting to wrap the company name or logo around an H1.<span id="more-33"></span></p>
<p>Quite a few high profile web designers added their opinion to the H1 Debate. You can read their comments as well as interesting articles on heading tags by following <a title="The H1 Debate on Twitter" href="http://www.twitter.com/h1debate" target="_blank">@h1debate</a>.</p>
<h2>Personal Opinion</h2>
<p>I do agree, there are certain pages that don’t have a specific main heading. For example the Digg.com website uses an H1 as the title on its homepage, yet uses an H1 as the main heading of an inside page, but every inner page has different content, and I think the H1 should describe it.</p>
<p>After reading the tweets, I have grown to like the idea of using an H1 on the homepage for the company name or logo, and to use H1 on ‘inside’ pages for the main page title.</p>
<p>From a search engine point of view, does an H1s’ weighting decrease if each page of the website is called the same name?</p>
<h2>Accessibility</h2>
<p>After looking into the subject of headings and accessibility, I came across a YouTube video by Aaron Cannon, and Accessibility Consultant who says:</p>
<blockquote cite="http://uk.youtube.com/watch?v=AmUPhEVWu_E"><p>All good screen readers offer a feature to jump from heading to heading. Assuming that headings are used properly on a website they can give an overview of what the author wanted to stand out. What were the important sections of the website.</p></blockquote>
<p><a title="Heading Tags and Accessibility" href="http://uk.youtube.com/watch?v=AmUPhEVWu_E" target="_blank">http://uk.youtube.com/watch?v=AmUPhEVWu_E</a></p>
<p>With a screen reader, pressing the H key takes you to the first heading, and allows you to jump from headline to headline. This allows you to jump to the content and start reading. Using the same H1 would mean that a screen reader would read out the company name/logo every single time on each page. Is that useful? Is it the best use of an H1? Once maybe, but on every page, I can imagine it gets repetitive for the user.</p>
<h2>The Early Days of HTML</h2>
<p>Another area of my research took me to an early (1992) document, which states:</p>
<blockquote cite="http://www.w3.org/History/19921103-hypertext/hypertext/WWW/MarkUp/Tags.html"><p>It is suggested that the first heading be one suitable for a reader who is already browsing in related information, in contrast to the title tag which should identify the node in a wider context.</p></blockquote>
<p><a title="HTML Markup Tags" href="http://www.w3.org/History/19921103-hypertext/hypertext/WWW/MarkUp/Tags.html" target="_blank">http://www.w3.org/History/19921103-hypertext/hypertext/WWW/MarkUp/Tags.html</a></p>
<h2>The Answer is?</h2>
<p>I don’t think there will ever be a definitive answer, and I agree with the comments that sites should be judged on a case-by-case basis. I think this quote sums it up:</p>
<blockquote><p>The H1 element defines a level-one heading. A document generally should have exactly one H1 element to mark the most important heading.</p></blockquote>
<p>What the ‘most important heading’ is depends entirely on the website.</p>
<p>Please do keep tagging your tweets with #h1logo and #h1title because even if your vote has been counted, your views will still appear on the website. Thanks to the thousands of you who have already visited The H1 Debate, and for leaving us with all your comments on this subject.</p>
]]></content:encoded>
			<wfw:commentRss>https://paulrandall.com/2009/02/06/the-h1-debate/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Design Work on FootyTweets</title>
		<link>https://paulrandall.com/2009/01/12/design-work-on-footytweets/</link>
		<comments>https://paulrandall.com/2009/01/12/design-work-on-footytweets/#comments</comments>
		<pubDate>Mon, 12 Jan 2009 21:11:41 +0000</pubDate>
		<dc:creator><![CDATA[Paul]]></dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[960]]></category>
		<category><![CDATA[footytweets]]></category>

		<guid isPermaLink="false">http://prandall.com/?p=12</guid>
		<description><![CDATA[A site I have recently done some design work on has been launched by Ollie Parsley this week. FootyTweets allow you to follow your favourite football team and get tweets of news and goal updates as they happen. Ollie has also been working on a Rugby and Cricket version and I think there are plans [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>A site I have recently done some design work on has been launched by Ollie Parsley this week. <a title="Footy Tweets" href="http://footytweets.com" target="_blank">FootyTweets</a> allow you to follow your favourite football team and get tweets of news and goal updates as they happen.</p>
<p>Ollie has also been working on a Rugby and Cricket version and I think there are plans for a Motorsport version too.</p>
<p>I thought the project was a really good idea, and so volunteered my services to produce a quick PhotoShop mockup and XHTML design, from which Ollie could base the sites on. I initially based the site around a 12 column grid design, with each team crest taking up column and used a template from the extremely useful <a title="960 Grid Template" href="http://960.gs" target="_blank">960.gs</a> site.</p>
<p><img class="size-full wp-image-13 alignnone" title="footy-tweets-small" src="https://paulrandall.com/wp-content/uploads/2009/01/footy-tweets-small.jpg" alt="footy tweets grid design" width="420" height="285" /></p>
<p><span id="more-12"></span>I used the CSS3 border-radius property in this project, and with this, you can create rounded corners without the need for additional divs, images or JavaScript. I would be cautious of using this on a client’s site, but I thought that a site like this could benefit from a little bit of progressive enhancement. For browsers which don’t support this property, the div just shows square edges.</p>
<p>To use the same effect, just add this code to the div:</p>
<pre>-moz-border-radius: 20px;
-webkit-border-radius: 20px;
border-radius: 20px;</pre>
<p>The site design had to be flexible enough to work for multiple sports: football, rugby and cricket, and with the future plans of motorsports too, the design had to be versatile enough to work for all of these. So the design was left simple to edit, with a repeatable background and a feature image which is controlled by another CSS file.</p>
]]></content:encoded>
			<wfw:commentRss>https://paulrandall.com/2009/01/12/design-work-on-footytweets/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>
