<?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>DivitoDesign &#187; Accesibility</title>
	<atom:link href="http://divitodesign.com/tag/accesibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://divitodesign.com</link>
	<description>Articles, Tutorials and Resources for the Webdesigner</description>
	<lastBuildDate>Mon, 08 Mar 2010 14:24:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Format accessible forms using CSS</title>
		<link>http://divitodesign.com/css/format-accessible-forms-using-css/</link>
		<comments>http://divitodesign.com/css/format-accessible-forms-using-css/#comments</comments>
		<pubDate>Thu, 10 Jul 2008 00:00:12 +0000</pubDate>
		<dc:creator>Stefan Vervoort</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[Accesibility]]></category>

		<guid isPermaLink="false">http://www.divitodesign.com/?p=133</guid>
		<description><![CDATA[<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdivitodesign.com%2Fcss%2Fformat-accessible-forms-using-css%2F"><br />
				<br />
			</a>
		
<p><a href="/dd-articles/accessible-form/example.html"></a></p>
<p>In this CSS tutorial we will look deeper inside the building of a form. You see forms everywhere on the web and they are most often used to gather information about the visitors.... &#187;</p>]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdivitodesign.com%2Fcss%2Fformat-accessible-forms-using-css%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdivitodesign.com%2Fcss%2Fformat-accessible-forms-using-css%2F&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p><a href="/dd-articles/accessible-form/example.html"><img src="http://www.divitodesign.com/wp-content/uploads/2008/07/screen.jpg" alt="Accessible Forms" /></a></p>
<p>In this CSS tutorial we will look deeper inside the building of a form. You see forms everywhere on the web and they are most often used to gather information about the visitors. The examples are everywhere: contact forms, polls, surveys, search forms.</p>
<p>There are a couple ways to produce a proper formatted form. A couple years back, I did the formatting with tables, because I simply didn&#8217;t hear from CSS (it was there, but not as popular as it is now!). It worked alright, but in today&#8217;s web-world you should better use CSS to do all your formatting.</p>
<p>Today, we will create a fully accessible, proper formatted form. This form should be accessible for almost everyone.<br />
<span id="more-133"></span></p>
<h2>The beginning</h2>
<p>We&#8217;ll start with the structure of the form. Take a look below:</p>
<h3>HTML</h3>
<pre class="html">
<span class="htmlFormTag">&lt;form id=<span class="htmlAttributeValue">&quot;info&quot;</span> method=<span class="htmlAttributeValue">&quot;post&quot;</span>&gt;</span> <span class="htmlOtherTag">&lt;fieldset&gt;</span>
<span class="htmlOtherTag">&lt;legend&gt;</span>General Information<span class="htmlOtherTag">&lt;/legend&gt;</span>
<span class="htmlOtherTag">&lt;ul&gt;</span>
	<span class="htmlOtherTag">&lt;li&gt;</span> <span class="htmlOtherTag">&lt;label title=<span class="htmlAttributeValue">&quot;Name&quot;</span> for=<span class="htmlAttributeValue">&quot;name&quot;</span>&gt;</span>Name <span class="htmlOtherTag">&lt;span&gt;</span>*<span class="htmlOtherTag">&lt;/span&gt;</span><span class="htmlOtherTag">&lt;/label&gt;</span> <span class="htmlFormTag">&lt;input id=<span class="htmlAttributeValue">&quot;name&quot;</span> name=<span class="htmlAttributeValue">&quot;name&quot;</span> type=<span class="htmlAttributeValue">&quot;text&quot;</span> /&gt;</span><span class="htmlOtherTag">&lt;/li&gt;</span>
	<span class="htmlOtherTag">&lt;li&gt;</span> <span class="htmlOtherTag">&lt;label title=<span class="htmlAttributeValue">&quot;Email&quot;</span> for=<span class="htmlAttributeValue">&quot;email&quot;</span>&gt;</span>Email <span class="htmlOtherTag">&lt;span&gt;</span>*<span class="htmlOtherTag">&lt;/span&gt;</span><span class="htmlOtherTag">&lt;/label&gt;</span> <span class="htmlFormTag">&lt;input id=<span class="htmlAttributeValue">&quot;email&quot;</span> name=<span class="htmlAttributeValue">&quot;email&quot;</span> type=<span class="htmlAttributeValue">&quot;text&quot;</span> /&gt;</span><span class="htmlOtherTag">&lt;/li&gt;</span>
	<span class="htmlOtherTag">&lt;li&gt;</span> <span class="htmlOtherTag">&lt;label title=<span class="htmlAttributeValue">&quot;Address&quot;</span> for=<span class="htmlAttributeValue">&quot;address&quot;</span>&gt;</span>Address <span class="htmlOtherTag">&lt;/label&gt;</span> <span class="htmlFormTag">&lt;input id=<span class="htmlAttributeValue">&quot;address&quot;</span> name=<span class="htmlAttributeValue">&quot;address&quot;</span> type=<span class="htmlAttributeValue">&quot;text&quot;</span> /&gt;</span><span class="htmlOtherTag">&lt;/li&gt;</span>
	<span class="htmlOtherTag">&lt;li&gt;</span> <span class="htmlOtherTag">&lt;label title=<span class="htmlAttributeValue">&quot;Postcode&quot;</span> for=<span class="htmlAttributeValue">&quot;postcode&quot;</span>&gt;</span>Postcode <span class="htmlOtherTag">&lt;/label&gt;</span> <span class="htmlFormTag">&lt;input id=<span class="htmlAttributeValue">&quot;postcode&quot;</span> name=<span class="htmlAttributeValue">&quot;postcode&quot;</span> type=<span class="htmlAttributeValue">&quot;text&quot;</span> /&gt;</span><span class="htmlOtherTag">&lt;/li&gt;</span>
	<span class="htmlOtherTag">&lt;li&gt;</span> <span class="htmlOtherTag">&lt;label title=<span class="htmlAttributeValue">&quot;Comments&quot;</span> for=<span class="htmlAttributeValue">&quot;comments&quot;</span>&gt;</span>Further Comments <span class="htmlOtherTag">&lt;/label&gt;</span> <span class="htmlFormTag">&lt;textarea id=<span class="htmlAttributeValue">&quot;comments&quot;</span> name=<span class="htmlAttributeValue">&quot;comments&quot;</span>&gt;</span><span class="htmlFormTag">&lt;/textarea&gt;</span><span class="htmlOtherTag">&lt;/li&gt;</span>
<span class="htmlOtherTag">&lt;/ul&gt;</span>
<span class="htmlOtherTag">&lt;/fieldset&gt;</span>
<span class="htmlOtherTag">&lt;fieldset&gt;</span>
<span class="htmlFormTag">&lt;input id=<span class="htmlAttributeValue">&quot;Submit&quot;</span> name=<span class="htmlAttributeValue">&quot;Submit&quot;</span> type=<span class="htmlAttributeValue">&quot;submit&quot;</span> value=<span class="htmlAttributeValue">&quot;Submit&quot;</span> /&gt;</span>
<span class="htmlFormTag">&lt;input id=<span class="htmlAttributeValue">&quot;Reset&quot;</span> name=<span class="htmlAttributeValue">&quot;Reset&quot;</span> type=<span class="htmlAttributeValue">&quot;reset&quot;</span> value=<span class="htmlAttributeValue">&quot;Reset&quot;</span> /&gt;</span>
<span class="htmlOtherTag">&lt;/fieldset&gt;</span>
<span class="htmlFormTag">&lt;/form&gt;</span></pre>
<h2>HTML Explanation</h2>
<p>The <em>fieldset</em> element is there to divide our complete form in different parts. Say a &#8220;General Information&#8221; part, a &#8220;Specific information&#8221; part etc. We give a name to that fieldset by adding a <em>legend</em> element to it. You&#8217;ll see what that will give in a <a href="/dd-articles/accessible-form/example1.html">working example</a>.</p>
<h3>&lt;ul&gt; and &lt;li&gt;</h3>
<p>We are moving on; In the next codes, you&#8217;ll see the <em>ul</em> and <em>li</em> elements. This is an un-ordered list and is used to style all the question/answers in the same way. We &#8220;order&#8221; the questions and answer fields using a list.</p>
<h3>Inside the &lt;li&gt; element</h3>
<p>You will see that inside the <em>li</em> element a <em>label</em>, a <em>span</em> and <em>input</em> element are placed. The <em>label</em> element is there to connect the question to the answer field. When you click on the question your focus moves right to the answer field. The <em>title</em> is there to give your visitors more accessibility options.</p>
<h3>Asterix</h3>
<p>I&#8217;ve placed the asterix sign inside the <em>span</em> element to indicate which fields are required. The <em>input</em> element is the field where your visitor should answer your question. Nothing hard about that I guess.</p>
<p>As you might notice, I didn&#8217;t use any <em>div</em> elements in the structure. We don&#8217;t need them, as we are able to style our form using these basic codes.</p>
<h2>Let&#8217;s format</h2>
<p>If you understand the structure of our form, I will start explaining the formatting via CSS, if not, read the whole article again. Let&#8217;s go.</p>
<h3>CSS</h3>
<pre class="css">
<span class="cssSelector">ul{</span>
<span class="cssProperty">list-style</span><span class="cssRest">:</span><span class="cssValue">none</span><span class="cssRest">;</span>
<span class="cssProperty">margin-top</span><span class="cssRest">:</span><span class="cssValue">5px</span><span class="cssRest">;</span><span class="cssSelector">}</span>
<span class="cssSelector">ul li{</span>
<span class="cssProperty">display</span><span class="cssRest">:</span><span class="cssValue">block</span><span class="cssRest">;</span>
<span class="cssProperty">float</span><span class="cssRest">:</span><span class="cssValue">left</span><span class="cssRest">;</span>
<span class="cssProperty">width</span><span class="cssRest">:</span><span class="cssValue">100%</span><span class="cssRest">;</span>
<span class="cssProperty">height</span><span class="cssRest">:</span><span class="cssValue">1%</span><span class="cssRest">;</span><span class="cssSelector">}</span>
<span class="cssSelector">ul li label{</span>
<span class="cssProperty">float</span><span class="cssRest">:</span><span class="cssValue">left</span><span class="cssRest">;</span>
<span class="cssProperty">padding</span><span class="cssRest">:</span><span class="cssValue">7px</span><span class="cssRest">;</span><span class="cssSelector">}</span>
<span class="cssSelector">ul li input, ul li textarea{</span>
<span class="cssProperty">float</span><span class="cssRest">:</span><span class="cssValue">right</span><span class="cssRest">;</span>
<span class="cssProperty">margin-right</span><span class="cssRest">:</span><span class="cssValue">10px</span><span class="cssRest">;</span>
<span class="cssProperty">border</span><span class="cssRest">:</span><span class="cssValue">1px solid #ccc</span><span class="cssRest">;</span>
<span class="cssProperty">padding</span><span class="cssRest">:</span><span class="cssValue">3px</span><span class="cssRest">;</span>
<span class="cssProperty">font-family</span><span class="cssRest">:</span><span class="cssValue"> Georgia, Times New Roman, Times, serif</span><span class="cssRest">;</span>
<span class="cssProperty">width</span><span class="cssRest">:</span><span class="cssValue">60%</span><span class="cssRest">;</span><span class="cssSelector">}</span>
<span class="cssSelector">li input:focus, li textarea:focus{</span>
<span class="cssProperty">border</span><span class="cssRest">:</span><span class="cssValue">1px solid #666</span><span class="cssRest">;</span> <span class="cssSelector">}</span>
<span class="cssSelector">fieldset{</span>
<span class="cssProperty">padding</span><span class="cssRest">:</span><span class="cssValue">10px</span><span class="cssRest">;</span>
<span class="cssProperty">border</span><span class="cssRest">:</span><span class="cssValue">1px solid #ccc</span><span class="cssRest">;</span>
<span class="cssProperty">width</span><span class="cssRest">:</span><span class="cssValue">360px</span><span class="cssRest">;</span>
<span class="cssProperty">overflow</span><span class="cssRest">:</span><span class="cssValue">auto</span><span class="cssRest">;</span>
<span class="cssProperty">margin</span><span class="cssRest">:</span><span class="cssValue">10px</span><span class="cssRest">;</span><span class="cssSelector">}</span>
<span class="cssSelector">legend{</span>
<span class="cssProperty">color</span><span class="cssRest">:</span><span class="cssValue">#444</span><span class="cssRest">;</span>
<span class="cssProperty">margin</span><span class="cssRest">:</span><span class="cssValue">0 10px 0 0</span><span class="cssRest">;</span>
<span class="cssProperty">padding</span><span class="cssRest">:</span><span class="cssValue">0 5px</span><span class="cssRest">;</span>
<span class="cssProperty">font-size</span><span class="cssRest">:</span><span class="cssValue">100%</span><span class="cssRest">;</span> <span class="cssSelector">}</span>
<span class="cssSelector">label span{</span>
<span class="cssProperty">color</span><span class="cssRest">:</span><span class="cssValue">#f00</span><span class="cssRest">;</span>  <span class="cssSelector">}</span>
<span class="cssSelector">fieldset input#Reset, fieldset input#Submit{</span>
<span class="cssProperty">background</span><span class="cssRest">:</span><span class="cssValue">#E5E5E5</span><span class="cssRest">;</span>
<span class="cssProperty">color</span><span class="cssRest">:</span><span class="cssValue">f00</span><span class="cssRest">;</span>
<span class="cssProperty">border</span><span class="cssRest">:</span><span class="cssValue">1px solid #ccc</span><span class="cssRest">;</span>
<span class="cssProperty">padding</span><span class="cssRest">:</span><span class="cssValue">5px</span><span class="cssRest">;</span><span class="cssSelector">}</span>
</pre>
<h2>CSS Explanation</h2>
<p>I will explain some of the codes that might be hard to understand to the beginning CSS designer. <em>ul li input:focus</em> makes the form for non-Internet Explorer- users more accessibile. <a href="http://www.divitodesign.com/2008/06/usability-upgrade-for-forms-with-focus-selector/">Read more about this in the following article</a>.</p>
<p>The <em>fieldset input#Reset, fieldset input#Submit</em> style declarations are there to style the Submit and Reset button. They need a proper look as well, right?</p>
<p>I think the rest is quite understandable. If not, please leave a comment or email me.</p>
<h2>There you are</h2>
<p>And there is your <a href="/dd-articles/accessible-form/example.html">nice looking, accessible CSS based form</a>. This tutorial form is there to learn you the basics of an <strong>Accessible</strong> CSS based form, and it is up to you to think of the thousands of variants that are waiting to be designed! Good luck with experimenting your way to the top.</p>
]]></content:encoded>
			<wfw:commentRss>http://divitodesign.com/css/format-accessible-forms-using-css/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HTML &#8211; ABBR Property to Explain Abbreviations</title>
		<link>http://divitodesign.com/html/html-abbr-property-to-explain-abbreviations/</link>
		<comments>http://divitodesign.com/html/html-abbr-property-to-explain-abbreviations/#comments</comments>
		<pubDate>Sun, 01 Jun 2008 16:42:44 +0000</pubDate>
		<dc:creator>Stefan Vervoort</dc:creator>
				<category><![CDATA[HTML]]></category>
		<category><![CDATA[Accesibility]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Search Engine Optimizing]]></category>

		<guid isPermaLink="false">http://www.divitodesign.com/?p=106</guid>
		<description><![CDATA[<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdivitodesign.com%2Fhtml%2Fhtml-abbr-property-to-explain-abbreviations%2F"><br />
				<br />
			</a>
		
<p>HTML has many properties. There are a couple of them we don&#8217;t use that often and we will discuss one today. It is called the ABBR property and is used to explain and mark-up... &#187;</p>]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdivitodesign.com%2Fhtml%2Fhtml-abbr-property-to-explain-abbreviations%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdivitodesign.com%2Fhtml%2Fhtml-abbr-property-to-explain-abbreviations%2F&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p>HTML has many properties. There are a couple of them we don&#8217;t use that often and we will discuss one today. It is called the ABBR property and is used to explain and mark-up abbreviations. We bloggers write for the web and we shouldn&#8217;t forget the text should be understandable for everyone.</p>
<p>You might have seen news sites and information websites use this property. In the text, an abbreviation is underlined with a little gray and dashed line. When your mouse rolls over that link-look-alike, you come to the conclusion it is something else. An explanation about the abbreviation shows up. You might have seen this property more than you think. </p>
<p>Ok. But what is the point of using ABBR in your website? These arguments should convince you:</p>
<p><strong>1. Better for Accessibility</strong> &#8211; Using ABBR properties in your website will only optimize the accessibility of your website. Some visitors might don’t know terms like &#8220;SQL&#8221;, &#8220;AI&#8221; or &#8220;NASA&#8221;. Look at yourself, do you know them all? You should try as hard as possible to make your content as accessible as possible. </p>
<p><strong>2. Educate your visitors</strong> &#8211; Many websites and blogs are here to teach people with their knowledge. Those have different subjects and different visitors. When they are reading an article, everything should be clear about the topic. When acronyms or abbreviations aren&#8217;t clear enough, the visitor might do not understand the whole article.<br />
<span id="more-106"></span><br />
<strong>3. Multiple purposes</strong> &#8211; Not only are you educating your visitors, you will make it easier for spell checkers, translators and speech synthesizers to understand the meaning of an abbreviation and therefore the meaning of a sentence. </p>
<p><strong>4. Search engine optimizing</strong> &#8211; Another advantage is the search engine (yes, they are everywhere!). When you are using an abbreviation instead of a couple keywords, the <abbr title="Search Engine">SE</abbr> isn&#8217;t totally clear what you mean and therefore they couldn&#8217;t display the most accurate data to their users. </p>
<p>When you are using the ABBR function in HTML, it will explain the abbreviation to the search engine as well and you have yourself an extra keyword. Always great, right?</p>
<h2>How to use ABBR?</h2>
<p>ABBR is not hard to use. It only uses the &#8220;title&#8221; tag to explain the abbreviation. As always, CSS is around the corner to style your ABBR tag in a way you prefer.</p>
<pre class="html"><span class="htmlOtherTag">&lt;abbr title=<span class="htmlAttributeValue">&quot;Structured Query Language&quot;</span>&gt;</span>SQL<span class="htmlOtherTag">&lt;/abbr&gt;</span></pre>
<p>When you add ABBR to an other &#8220;SQL&#8221; abbreviation elsewhere in the page, <abbr></abbr> around it is everything you need to do.</p>
<h2>When ABBR, and when Acronym?</h2>
<p>Some abbreviations like &#8220;URL&#8221; and &#8220;SQL&#8221; are pronounced letter by letter by some, and as a normal word by others. The ABBR property should be used in these cases. Other abbreviations are just normal &#8216;words&#8217; like &#8220;NAVO&#8221; or &#8220;ASAP&#8221;. Those should be surrounded by the acronym property.</p>
<pre class="html"><span class="htmlOtherTag">&lt;abbr title=<span class="htmlAttributeValue">&quot;Structured Query Language&quot;</span>&gt;</span>SQL<span class="htmlOtherTag">&lt;/abbr&gt;</span>
<span class="htmlOtherTag">&lt;acronym title=<span class="htmlAttributeValue">&quot;Naval Oceanographic Office&quot;</span>&gt;</span>NAVO<span class="htmlOtherTag">&lt;/acronym&gt;</span></pre>
<h2>Disadvantages?</h2>
<p>Everything has its disadvantages. The use on a blog or website has a major problem. Internet Explorer will not play along as it simply doesn&#8217;t recognize the property. </p>
<p>But there is a solution for Internet Explorer. We can add something extra HTML to the original codes:</p>
<pre class="html"><span class="htmlOtherTag">&lt;abbr title=<span class="htmlAttributeValue">&quot;Structured Query Language&quot;</span>&gt;</span><span class="htmlOtherTag">&lt;span class=<span class="htmlAttributeValue">&quot;abbr&quot;</span> title=<span class="htmlAttributeValue">&quot;Structured Query Language&quot;</span>&gt;</span>SQL<span class="htmlOtherTag">&lt;/span&gt;</span><span class="htmlOtherTag">&lt;/abbr&gt;</span></pre>
<p>In Internet Explorer, ABBR isn&#8217;t recognized and therefore not styled. The extra span is there to get this done in another way. Below are the style declarations you should use if you want your visitors to think they are dealing with the original ABBR property:</p>
<pre class="css">
<span class="cssSelector">abbr, acronym, .abbr {</span>
  <span class="cssProperty">cursor</span><span class="cssRest">:</span><span class="cssValue"> help</span><span class="cssRest">;</span>
  <span class="cssProperty">border-bottom</span><span class="cssRest">:</span><span class="cssValue"> 1px dashed #ccc</span><span class="cssRest">;</span>
<span class="cssSelector">}</span>
</pre>
<h2>Conclusion</h2>
<p>Internet Explorer is always bugging a webdesigner. All we can do is waiting until all IE users switch to a better browser. This is hard to achieve and in the meantime&#8230; We have to live with it. </p>
<p>I think the advantages of this property really are great, and the Internet Explorer problem is not that big. Thanks for your time.</p>
]]></content:encoded>
			<wfw:commentRss>http://divitodesign.com/html/html-abbr-property-to-explain-abbreviations/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Accessibility Tips For Fonts</title>
		<link>http://divitodesign.com/accesibility/accessibility-tips-for-fonts/</link>
		<comments>http://divitodesign.com/accesibility/accessibility-tips-for-fonts/#comments</comments>
		<pubDate>Wed, 21 May 2008 17:43:48 +0000</pubDate>
		<dc:creator>Stefan Vervoort</dc:creator>
				<category><![CDATA[Accesibility]]></category>
		<category><![CDATA[CSS]]></category>

		<guid isPermaLink="false">http://www.divitodesign.com/?p=99</guid>
		<description><![CDATA[<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdivitodesign.com%2Faccesibility%2Faccessibility-tips-for-fonts%2F"><br />
				<br />
			</a>
		
<p></p>
<p><em>Fonts</em> is a though subject when we are talking about <a href="http://www.divitodesign.com/tag/accesibility/">accessibility</a>. Many of the webdesigners out there design and code their website in a way they like it. They use a header... &#187;</p>]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdivitodesign.com%2Faccesibility%2Faccessibility-tips-for-fonts%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdivitodesign.com%2Faccesibility%2Faccessibility-tips-for-fonts%2F&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p><img class="alignleft" style="float: left; margin:0 0 10px 0;" src="http://www.divitodesign.com/wp-content/uploads/2008/05/font-accessibility1.jpg" alt="" /></p>
<p><em>Fonts</em> is a though subject when we are talking about <a href="http://www.divitodesign.com/tag/accesibility/">accessibility</a>. Many of the webdesigners out there design and code their website in a way they like it. They use a header image they like and they use the <a href="http://www.divitodesign.com/tag/css/">font family</a> and font size they like. Sometimes (if not often?), they forget all machines and browsers are different and do not have the same settings.</p>
<p>This means the content of the website is not displayed to the visitors as the designer wanted. But how are we webdesigners supposed to use typography, if we don&#8217;t know how the text is displayed on other computers and browsers?</p>
<p>The tips I will give you in this article will improve your design. It’ll give you more control power over your content and typography. Ready?<span id="more-99"></span></p>
<h2>1. Use universal fonts</h2>
<p>Windows is not the same as a Mac machine and Windows &#8216;95 differs from Windows XP. They don’t have the same fonts installed by default. Fortunately, a couple fonts are installed on all those machines and we call them universal fonts. For example, fonts as <em>Arial</em>, <em>Times New Roman</em> and <em>Courier New</em> are included in the most systems around the world. It is safe and recommended to use these.</p>
<p>If you designed your content and you used different fonts and sizes on your website, we call it typography. But you shouldn’t experiment with fonts that you have downloaded from the internet because the visitors usually don’t have this font installed and therefore, they will only see the default font. If you are defining a downloaded font via CSS, you’d always add a couple standard fonts as a back-up. An example below:</p>
<pre class="css">
<span class="cssSelector">body {</span> <span class="cssProperty">font</span><span class="cssRest">:</span><span class="cssValue"> Times New Roman, Verdana, Arial, Helvetica, sans-serif</span><span class="cssRest">;</span> <span class="cssSelector">}</span>
</pre>
<h2>2. Font sizes</h2>
<p>Font families belong to typography. The same goes with their sizes: large headings, smaller paragraphs, and bolded links, to name a few. Unfortunately, most webdesigners don’t know how to use font sizes in proper way, and as a result, some visitors will get an accessibility problem. Learn on below.</p>
<p>According to <a href="http://www.alistapart.com/articles/howtosizetextincss/">Alistapart&#8217;s investigation and testing</a>, it isn&#8217;t safe to use pixels to define your font size. <em>Points</em> aren&#8217;t safe either. What about <em>Percents</em>? Or <em>Em</em>s? Ems are <a href="http://www.w3.org/WAI/GL/css2em.htm">recommended by the W3C</a>. And yes, Alistapart tells you the exact same thing, with a little extra tip to smooth things up. Look below:</p>
<pre class="css">
<span class="cssSelector">body {</span>   <span class="cssProperty">font-size</span><span class="cssRest">:</span><span class="cssValue"> 100%</span><span class="cssRest">;</span> <span class="cssSelector">}</span>
<span class="cssSelector">p {</span>      <span class="cssProperty">font-size</span><span class="cssRest">:</span><span class="cssValue">0.75em</span><span class="cssRest">;</span> <span class="cssSelector">}</span>
</pre>
<p>The style declarations I&#8217;ve shown above will do the job. The only thing you should add is the <em>font-size:100%;</em> to your body property and now you can use Ems to define your font size. With this codes, everything is perfectly readable and resizable in most (modern) browsers like IE6+ , Firefox and Opera.</p>
<h2>3. Use a correct line height</h2>
<p>A paragraph text should be easy to read. This can be achieved with solid, accessible font families and font sizes. A part most webdesigners often forget is the area between the lines (&#8220;<em>Line-height</em>&#8220;, as it is called in CSS). A paragraph is much easier to read when a proper line-height is defined.</p>
<p>Recently, Eric Meyer did some investigation regarding the behavior of line-height in CSS. He tried different fonts and he came to the conclusion a &#8220;normal&#8221; line-height doesn&#8217;t exists. It changes per font. We can define line-height in the same way as we styled our font-sizes a couple minutes back.</p>
<pre class="css">
<span class="cssSelector">body {</span>      <span class="cssProperty">font-size</span><span class="cssRest">:</span><span class="cssValue"> 100%</span><span class="cssRest">;</span>
            <span class="cssProperty">line-height</span><span class="cssRest">:</span><span class="cssValue">1.5em</span><span class="cssRest">;</span> <span class="cssSelector">}</span>
<span class="cssSelector">p {</span>         <span class="cssProperty">font-size</span><span class="cssRest">:</span><span class="cssValue">0.75em</span><span class="cssRest">;</span> <span class="cssSelector">}</span>
</pre>
<p>Again, the text is now fully resizable and accessible. Your paragraph is displayed correctly in most (modern) browsers.</p>
<h2>4. Website based font-size resizer</h2>
<p>With the latest JavaScript libraries around the web, it is possible to improve your website by adding a font-size resizer. It will make your website more accessible, as a lot of people didn&#8217;t look for resizer options in their browser. A resizer on your website makes things easier.</p>
<p>Even when people know their browser has a resize option, this website based resizer has its advantages. As developers, we could specify the area to resize. For example, the text of your article should get resized, without messing up the layout. My resizer does the same job, so it is possible!</p>
<p>The web offers many ways to build a resizer. <a href="http://www.white-hat-web-design.co.uk/articles/js-fontsize.php">Here is the one I use myself</a>. It works correctly.</p>
<h2>5. Checking your website.</h2>
<p>If you are in your office or at school, check your own website on the available computers. Most of the time, you only see your website from your own, development computer and most likely, you have changed some settings. Your website might look good on your computer, but maybe not on another one.</p>
<p>You are not your only visitor (I hope!), and people are visiting your website from all over the world. Check your website statistics and see with which browsers users are visiting. If 30% uses Firefox 2.0, be sure you browse your site in Firefox 2.0. Do the same thing with the other browsers.</p>
<p>It is always good to test your website. You become a visitor of your website yourself and you see what others are noticing. This knowledge can only help you improve your website.</p>
<h2>Conclusion</h2>
<p>Accessibility is important and you have all the information you need about accessibility and fonts. These are the tips I think, are the most valuable, but if you think an important one is missing, please contact me. This will only make this article more up-to-date and helpful.</p>
<p>If you think this article was useful, consider <a href="http://feeds.feedburner.com/DivitoDesign">subscribing to my RSS feed</a> to get the latest articles as soon as they will be available.</p>
<p>Thanks for reading and if you have a question, please do <a href="contact/">contact</a> me. Comments, emails or IM messages are appreciated. As always.</p>
]]></content:encoded>
			<wfw:commentRss>http://divitodesign.com/accesibility/accessibility-tips-for-fonts/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Make Your Blog More User-Friendly</title>
		<link>http://divitodesign.com/accesibility/tips-to-make-your-weblog-more-user-friendly/</link>
		<comments>http://divitodesign.com/accesibility/tips-to-make-your-weblog-more-user-friendly/#comments</comments>
		<pubDate>Sat, 23 Feb 2008 13:24:01 +0000</pubDate>
		<dc:creator>Stefan Vervoort</dc:creator>
				<category><![CDATA[Accesibility]]></category>
		<category><![CDATA[Blogging]]></category>
		<category><![CDATA[Search Engine Optimizing]]></category>

		<guid isPermaLink="false">http://www.divitodesign.com/2008/02/tips-to-make-your-weblog-more-user-friendly/</guid>
		<description><![CDATA[<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdivitodesign.com%2Faccesibility%2Ftips-to-make-your-weblog-more-user-friendly%2F"><br />
				<br />
			</a>
		
<p>Every blog should provide their visitors with the most pleasant experience. Content is the most important part of a blog, as this is where visitors are coming for. Without this content a blog will... &#187;</p>]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdivitodesign.com%2Faccesibility%2Ftips-to-make-your-weblog-more-user-friendly%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdivitodesign.com%2Faccesibility%2Ftips-to-make-your-weblog-more-user-friendly%2F&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p>Every blog should provide their visitors with the most pleasant experience. Content is the most important part of a blog, as this is where visitors are coming for. Without this content a blog will never become a success. How this content is displayed and how easy it is to navigate that blog plays a serious part at keeping visitors. A user-friendly theme in combination with great content will give your readers trust and interest, which will most likely bring them back for more.</p>
<p>As mentioned, a blog design should be designed for its users. You could ask for the user&#8217;s needs before starting the developing process, to find out what they are looking for in your blog. You&#8217;ll come out better: User-friendly and at the same time, it is a pleasure for the eye.</p>
<p>This article describes what users are looking for and how you can improve your design and more important your blog (and your visitor base).<br />
<span id="more-50"></span></p>
<h2>1. Accessibility</h2>
<p>Important part. Not all visitors use the same device, computer, browser, and/or settings. Maybe, your weblog is not visualized the way you or your designer wanted to. Some users might have disabled images or JavaScript, some might have a 800&#215;600 resolution. You should prepare for this, make sure they can read the content and view the site as good as possible. Remember, you are publishing for all users and it should be your goal to let everyone read your content. <a title="Accesibilty Tips" href="http://www.divitodesign.com/2007/10/6-accessibility-tips/">Read more accessibility tips.</a></p>
<h2>2. Organize your page</h2>
<p>When a user lets his eyes go over a page, he should see the important things first. Users are looking for content. Make sure they see content. The most blog readers start looking for the navigation, the RSS feed link or button, your categories or a search form. To make your weblog as organized and user-friendly as possible, make sure those items are in sight.</p>
<h2>3. Information</h2>
<p>Your visitors do visit your weblog for a reason. This reason can vary: one weblog has some great articles on webdesign, others on music and another on Prison Break. Your task is to place all the content you feel your visitors need right in front of their eyes. They&#8217;ll find the content they need fast and they are satisfied. Again, content is the most important part of a blog, so make sure you have it.</p>
<h2>4. Advertisements</h2>
<p>Watch out for advertisements. It is nice to make some money of your blog, but make sure you don&#8217;t cram your content full of advertisements. Users aren&#8217;t coming for the ads, they are coming for your content. If you want people to advertise, organize the ads and spread them over your whole page. In my opinion, you should leave the content as readable as possible. A weblog (ea. my weblog) lives from its visitors and if you press to many advertisements to their chest they might leave and never come back.</p>
<h2>5. Cluttering</h2>
<p>Users scan a page, but they also scan an article for useful information. A proper use of <strong>bold</strong> texts, images and headings will separate the article in information blocks and makes sure the readers pay attention to the most important information and/or keywords of the article.</p>
<h2>Some smaller points</h2>
<p><strong>6. Navigation</strong> &#8211; Users want to move around a weblog the way they like. They need info, so make sure you ordered your content under the right navigation items to let your users find information fast.<br />
<strong>7. Loading time</strong> &#8211; Not everyone is on a very fast cable connection. Optimize your design to load fast with every connection. Users navigate away when it takes to long.<br />
<strong>8. Sitemap</strong> &#8211; A sitemap is especially with larger blogs, a must-have. With one click, your visitor can view all information on your blog. <a title="Search Engine Optimizing Guide" href="http://www.divitodesign.com/2007/07/update-you-pages-the-seo-friendly-way/">This is seach engine friendly</a>.<br />
<strong>9. Page title</strong> &#8211; Use a page title which describes the content the page is loaded with. An example: &#8220;How can you make your blog user-friendly &#8211; Divitodesign.com&#8221;. There&#8217;s a smart <a href="http://WordPress.org/extend/plugins/optimal-title">plugin</a> available to do this for you.</p>
<h2>Interested in more?</h2>
<p>I hope you enjoyed this post and learned something. You could subscribe to my <a href="http://feeds.feedburner.com/DivitoDesign">RSS reader and read articles</a> as soon as I post them!</p>
]]></content:encoded>
			<wfw:commentRss>http://divitodesign.com/accesibility/tips-to-make-your-weblog-more-user-friendly/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>6 Accessibility Tips</title>
		<link>http://divitodesign.com/accesibility/6-accessibility-tips/</link>
		<comments>http://divitodesign.com/accesibility/6-accessibility-tips/#comments</comments>
		<pubDate>Thu, 11 Oct 2007 09:59:56 +0000</pubDate>
		<dc:creator>Stefan Vervoort</dc:creator>
				<category><![CDATA[Accesibility]]></category>

		<guid isPermaLink="false">http://www.divitodesign.com/blog/2007/10/6-accessibility-tips/</guid>
		<description><![CDATA[<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdivitodesign.com%2Faccesibility%2F6-accessibility-tips%2F"><br />
				<br />
			</a>
		
<p>What is accessibility? What we are talking about is the accessibility of a website. Can your website be viewed by people using other mediums? Or can it be used by deaf people? A common... &#187;</p>]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdivitodesign.com%2Faccesibility%2F6-accessibility-tips%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdivitodesign.com%2Faccesibility%2F6-accessibility-tips%2F&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p>What is accessibility? What we are talking about is the accessibility of a website. Can your website be viewed by people using other mediums? Or can it be used by deaf people? A common mistake people make is that accessibility is something for people with a handicap. Dont think that way; Accessibility is for ALL your website users. One guy might be deaf, the other one might has a small screen resolution, and another guy might not want to load images. All those people should see a normal website with good understandable content.<br />
<span id="more-21"></span></p>
<h2>Validation</h2>
<p>As always, validate your website. Validation is an important part of developing your website. There could be a small error in your HTML or CSS, and your testing browsers render it the good way. But what happens when an older browser doesn&#8217;t render it correct, or render it at all? Visitors with that older browser might not see all the content and/or miss some parts. Therefore, always try your website in different browsers and versions and most importantly, validate your HTML and CSS.</p>
<h2>Different mediums</h2>
<p>Not all people are visiting your website on the standard computer, with the standard browser. There are also people visiting via a cell phone, while many browsers can be using different settings, as well as versions and screen resolutions. Is there a way to develop your website for all those different types?  No, you can&#8217;t. The only thing you can do is check your website in all different types of mediums and look if there is something you can do about a possible display error. Keep this in mind.</p>
<h2>Images</h2>
<p>Remember, there are people who are on a dial connection. Those visitors have to wait a long time before a website loads. In order to make a webpage load faster, they often browse the internet without images. On the spot the image would have been located their browser displays the &#8216;ALT&#8217; text. Therefore, adding an &#8216;ALT&#8217; text is a MUST for making your page more accessible.</p>
<p>Some images are located in the content. When an image doesn&#8217;t load, the alt text is displayed inside the content. Visitors might read over it and don&#8217;t see there is an image located. Make it noticeable. Try something like this: &#8216; &#8212; CSS MENU EXAMPLE &#8211; -&#8217;. This will not tell people you are using an image, but it&#8217;ll get noticed much more and faster. Alt texts are also good for an extra keyword for onsite search engine optimizing.</p>
<p>Watch out for background images as well. When not loading images, the text could get lost in the background because there isn&#8217;t a proper contrast. Those people should be able to read the content too. Make sure your font color is readable when the images are turned off. A good way to check this is to try it yourself in your own browser.</p>
<h2>Colors</h2>
<p>Some older browsers don&#8217;t recognize color &#8216;names&#8217;. Example, &#8216;green&#8217; won&#8217;t be displayed the way it should in some very old browsers. They usually use the standard value if they don&#8217;t recognize what to do with the entered value. A way to have more browsers render the colors you have chosen, use the color&#8217;s prefix. 99.9% if not 100% of the browsers render prefixes the correct way.</p>
<h2>The &#8216;FONT&#8217; element</h2>
<p>Some time ago, I read an article on accessibility, and they told me something I didn&#8217;t know about the &#8216;FONT&#8217; element. In a lot of browsers, it is possible to change the standard used font, font color and background color. When using the following codes on your website, it is possible the browser will use this color. The user defined its own colors, but they won&#8217;t be used there. The background color doesn&#8217;t change and this might cause problems with readability of the content.</p>
<h2>Javascript</h2>
<p>When using Javascript, remember there are people who have it turned off. Those people should still be able to use your page the way it should. Always try to avoid Javascript in important parts of your website like navigation. If you are going to use it, use it in a proper way and make sure people can use the important parts.</p>
<h2>That&#8217;s it</h2>
<p>As I told you before, it isn&#8217;t possible to make your website 100% accessible for all visitors out there. The only thing you could do is optimize your webpage the best possible way, by following some tips given today in this article.</p>
<p>If you want more information on this subject, I suggest you should take a look at the &#8216;<a href="http://www.google.com/webmasters/guidelines.html">Webmaster Guidelines by Google</a>&#8216;. Google rewards Accessibility by better index and rank your pages. Another page you should visit is the &#8216;<a href="http://www.w3.org/TR/WAI-WEBCONTENT/">W3&#8217;s Accessibility guide</a>&#8216;, where you can get some more in-depth information together with a guide your website should comply to if you think accessibility is important.</p>
<p>Thanks for reading and see you next time!</p>
]]></content:encoded>
			<wfw:commentRss>http://divitodesign.com/accesibility/6-accessibility-tips/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>
