<?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>Lifeline Blog&#187; Accessibility</title>
	<atom:link href="http://www.lifelinedesign.ca/blog/category/accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lifelinedesign.ca/blog</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Fri, 19 Aug 2011 21:22:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>Automatic AODA Compliance for your site!</title>
		<link>http://www.lifelinedesign.ca/blog/2010/05/automatic-aoda-compliance-for-your-site/</link>
		<comments>http://www.lifelinedesign.ca/blog/2010/05/automatic-aoda-compliance-for-your-site/#comments</comments>
		<pubDate>Mon, 03 May 2010 15:57:07 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.lifelinedesign.ca/blog/?p=445</guid>
		<description><![CDATA[Lifeline is excited to announce a revolutionary module available only for the Intelligent Web Interface, our proprietary content management system.  This new accessibility module will allow any website running our CMS software to automatically maintain a website that will comply with the upcoming communications standard for the AODA and WCAG 2.0 level AAA accessibility compliance. [...]]]></description>
			<content:encoded><![CDATA[<p>Lifeline is excited to announce a revolutionary module available only for the Intelligent Web Interface, our proprietary content management system.  This new accessibility module will allow any website running our CMS software to automatically maintain a website that will comply with the upcoming communications standard for the AODA and WCAG 2.0 level AAA accessibility compliance.</p>
<p>Users can simply edit and add content as they normally would and the  system will  automatically  ensure that there is an accessible version of any content created available for impaired users.</p>
<p>The first automated system of its kind, the Lifeline AODA automatic compliance module is sure to make the lives of many of our customers easier in the near future!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.lifelinedesign.ca/blog/2010/05/automatic-aoda-compliance-for-your-site/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accessibility Check List: The ALT tag</title>
		<link>http://www.lifelinedesign.ca/blog/2010/03/accessibility-check-list-the-alt-tag/</link>
		<comments>http://www.lifelinedesign.ca/blog/2010/03/accessibility-check-list-the-alt-tag/#comments</comments>
		<pubDate>Mon, 01 Mar 2010 13:39:06 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://www.lifelinedesign.ca/blog/?p=412</guid>
		<description><![CDATA[Today we&#8217;re going to talk about some accessibility specifics and what you can do when creating content to ensure your website remains accessible.  In this post, we&#8217;ll be talking about one of the most important factors for accessibility that you&#8217;ll have to deal with as an end user adding content to a website through a [...]]]></description>
			<content:encoded><![CDATA[<p>Today we&#8217;re going to talk about some accessibility specifics and what you can do when creating content to ensure your website remains accessible.  In this post, we&#8217;ll be talking about one of the most important factors for accessibility that you&#8217;ll have to deal with as an end user adding content to a website through a CMS, with the intention of it remaining accessible.  You&#8217;ll have to take this specific HTML code into  account every time you add a picture to your website.</p>
<p>This important accessibility item is of course the ALT tag, and it is usually one of the first things you&#8217;ll learn about accessibility, solely due to how often it comes up .  It&#8217;s essentially an additional piece of HTML you can use to attach text to an image. This is very helpful for making a website accessible&#8230; at the most basic level, you can use alt tags to describe a picture placed within your content.  A picture of a beautiful sunset would be labeled as &#8220;a picture of a beautiful sunset&#8221; in the alt tag. When an ALT tag is defined,  if someone who had impaired vision was using a screen reader to view your website,  the screen reader would inform them that there is a picture of a beautiful sunset under the cursor, thus helping them better understand the content of your website.</p>
<p>Things can get a bit more complicated than that in the real world though.  ALT tags are often a favorite tool of Internet Marketers who are focusing on SEO (search engine optimization),  as it gives them another avenue to insert keywords into a page for their search engine rankings.  However, for accessibility&#8217;s sake, you must ensure that you are providing accurate descriptions of your images, and images that aren&#8217;t conveying content (i.e. they are purely decorative in nature) must have a null (empty) alt tag &#8212; otherwise an impaired visitor using a screen reader would be confused by the ALT tag descriptions.  To address SEO concerns, you can ensure that images used relate to or  contain images of your keywords while being relevant to the page content.  Using this  method, you can have proper descriptions in your ALT tags as  well as  the keywords that are part of an overall SEO campaign.</p>
<p>An acceptable alternative for images that aren&#8217;t conveying content is to have them implemented as a CSS background. This method uses CSS code to display the image without actually placing it in the HTML code. However, inserting images as a CSS background is not typically an option available when building content in a CMS system, whereas placing alt tags on images is.</p>
<p>This may seem a little overwhelming, but don&#8217;t worry&#8230; if you are using a modern CMS then it will most likely have  a very easy method of inserting ALT tags for your images that you can manage without any specific technical knowledge, provided you understand what the ALT tag is and what information is supposed to be entered for it.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.lifelinedesign.ca/blog/2010/03/accessibility-check-list-the-alt-tag/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AODA and Your Website</title>
		<link>http://www.lifelinedesign.ca/blog/2010/02/aoda-and-your-website/</link>
		<comments>http://www.lifelinedesign.ca/blog/2010/02/aoda-and-your-website/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 14:00:48 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://www.lifelinedesign.ca/blog/?p=260</guid>
		<description><![CDATA[The AODA or Accessibility for Ontarians with Disabilities Act is a law in Ontario governing how businesses and government offices are required to ensure that their operations do not exclude or cause difficulty for Ontarians who are disabled.  Currently, this only extends to business operations in the real world,  and not to virtual places of [...]]]></description>
			<content:encoded><![CDATA[<p>The AODA or Accessibility for Ontarians with Disabilities Act is a law in Ontario governing how businesses and government offices are required to ensure that their operations do not exclude or cause difficulty for Ontarians who are disabled.  Currently, this only extends to business operations in the real world,  and not to virtual places of business like the Internet.</p>
<p>Now, as a regular business this is not something you&#8217;ll have to worry about for quite a few years, but those managing a government office or location will be required to have accessible websites in just a few short years.  This can be an issue in that case, especially if you&#8217;re in the process of (or will shortly be in the process of) building a new website. Typically you would hope to get more than a few years of millage out of a website&#8230; so what can be done to protect your investment in a site now?</p>
<p>First off, it is important to note that the AODA information and communications standard (which will govern website and other communications requirements)  has not been finalized yet, but we can be reasonably confident that the standard for websites is going to be WCAG 2.0 Level A compliance.  It&#8217;s logical to assume that when the standard is finalized, existing websites will not have to be brought up to speed immediately or if they are there will be government funding to help organizations achieve this goal. However, it&#8217;s probably not a good idea to count on that being the case, because it&#8217;s still uncertain until the standard is formalized.</p>
<p>Making your website accessible does add legwork to the project, but most of the legwork should be done by the web provider you&#8217;ve selected and not your organization, and there is certainly value to ensuring your website is accessible to a wider audience.  There are two main points you&#8217;ll want to ensure for accessibility when developing your new website:</p>
<p><strong>1. Ensure your web provider is building a site that will be at least WCAG 2.0 compliant.</strong></p>
<p>If you don&#8217;t already have a good working relationship with your selected provider, ensure that they are contractually obligated to provide WCAG 2.0 compliance or greater. Knowing the Web Design industry, I am positive that there will be web providers out there that will try to capitalize on the new focus on accessibility and promise their customers they are delivering accessible websites, but won&#8217;t actually go through the process of ensuring accessibility, banking on the fact that by the time the standard comes into law, the website will be done and they will be long gone.</p>
<p><strong>2. Ensure that you are trained on creating WCAG 2.0 compliant content.</strong></p>
<p>Very few sites sold today don&#8217;t have a content management system (or CMS for short). If you&#8217;re unfamiliar, a CMS essentially lets you edit and add content to your website without technical knowledge or ability.  Since you will be adding and editing content to your website after it launches, it is extremely important that the CMS your provider is supplying actually supports the creation of accessible content, but also that the training supplied by your provider goes beyond just using the CMS to edit your website, and includes training of  your staff on the steps and processes you will need to go through internally when adding or editing content to ensure that your website remains accessible.</p>
<p>I  hope you found this brief overview of the AODA and how it will apply to your websites in the future helpful; in the next article we&#8217;ll be talking about the requirements a website must meet to be WCAG compliant.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.lifelinedesign.ca/blog/2010/02/aoda-and-your-website/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

