<?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>Perth Digital Agency &#187; Dynamic content</title>
	<atom:link href="http://www.slinky.net.au/tag/dynamic-content/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.slinky.net.au</link>
	<description>SEO, Web Design &#38; Digital Strategy</description>
	<lastBuildDate>Tue, 17 Aug 2010 01:12:07 +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>Web Design &amp; Accessibility: Adding features to websites</title>
		<link>http://www.slinky.net.au/web-design-tips/web-design-accessibility-adding-features-to-websites/</link>
		<comments>http://www.slinky.net.au/web-design-tips/web-design-accessibility-adding-features-to-websites/#comments</comments>
		<pubDate>Tue, 20 Jan 2009 05:22:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[web design tips]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Dynamic content]]></category>
		<category><![CDATA[W3C]]></category>

		<guid isPermaLink="false">http://slinky.net.au/?p=389</guid>
		<description><![CDATA[There are certain guidelines on W3 about web content accessibility which are aimed at making using websites easier for people with disabilities. These guidelines should be taken into consideration by all web content developers and designers. The primary goal is to promote accessibility, but other advantages also are present. It makes your page easy not [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: left;"><a href="http://202.125.42.98/web-design/wp-content/uploads/g8crop.jpg"><img class="aligncenter size-full wp-image-399" title="Perth Digital Advertising Agency" src="http://202.125.42.98/web-design/wp-content/uploads/g8crop.jpg" alt="" width="485" height="162" /></a>There are certain guidelines on <a title="The World Wide Web Consortium" href="http://www.w3.org/">W3</a> about web content accessibility which are aimed at making using websites easier for people with disabilities. These guidelines should be taken into consideration by all web content developers and designers. The primary goal is to promote accessibility, but other advantages also are present. It makes your page easy not only for your customers with some disability but easier to use for the ones with no disabilities. It does not discourage from using video and audios but they can be used such that it becomes more accessible to a wider audience.<br />
<span id="more-389"></span><br />
If you consider a point of using images and videos you can easily identify two benefits from it. The accessibility benefit is that those who find difficulty in reading can understand from the image itself what it is all about. By providing non text equivalents like pictures and videos it can become easier for those with reading disability. Similarly it is very important to provide text and graphics which are understandable when viewed. When using the foreground and the background colors sufficient care should be taken to ensure that the content is visible for people using monochrome displays or with difficulty in color recognition.</p>
<p>If you are adding movie or animation you can synchronize equivalent alternatives like caption or auditory description of those visual tracks. The use of the markup is also important. By misusing markup for presentation effect like table for layout or header to change font size makes the page difficult to navigate with specialized software. It also makes it difficult to render a page if you construct what looks like a table of data with an HTML PRE element. Content developers should be aware that using these cause accessibility problems and must ensure formatting effects taking into consideration accessibility to all users.</p>
<p>However they should ensure that they do not sacrifice appropriate markup if a certain browser does not support it correctly. Using CSS helps control layout and presentation.</p>
<p>It is necessary to ensure that the pages with new technologies transform gracefully. So design the page such that it can be read without style sheets. Even if style sheets are turned off or not supported ensure that you organize content logically that helps render it in a meaningful order. Dynamic content equivalents should be changed when dynamic content changes. Ensure that pages do not become useless when scripts, applets etc are not supported. If this is not possible provide equivalent alternatives. It is very important to remember that some people with cognitive or visual disabilities may not be able to read moving text or blinking text, ensure that you provide auto updating objects that may be paused or stopped. Provide device independent access. It means that the user may interact with user agent or document with a preferred input and output device like mouse, keyboard, voice, head wand etc. You can provide client side image maps instead of server side image maps. For scripts too provide logical event handlers rather than device dependent event handler.</p>
<p>Keep in mind to make use of the interim solutions so that assistive technologies and old browsers also operate correctly. There are several <a title="The World Wide Web Consortium" href="http://www.w3.org/">W3C</a> guidelines and technologies that you can make use of to make your site accessible which results in graceful transformation of your page to an alternative version.</p>
<p>Peter Brittain<br />
<a title="Perth Web Designers" href="http://www.slinky.net.au">Slinky Digital</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.slinky.net.au/web-design-tips/web-design-accessibility-adding-features-to-websites/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
