<?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>Premier Web Templates&#187; stylesheets</title>
	<atom:link href="http://premierwebtemplates.com/blog/tag/stylesheets/feed/" rel="self" type="application/rss+xml" />
	<link>http://premierwebtemplates.com/blog</link>
	<description>Web design tips and techniques for anyone who runs a web site or blog</description>
	<lastBuildDate>Wed, 10 Dec 2008 04:50:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
		<item>
		<title>Planning Your Stylesheet &#8211; The Definitive Guide</title>
		<link>http://premierwebtemplates.com/blog/css/planning-your-stylesheet-the-definitive-guide/</link>
		<comments>http://premierwebtemplates.com/blog/css/planning-your-stylesheet-the-definitive-guide/#comments</comments>
		<pubDate>Wed, 05 Nov 2008 08:06:07 +0000</pubDate>
		<dc:creator>Mark</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[stylesheets]]></category>

		<guid isPermaLink="false">http://premierwebtemplates.com/blog/?p=142</guid>
		<description><![CDATA[The more we rely upon CSS, the larger and more complex stylesheet files become. Planning and organising your stylesheet is essential to creating a lean, manageable website. There are many ways of organising CSS code but the following are best practice...]]></description>
			<content:encoded><![CDATA[<p>The more we rely upon CSS, the larger and more complex stylesheet files become. Planning and organising your stylesheet is essential to creating a lean, manageable website. There are many ways of organising CSS code but the following are best practice&#8230;<span id="more-142"></span></p>
<h4>Comment your stylesheet</h4>
<p>Commenting your stylesheet makes it much easier to find the information or the commands you&#8217;re looking for.</p>
<p>Meaningful comments include:</p>
<ul>
<li><strong>Last updated</strong> &#8211; This information can quickly let developers know about recent changes made to the file:<br />
<code>/* WEBCREDIBLE<br />
Updated: Thu 1 Jan 2008<br />
Author: John Doe<br />
Updates: Add new section 'Forum'<br />
––––––––––––––––––––––––––––––––––––––––––––––––*/</code></li>
<li><strong>References</strong> &#8211; Comments can also be used as a quick reference for the main style guides applied throughout the site:<br />
<code>/* COLORS<br />
Body Background: #FFFFFF;<br />
Main Text: #000000;<br />
Link: #F0F0F0;<br />
etc ...<br />
*/</code>
</li>
<li><strong>Organisation</strong> &#8211; Use comments to identify the different sections of the stylesheet:<br />
<code>/* =HEADER<br />
––––––––––––––––––––––––––––––––––––––––––––––––*/</code></p>
<p><code>/* =FOOTER<br />
––––––––––––––––––––––––––––––––––––––––––––––––*/</code>
</li>
<li> <strong>Reminders and notes</strong> &#8211; Leaving reminders and notes for yourself and other developers can help avoid confusion later:<br />
<code>/* The width is overwritten for IE 6 in: cssIE.css */<br />
    div {width: 150px;}</code>
</li>
</ul>
<h4>Define general rules and main classes at the top of the stylesheet</h4>
<p>Set the styles of generic HTML elements, for example:<br />
<code>body<br />
    {<br />
        background: #FFF;<br />
        font: Arial, sans-serif 75%;<br />
    }<br />
    h1 {<br />
        font-size: 1.2em;<br />
        color: #000;<br />
    }<br />
    h2 {<br />
        font-size: 1em;<br />
        color: #F0F0F0;<br />
    }<br />
    img {border: 0;}</code></p>
<p>Then, list the classes that will be most commonly used across the site, for example:<br />
<code>.hide<br />
    {<br />
        position: absolute;<br />
        left: -9000px;<br />
    }<br />
    .required {<br />
        background: url(#) no-repeat 100% 0;<br />
    }<br />
    .fl<br />
    {<br />
        float: left;<br />
    }<br />
    .fr<br />
    {<br />
        float: right;<br />
    }</code></p>
<h4>Order the CSS in the same order as the HTML</h4>
<p>The order of the HTML should be used to determine the order of the CSS sections. CSS files can sometimes be large and commands difficult to find. Having some correlation between the HTML and CSS file makes it easier to locate how an element is being styled.</p>
<h4>Know when to use elements, ids and classes</h4>
<p>Using the correct selector type means your CSS file can be significantly reduced in size:</p>
<ol>
<li><strong>Elements</strong> &#8211; Elements such as body, (&lt;body&gt;), paragraphs, (&lt;p&gt;) and headings, (&lt;h1&gt;,&lt;h2&gt; etc.) should be used to define general rules</li>
<li><strong>IDs</strong> &#8211; These are unique identifiers and should only be used once within a document. IDs should be used to style major structural sections of a web page such as the header or the footer.</li>
<li><strong>Classes</strong> &#8211; These can be used on any type of HTML element.</li>
</ol>
<p>Too many ids or classes can overload the HTML and the CSS files unnecessarily. Try and define as many rules as possible by referencing elements and/or ids by nesting the selectors.</p>
<p>Imagine the following HTML code:<br />
<code>&lt;ul id="nav"&gt;<br />
&lt;li&gt;&lt;a href="#"&gt;Item 1&lt;/a&gt;&lt;/li&gt;<br />
&lt;/ul&gt;</code></p>
<p>Because each of the list items has a common parent, descendant selectors can simplify the CSS markup as follow:</p>
<p><code>#nav { properties listed here }<br />
#nav li { properties listed here }<br />
#nav li a { properties listed here }</code></p>
<h4>Name classes and ids logically</h4>
<p>Don&#8217;t name classes and ids based on their color or position as these may change in time. Try and give them a name that&#8217;s likely to remain relevant over time. Also, use hyphens ahead of underscores as certain old browsers have a hard time understanding the latter.</p>
<p>Use a common naming system for your classes and ids. It will save a lot of time and confusion when developing, debugging and updating documents.</p>
<h4>Nest CSS selectors</h4>
<p>By nesting CSS selectors (i.e. using more than one CSS selector in one command) we can apply styles by navigating the HTML document tree. For example, to apply a colour of red to all paragraphs within a div, we can use the following rule:<br />
<code>div p {color: red;}</code></p>
<h4>Take advantage of inheritance</h4>
<p>Some CSS commands inherit from their parents whereas others don&#8217;t. The use of nesting means you don&#8217;t have to declare the same properties over and over again.</p>
<p>Generally speaking, text-related CSS commands (e.g. font-size, color) are inherited by descendant elements, whereas layout-related commands (e.g. float, width) aren&#8217;t inherited .</p>
<h4>Group selectors with common CSS declarations</h4>
<p>You can avoid specifying the same set of properties several times by grouping the selectors that share the same CSS declarations together. For example:<br />
<code>h1, h2, h3<br />
{<br />
color: black;<br />
padding: .2em;<br />
}</code></p>
<blockquote><p>This article was written by Brigitte Simard. Brigitte&#8217;s crazy about accessibility and CSS &#8211; so crazy that she works for Webcredible, an industry leading <a href="http://www.webcredible.co.uk/" target="_blank">user experience consultancy</a>, helping to make the Internet a better place for everyone. She spends much of her time working on the world&#8217;s <a href="http://www.webcredible.co.uk/services/accessible-cms.shtml" target="_blank">most accessible CMS</a> and is very good at <a href="http://www.webcredible.co.uk/services/css-training-fund.shtml" target="_blank">CSS training</a>.</p></blockquote>
Note: There is a rating embedded within this post, please visit this post to rate it.
]]></content:encoded>
			<wfw:commentRss>http://premierwebtemplates.com/blog/css/planning-your-stylesheet-the-definitive-guide/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>7 Tips To Make Your Website Super Accessible</title>
		<link>http://premierwebtemplates.com/blog/web-design-tips/7-tips-to-make-your-website-super-accessible/</link>
		<comments>http://premierwebtemplates.com/blog/web-design-tips/7-tips-to-make-your-website-super-accessible/#comments</comments>
		<pubDate>Wed, 01 Oct 2008 02:57:24 +0000</pubDate>
		<dc:creator>Mark</dc:creator>
				<category><![CDATA[Web Design Tips]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[alt tags]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[design practices]]></category>
		<category><![CDATA[screen readers]]></category>
		<category><![CDATA[stylesheets]]></category>
		<category><![CDATA[web design]]></category>

		<guid isPermaLink="false">http://premierwebtemplates.com/blog/?p=90</guid>
		<description><![CDATA[ Accessibility is a crucial factor in website designing. Investing thoughts and elements on how the website looks is all well but what is more important is how accessible the it is to visitors and prospective customers.

An ideal website design focuses on letting the visitors attain a higher level of accessibility into the website. Here are some tips that can help you create a website design that allows visitors to come through with minimal troubles:
]]></description>
			<content:encoded><![CDATA[<p>Accessibility is a crucial factor in website designing. Investing thoughts and elements on how the website looks is all well but what is more important is how accessible the it is to visitors and prospective customers.</p>
<p>An ideal website design focuses on letting the visitors attain a higher level of accessibility into the website. Here are some tips that can help you create a website design that allows visitors to come through with minimal troubles:<span id="more-90"></span></p>
<h4>ALT Text</h4>
<p>Do make sure to include meaningful ALT text in your website design. Visually impaired users are able to browse through the site when their screen readers read aloud the ALT text. With the ALT text missing from your website design, your website will potentially be unusable for your blind visitors and you could end up losing out on potential customers.</p>
<h4>Correct Spelling</h4>
<p>Screen readers are not able to pronounce words that are misspelled. So, if the content of your website has any spelling errors the screen readers will completely ignore the word and the sentence will make no sense to the user. Visually impaired users have a sense of your web design through what the screen readers portray. And if they have a bad impression, you stand to lose business. Avoid abbreviations as much as you can. Just like screen readers don&#8217;t recognize spelling errors, the same way it fails to know abbreviated words. They try to spell it out and end up pronouncing some undecipherable word. For example you might be able to know that &#8216;eg&#8217; is example but the screen reader may pronounce it as &#8216;egg.&#8217; Thus, it is always better to use good website design practices to make life easier for your users.</p>
<h4>Contrasting Colors for Text</h4>
<p>Dark text on a light or white background is the tried and tested best for most people as it increases readability. Even if you are using other colors make sure to keep the text color in dark contrast to the background.</p>
<h4>Readable Text</h4>
<p>Make your text resizable so that people with poor eyesight are able to resize the content matter to suit them.</p>
<h4>Colors and <abbr title="Cascading Style Sheet">CSS</abbr></h4>
<p>Adjust the colors of your website using web design solutions such as CSS. Thus, if by chance visitors find your default stylesheet hard to use, they can turn it off and use their own stylesheet.</p>
<h4>Sensible Links</h4>
<p>Make sure that all the links on your website make sense even out of context. Visually impaired people often skip through the links on a page. Links like &#8216;Click here&#8217; does not make any sense to them. rather try framing &#8216;Click here for more information about website design.&#8217; This would tell them what exactly are they for.</p>
<blockquote><p>Maneet Puri is the Director of LeXolution IT Services, a leading <a href="http://www.lexolutionit.com" target="_blank">web design firm in India</a> that specializes in web designing and development, website maintenance and internet promotion. With 10 years of industry experience to boast of Maneet advises his clients on hiring offshore web designing services</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://premierwebtemplates.com/blog/web-design-tips/7-tips-to-make-your-website-super-accessible/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

