<?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/"
		>
<channel>
	<title>Comments on: BSI British Standards invites comments on new draft standard on accessible web content</title>
	<atom:link href="http://www.webstandards.org/2008/12/01/bsi-british-standards-invites-comments-on-new-draft-standard-on-accessible-web-content/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webstandards.org/2008/12/01/bsi-british-standards-invites-comments-on-new-draft-standard-on-accessible-web-content/</link>
	<description>Working together for standards</description>
	<lastBuildDate>Wed, 27 Mar 2013 12:19:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: En Yeni</title>
		<link>http://www.webstandards.org/2008/12/01/bsi-british-standards-invites-comments-on-new-draft-standard-on-accessible-web-content/comment-page-1/#comment-73413</link>
		<dc:creator>En Yeni</dc:creator>
		<pubDate>Mon, 02 Feb 2009 14:46:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1221#comment-73413</guid>
		<description>As a web developer there is several areas that I feel are key to the BSI 8878 that go beyond PAS 78 and WCAG. No longer can web developers rely upon automated tools to see if a website is accessible. This I believe too is only half the battle.</description>
		<content:encoded><![CDATA[<p>As a web developer there is several areas that I feel are key to the BSI 8878 that go beyond PAS 78 and WCAG. No longer can web developers rely upon automated tools to see if a website is accessible. This I believe too is only half the battle.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Partnerprogramme</title>
		<link>http://www.webstandards.org/2008/12/01/bsi-british-standards-invites-comments-on-new-draft-standard-on-accessible-web-content/comment-page-1/#comment-73212</link>
		<dc:creator>Partnerprogramme</dc:creator>
		<pubDate>Mon, 12 Jan 2009 21:15:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1221#comment-73212</guid>
		<description>What is the correct date for the deadline?</description>
		<content:encoded><![CDATA[<p>What is the correct date for the deadline?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jimbo</title>
		<link>http://www.webstandards.org/2008/12/01/bsi-british-standards-invites-comments-on-new-draft-standard-on-accessible-web-content/comment-page-1/#comment-72948</link>
		<dc:creator>Jimbo</dc:creator>
		<pubDate>Mon, 22 Dec 2008 18:40:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1221#comment-72948</guid>
		<description>I think defacto standards which allow all websites to conform and make the internet accessible for disabled users can only be a wonderful thing.
The internet has had a phenominal effect on the world and it seems only fair we put in place measures so everyone can benefit as equally as possible.</description>
		<content:encoded><![CDATA[<p>I think defacto standards which allow all websites to conform and make the internet accessible for disabled users can only be a wonderful thing.<br />
The internet has had a phenominal effect on the world and it seems only fair we put in place measures so everyone can benefit as equally as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Morton, Accessible Web Consultancy</title>
		<link>http://www.webstandards.org/2008/12/01/bsi-british-standards-invites-comments-on-new-draft-standard-on-accessible-web-content/comment-page-1/#comment-72898</link>
		<dc:creator>Richard Morton, Accessible Web Consultancy</dc:creator>
		<pubDate>Fri, 19 Dec 2008 13:10:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1221#comment-72898</guid>
		<description>I can&#039;t imagine that BSI will make the final standard free as they are a commercial organisation, however I am prepared to be pleasantly surprised and eat my hat if I am wrong about that.</description>
		<content:encoded><![CDATA[<p>I can&#8217;t imagine that BSI will make the final standard free as they are a commercial organisation, however I am prepared to be pleasantly surprised and eat my hat if I am wrong about that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Gibson</title>
		<link>http://www.webstandards.org/2008/12/01/bsi-british-standards-invites-comments-on-new-draft-standard-on-accessible-web-content/comment-page-1/#comment-72782</link>
		<dc:creator>Alan Gibson</dc:creator>
		<pubDate>Wed, 10 Dec 2008 14:58:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1221#comment-72782</guid>
		<description>&gt;&gt; So why doesn’t it?

I raised this with the beeb, and they were gracious enough to say (I paraphrase), &quot;Oops.&quot;</description>
		<content:encoded><![CDATA[<p>&gt;&gt; So why doesn’t it?</p>
<p>I raised this with the beeb, and they were gracious enough to say (I paraphrase), &#8220;Oops.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Gibson</title>
		<link>http://www.webstandards.org/2008/12/01/bsi-british-standards-invites-comments-on-new-draft-standard-on-accessible-web-content/comment-page-1/#comment-72777</link>
		<dc:creator>Alan Gibson</dc:creator>
		<pubDate>Tue, 09 Dec 2008 22:30:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1221#comment-72777</guid>
		<description>We might expect the much-touted BBC My Web My Way to be a paragon of accessibility.

So &quot;Skip to content&quot; should skip over common stuff like navigation menus, and go to the page&#039;s distinct content.

So why doesn&#039;t it?</description>
		<content:encoded><![CDATA[<p>We might expect the much-touted BBC My Web My Way to be a paragon of accessibility.</p>
<p>So &#8220;Skip to content&#8221; should skip over common stuff like navigation menus, and go to the page&#8217;s distinct content.</p>
<p>So why doesn&#8217;t it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Worthington</title>
		<link>http://www.webstandards.org/2008/12/01/bsi-british-standards-invites-comments-on-new-draft-standard-on-accessible-web-content/comment-page-1/#comment-72776</link>
		<dc:creator>Tom Worthington</dc:creator>
		<pubDate>Tue, 09 Dec 2008 22:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1221#comment-72776</guid>
		<description>This announcement doesn&#039;t actually say where, or how, to get the draft standard. I suggest making it clear, near the top of the announcement where the draft can be obtained. There is a link near the bottom for getting it in PDF or Word format, but I can&#039;t imagine that BSI would be silly enough to not offer the standard in HTML.

Also it is not made clear if the standard will be made available for free online. If the standard is going to be document which the reader has to pay for then it will not be widely read.

I suggest BSI adopt W3C&#039;s processes and simply provide the standard online in HTML format for anyone to read for free. To do otherwise is a waste of time and effort.</description>
		<content:encoded><![CDATA[<p>This announcement doesn&#8217;t actually say where, or how, to get the draft standard. I suggest making it clear, near the top of the announcement where the draft can be obtained. There is a link near the bottom for getting it in PDF or Word format, but I can&#8217;t imagine that BSI would be silly enough to not offer the standard in HTML.</p>
<p>Also it is not made clear if the standard will be made available for free online. If the standard is going to be document which the reader has to pay for then it will not be widely read.</p>
<p>I suggest BSI adopt W3C&#8217;s processes and simply provide the standard online in HTML format for anyone to read for free. To do otherwise is a waste of time and effort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max Design - standards based web design, development and training &#187; Some links for light reading (9/12/08)</title>
		<link>http://www.webstandards.org/2008/12/01/bsi-british-standards-invites-comments-on-new-draft-standard-on-accessible-web-content/comment-page-1/#comment-72772</link>
		<dc:creator>Max Design - standards based web design, development and training &#187; Some links for light reading (9/12/08)</dc:creator>
		<pubDate>Tue, 09 Dec 2008 10:08:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1221#comment-72772</guid>
		<description>[...] BSI British Standards invites comments on new draft standard on accessible web content [...]</description>
		<content:encoded><![CDATA[<p>[...] BSI British Standards invites comments on new draft standard on accessible web content [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fleisch</title>
		<link>http://www.webstandards.org/2008/12/01/bsi-british-standards-invites-comments-on-new-draft-standard-on-accessible-web-content/comment-page-1/#comment-72751</link>
		<dc:creator>Fleisch</dc:creator>
		<pubDate>Sun, 07 Dec 2008 09:42:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1221#comment-72751</guid>
		<description>I came across this document by chance and I think it&#039;s great work! Getting these standards are more widely spread and included in authoring software is important. Keep up the great work!</description>
		<content:encoded><![CDATA[<p>I came across this document by chance and I think it&#8217;s great work! Getting these standards are more widely spread and included in authoring software is important. Keep up the great work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Williams</title>
		<link>http://www.webstandards.org/2008/12/01/bsi-british-standards-invites-comments-on-new-draft-standard-on-accessible-web-content/comment-page-1/#comment-72730</link>
		<dc:creator>Steve Williams</dc:creator>
		<pubDate>Thu, 04 Dec 2008 18:44:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/?p=1221#comment-72730</guid>
		<description>I will be contacting Julie Howell direct.  I have contacted her several times before to discuss issues.  Julie Howell has MS (Multiple Sclerosis) and has campaigned and promoted awareness to MS as well as web accessibility.

As a web developer there is several areas that I feel are key to the BSI 8878 that go beyond PAS 78 and WCAG. No longer can web developers rely upon automated tools to see if a website is accessible. This I believe is only half the battle.

Web standards can solve problem with  the seperation of content from style and layout which needs to be clearly defined in the new guidelines. For example colour balance for visually impaired or colour blind uses. 

Even today there are websites that are classed as WCAG AA complient that use light grey text on a white background or even green text on a lime green background which is difficult even for a non visually impaired user to read regardless of font size.</description>
		<content:encoded><![CDATA[<p>I will be contacting Julie Howell direct.  I have contacted her several times before to discuss issues.  Julie Howell has MS (Multiple Sclerosis) and has campaigned and promoted awareness to MS as well as web accessibility.</p>
<p>As a web developer there is several areas that I feel are key to the BSI 8878 that go beyond PAS 78 and WCAG. No longer can web developers rely upon automated tools to see if a website is accessible. This I believe is only half the battle.</p>
<p>Web standards can solve problem with  the seperation of content from style and layout which needs to be clearly defined in the new guidelines. For example colour balance for visually impaired or colour blind uses. </p>
<p>Even today there are websites that are classed as WCAG AA complient that use light grey text on a white background or even green text on a lime green background which is difficult even for a non visually impaired user to read regardless of font size.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.351 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2013-05-02 11:57:00 -->