<?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"
	>
<channel>
	<title>Comments on: Accessibility Statement on huge portals</title>
	<atom:link href="http://wojciechbednarski.com/web-accessibility/accessibility-statement-on-huge-portals/feed" rel="self" type="application/rss+xml" />
	<link>http://wojciechbednarski.com/web-accessibility/accessibility-statement-on-huge-portals</link>
	<description>my piece of the Web</description>
	<pubDate>Sun, 27 Jul 2008 09:27:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Tomasz Kępski</title>
		<link>http://wojciechbednarski.com/web-accessibility/accessibility-statement-on-huge-portals#comment-25677</link>
		<dc:creator>Tomasz Kępski</dc:creator>
		<pubDate>Wed, 05 Dec 2007 14:48:53 +0000</pubDate>
		<guid isPermaLink="false">http://wojciechbednarski.com/in-english/accessibility-statement-on-huge-portals#comment-25677</guid>
		<description>Good, very detailed info but in accessibility statement i would suspect rather simply guide through current website features (such as accesskeys) only than OS configuration issues. 

One of the accessibility aspects is simplicity. If BBC would like to prepare such "eLearning" they should rather build separate website. And have the real accessibility statement *only*, under the mentioned address.

BTW you wrote: "have clean HTML and full CSS layout. In another words which was accessible". 
The clean HTML doest not automatically mean accessible. I know you know, but it has to be written ;-) 
Moreover you can have few small bugs in HTML and still have accessible website. I do agree any webmaster should try to reach 100% W3C compliance, and if is really good he would. 
But not validating content is not a accessibility disaster.</description>
		<content:encoded><![CDATA[<p>Good, very detailed info but in accessibility statement i would suspect rather simply guide through current website features (such as accesskeys) only than OS configuration issues. </p>
<p>One of the accessibility aspects is simplicity. If BBC would like to prepare such &#8220;eLearning&#8221; they should rather build separate website. And have the real accessibility statement *only*, under the mentioned address.</p>
<p>BTW you wrote: &#8220;have clean HTML and full CSS layout. In another words which was accessible&#8221;.<br />
The clean HTML doest not automatically mean accessible. I know you know, but it has to be written ;-)<br />
Moreover you can have few small bugs in HTML and still have accessible website. I do agree any webmaster should try to reach 100% W3C compliance, and if is really good he would.<br />
But not validating content is not a accessibility disaster.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maciej Pawłowski</title>
		<link>http://wojciechbednarski.com/web-accessibility/accessibility-statement-on-huge-portals#comment-16205</link>
		<dc:creator>Maciej Pawłowski</dc:creator>
		<pubDate>Tue, 19 Jun 2007 22:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://wojciechbednarski.com/in-english/accessibility-statement-on-huge-portals#comment-16205</guid>
		<description>I think that's really good idea, but… (I hate buts)
When I visited &lt;a href="http://www.bbc.co.uk/accessibility/" rel="nofollow"&gt;the page&lt;/a&gt; I've seen… chaos, it could be more organised.

Also, who needs rounded corners on that kind of page? The page should be as much lightweight as it's possible.

The code, huh… &#60;span class="hide"&#62;.&#60;/span&#62;? Dreamweaver templates?!</description>
		<content:encoded><![CDATA[<p>I think that&#8217;s really good idea, but… (I hate buts)<br />
When I visited <a href="http://www.bbc.co.uk/accessibility/" rel="nofollow">the page</a> I&#8217;ve seen… chaos, it could be more organised.</p>
<p>Also, who needs rounded corners on that kind of page? The page should be as much lightweight as it&#8217;s possible.</p>
<p>The code, huh… &lt;span class=&#8221;hide&#8221;&gt;.&lt;/span&gt;? Dreamweaver templates?!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
