<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Basic Facts and Resources You Need to Know Now About Web Accessibility</title>
	<atom:link href="http://lorelle.wordpress.com/2011/07/15/basic-facts-and-resources-you-need-to-know-now-about-web-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://lorelle.wordpress.com/2011/07/15/basic-facts-and-resources-you-need-to-know-now-about-web-accessibility/</link>
	<description>Helping you learn more and do more with WordPress</description>
	<lastBuildDate>Wed, 22 May 2013 03:04:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Identifying the Barriers on Your Blog You May Cross &#124; Blog Your Passion</title>
		<link>http://lorelle.wordpress.com/2011/07/15/basic-facts-and-resources-you-need-to-know-now-about-web-accessibility/#comment-986046</link>
		<dc:creator><![CDATA[Identifying the Barriers on Your Blog You May Cross &#124; Blog Your Passion]]></dc:creator>
		<pubDate>Mon, 29 Apr 2013 05:27:48 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/?p=5297#comment-986046</guid>
		<description><![CDATA[[...] for websites include writing policies covering copyright, disclosure, privacy, and comments, web accessibility, and the laws in your state and country on web standards and web [...]]]></description>
		<content:encoded><![CDATA[<p>[...] for websites include writing policies covering copyright, disclosure, privacy, and comments, web accessibility, and the laws in your state and country on web standards and web [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What is a Properly Formed Link? &#124; Learning from Lorelle</title>
		<link>http://lorelle.wordpress.com/2011/07/15/basic-facts-and-resources-you-need-to-know-now-about-web-accessibility/#comment-973994</link>
		<dc:creator><![CDATA[What is a Properly Formed Link? &#124; Learning from Lorelle]]></dc:creator>
		<pubDate>Tue, 08 Jan 2013 23:13:24 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/?p=5297#comment-973994</guid>
		<description><![CDATA[[...] or tab so the reader could keep reading. This has not only proven to not be true, it violates web standards for accessibility and many federal laws for doing so without warning. People now know how to use the back button and how to open links in [...]]]></description>
		<content:encoded><![CDATA[<p>[...] or tab so the reader could keep reading. This has not only proven to not be true, it violates web standards for accessibility and many federal laws for doing so without warning. People now know how to use the back button and how to open links in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Check Out the New Media Manager in WordPress &#171; Lorelle on WordPress</title>
		<link>http://lorelle.wordpress.com/2011/07/15/basic-facts-and-resources-you-need-to-know-now-about-web-accessibility/#comment-969083</link>
		<dc:creator><![CDATA[Check Out the New Media Manager in WordPress &#171; Lorelle on WordPress]]></dc:creator>
		<pubDate>Sun, 02 Dec 2012 22:36:45 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/?p=5297#comment-969083</guid>
		<description><![CDATA[[...] Federal Laws For Web Accessibility and Images All images on commercial or government websites are required by law to feature alternative descriptions within their HTML image tag. In WordPress, this is set in the [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Federal Laws For Web Accessibility and Images All images on commercial or government websites are required by law to feature alternative descriptions within their HTML image tag. In WordPress, this is set in the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Basic Structure of a Blog Post &#124; Learning from Lorelle</title>
		<link>http://lorelle.wordpress.com/2011/07/15/basic-facts-and-resources-you-need-to-know-now-about-web-accessibility/#comment-965125</link>
		<dc:creator><![CDATA[The Basic Structure of a Blog Post &#124; Learning from Lorelle]]></dc:creator>
		<pubDate>Tue, 16 Oct 2012 02:33:48 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/?p=5297#comment-965125</guid>
		<description><![CDATA[[...] at. The title is required in WordPress for the database information, but it is optional to meet the web standards for accessibility. The title is usually the &#8220;title&#8221; of the image such as &#8220;Guernica, 1937 by [...]]]></description>
		<content:encoded><![CDATA[<p>[...] at. The title is required in WordPress for the database information, but it is optional to meet the web standards for accessibility. The title is usually the &#8220;title&#8221; of the image such as &#8220;Guernica, 1937 by [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What You Most Need to Know About WordPress &#171; Lorelle on WordPress</title>
		<link>http://lorelle.wordpress.com/2011/07/15/basic-facts-and-resources-you-need-to-know-now-about-web-accessibility/#comment-955588</link>
		<dc:creator><![CDATA[What You Most Need to Know About WordPress &#171; Lorelle on WordPress]]></dc:creator>
		<pubDate>Sat, 25 Aug 2012 01:48:58 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/?p=5297#comment-955588</guid>
		<description><![CDATA[[...] As required by US Federal law and many international laws, you are required to have a title attribute in your HTML links. WordPress offers this when adding a link from either editor. Use it. The title attribute is supposed to be a descriptive sentence (in sentence structure) that instructs the user about what the destination is for the link. Do not use spammy keywords, just information to help them decide to click. For more information on the law and how it works, see &#8220;Basic Facts and Resources You Need to Know Now About Web Accessibility.&#8221; [...]]]></description>
		<content:encoded><![CDATA[<p>[...] As required by US Federal law and many international laws, you are required to have a title attribute in your HTML links. WordPress offers this when adding a link from either editor. Use it. The title attribute is supposed to be a descriptive sentence (in sentence structure) that instructs the user about what the destination is for the link. Do not use spammy keywords, just information to help them decide to click. For more information on the law and how it works, see &#8220;Basic Facts and Resources You Need to Know Now About Web Accessibility.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle VanFossen</title>
		<link>http://lorelle.wordpress.com/2011/07/15/basic-facts-and-resources-you-need-to-know-now-about-web-accessibility/#comment-951515</link>
		<dc:creator><![CDATA[Lorelle VanFossen]]></dc:creator>
		<pubDate>Mon, 16 Apr 2012 21:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/?p=5297#comment-951515</guid>
		<description><![CDATA[Thank you for the information.]]></description>
		<content:encoded><![CDATA[<p>Thank you for the information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Hassell</title>
		<link>http://lorelle.wordpress.com/2011/07/15/basic-facts-and-resources-you-need-to-know-now-about-web-accessibility/#comment-951510</link>
		<dc:creator><![CDATA[Jonathan Hassell]]></dc:creator>
		<pubDate>Mon, 16 Apr 2012 18:52:24 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/?p=5297#comment-951510</guid>
		<description><![CDATA[Great post, Lorelle, and thanks for the mention of PAS 78, esmi.

Just to let you know that PAS 78 was superseded by BS 8878 in December 2010.

BS 8878S continues PAS 78’s emphasis on providing guidance to &lt;em&gt;non-technical&lt;/em&gt; website owners for the whole process of commissioning, procuring and producing accessible websites, but updates it to provide advice on :
- web 2.0’s much wider purposes for websites (e.g. multimedia sites, Software as a Service sites) and the move from provider-produced content to user-generated content (e.g. blogs, Facebook, YouTube)
- the increasing range of devices on which websites are viewed (e.g. smartphones, tablets, IPTV)
- the increasing use of non-W3C technologies to produce websites
- the increasing use of “off the shelf” website builder tools to create websites rather than bespoke development
- the increasing use of on-site accessibility personalisation tools like CSS style-switchers
- the changing organisational structure of web product teams and key personnel impacting product accessibility, especially the growing role of web product managers

BS 8878 is well worth checking out, and you can find the official slides from its launch, case studies of organisations using BS 8878, detailed blogs on its use by SMEs, tools and training for applying the Standard, and news on its progress towards an International Standard at &lt;a href=&quot;http://www.hassellinclusion.com/bs8878/&quot; rel=&quot;nofollow&quot;&gt;http://www.hassellinclusion.com/bs8878/&lt;/a&gt;

Jonathan Hassell
Lead-author of BS 8878]]></description>
		<content:encoded><![CDATA[<p>Great post, Lorelle, and thanks for the mention of PAS 78, esmi.</p>
<p>Just to let you know that PAS 78 was superseded by BS 8878 in December 2010.</p>
<p>BS 8878S continues PAS 78’s emphasis on providing guidance to <em>non-technical</em> website owners for the whole process of commissioning, procuring and producing accessible websites, but updates it to provide advice on :<br />
- web 2.0’s much wider purposes for websites (e.g. multimedia sites, Software as a Service sites) and the move from provider-produced content to user-generated content (e.g. blogs, Facebook, YouTube)<br />
- the increasing range of devices on which websites are viewed (e.g. smartphones, tablets, IPTV)<br />
- the increasing use of non-W3C technologies to produce websites<br />
- the increasing use of “off the shelf” website builder tools to create websites rather than bespoke development<br />
- the increasing use of on-site accessibility personalisation tools like CSS style-switchers<br />
- the changing organisational structure of web product teams and key personnel impacting product accessibility, especially the growing role of web product managers</p>
<p>BS 8878 is well worth checking out, and you can find the official slides from its launch, case studies of organisations using BS 8878, detailed blogs on its use by SMEs, tools and training for applying the Standard, and news on its progress towards an International Standard at <a href="http://www.hassellinclusion.com/bs8878/" rel="nofollow">http://www.hassellinclusion.com/bs8878/</a></p>
<p>Jonathan Hassell<br />
Lead-author of BS 8878</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What are the Essential WordPress Plugins You Can&#8217;t Live Without? &#171; Lorelle on WordPress</title>
		<link>http://lorelle.wordpress.com/2011/07/15/basic-facts-and-resources-you-need-to-know-now-about-web-accessibility/#comment-951031</link>
		<dc:creator><![CDATA[What are the Essential WordPress Plugins You Can&#8217;t Live Without? &#171; Lorelle on WordPress]]></dc:creator>
		<pubDate>Tue, 03 Apr 2012 00:19:43 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/?p=5297#comment-951031</guid>
		<description><![CDATA[[...] more WordPress Themes come mobile-ready, so adding these Plugins could be redundant. With the new US federal laws for accessibility compliance, all commercial, government, and public sites must meet the new laws for access from cell phones, [...]]]></description>
		<content:encoded><![CDATA[<p>[...] more WordPress Themes come mobile-ready, so adding these Plugins could be redundant. With the new US federal laws for accessibility compliance, all commercial, government, and public sites must meet the new laws for access from cell phones, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress Tips: Exploring the WordPress Text Widget &#171; Lorelle on WordPress</title>
		<link>http://lorelle.wordpress.com/2011/07/15/basic-facts-and-resources-you-need-to-know-now-about-web-accessibility/#comment-943716</link>
		<dc:creator><![CDATA[WordPress Tips: Exploring the WordPress Text Widget &#171; Lorelle on WordPress]]></dc:creator>
		<pubDate>Wed, 24 Aug 2011 05:06:18 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/?p=5297#comment-943716</guid>
		<description><![CDATA[[...] [TIP: Do not use &#039;target=&quot;_blank&quot; to open the link in a new page. To do so without warning is a violation of web standards.] [...]]]></description>
		<content:encoded><![CDATA[<p>[...] [TIP: Do not use &#039;target=&quot;_blank&quot; to open the link in a new page. To do so without warning is a violation of web standards.] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Managing Multiple Authors: Managing Writers in a Multiple Author Blog &#171; Lorelle on WordPress</title>
		<link>http://lorelle.wordpress.com/2011/07/15/basic-facts-and-resources-you-need-to-know-now-about-web-accessibility/#comment-943505</link>
		<dc:creator><![CDATA[Managing Multiple Authors: Managing Writers in a Multiple Author Blog &#171; Lorelle on WordPress]]></dc:creator>
		<pubDate>Thu, 18 Aug 2011 23:40:39 +0000</pubDate>
		<guid isPermaLink="false">http://lorelle.wordpress.com/?p=5297#comment-943505</guid>
		<description><![CDATA[[...] Standards: With the requirement in 2011 for public websites to meet web standards for accessibility coming up, spell out your site&#8217;s accessibility standards and [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Standards: With the requirement in 2011 for public websites to meet web standards for accessibility coming up, spell out your site&#8217;s accessibility standards and [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
