<?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: ABC mobile web site fails accessibility test</title> <atom:link href="http://www.webdirections.org/blog/abc-mobile-web-site-fails-accessibility-test/feed/" rel="self" type="application/rss+xml" /><link>http://www.webdirections.org/blog/abc-mobile-web-site-fails-accessibility-test/</link> <description>Just another WordPress weblog</description> <lastBuildDate>Thu, 09 Feb 2012 09:39:28 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.2.1</generator> <item><title>By: Hugh B</title><link>http://www.webdirections.org/blog/abc-mobile-web-site-fails-accessibility-test/comment-page-1/#comment-163825</link> <dc:creator>Hugh B</dc:creator> <pubDate>Thu, 19 Mar 2009 01:10:23 +0000</pubDate> <guid isPermaLink="false">http://www.webdirections.org/?p=1697#comment-163825</guid> <description>Thanks for pointing this out, Maxine.Firstly, (and not your fault) you are linking to an article I can only see the summary of. Where&#039;s the accessibility there? Gotta love that locked off content.True, we don&#039;t have access to their decisions, but you &lt;em&gt;do&lt;/em&gt; have more to go on than the test results. You can look at the served source code and give us your own evaluation. Andrew has struck on a very important point. What do &lt;em&gt;you&lt;/em&gt; think, as an expert, about the site&#039;s compliance?The great fail I&#039;d like to see the internal decisions around is the choice to serve this content separately. As experts and trustees of taxed money, they should be able to adhere to the most basic web vision of one resource being consumable by any standards-compliant user agent. Remember &lt;a href=&quot;http://www.w3.org/DesignIssues/TLD&quot; rel=&quot;nofollow&quot;&gt;Berners-Lee&#039;s railing against the .mobi top-level domain&lt;/a&gt;?:&lt;blockquote cite=&quot;http://www.w3.org/DesignIssues/TLD&quot;&gt; &quot;This domain will have a drastically detrimental effect on the Web. By partitioning the HTTP information space into parts designed for access from mobile access and parts designed (presumably) not for such access, an essential property of the Web is destroyed.&quot; &lt;/blockquote&gt;I don&#039;t think the ABC will single-handedly harm the Web, but this is the same, only using the new &quot;m&quot; hostname.BTW neither Andrew or I are ABC employees.</description> <content:encoded><![CDATA[<p>Thanks for pointing this out, Maxine.</p><p>Firstly, (and not your fault) you are linking to an article I can only see the summary of. Where’s the accessibility there? Gotta love that locked off content.</p><p>True, we don’t have access to their decisions, but you <em>do</em> have more to go on than the test results. You can look at the served source code and give us your own evaluation. Andrew has struck on a very important point. What do <em>you</em> think, as an expert, about the site’s compliance?</p><p>The great fail I’d like to see the internal decisions around is the choice to serve this content separately. As experts and trustees of taxed money, they should be able to adhere to the most basic web vision of one resource being consumable by any standards-compliant user agent. Remember <a href="http://www.w3.org/DesignIssues/TLD" rel="nofollow">Berners-Lee’s railing against the .mobi top-level domain</a>?:</p><blockquote cite="http://www.w3.org/DesignIssues/TLD"><p> “This domain will have a drastically detrimental effect on the Web. By partitioning the HTTP information space into parts designed for access from mobile access and parts designed (presumably) not for such access, an essential property of the Web is destroyed.“</p></blockquote><p>I don’t think the ABC will single-handedly harm the Web, but this is the same, only using the new “m” hostname.</p><p>BTW neither Andrew or I are ABC employees.</p> ]]></content:encoded> </item> <item><title>By: martinjy</title><link>http://www.webdirections.org/blog/abc-mobile-web-site-fails-accessibility-test/comment-page-1/#comment-163811</link> <dc:creator>martinjy</dc:creator> <pubDate>Wed, 18 Mar 2009 23:00:43 +0000</pubDate> <guid isPermaLink="false">http://www.webdirections.org/?p=1697#comment-163811</guid> <description>+1 for Andrew&#039;s comments. Run that automated test on almost any site and you&#039;ll get hundreds of results. Sure, the ABC could (should) have caught a couple of the obvious errors before release, but this is a non-story without some proper analysis by Crikey.</description> <content:encoded><![CDATA[<p>+1 for Andrew’s comments. Run that automated test on almost any site and you’ll get hundreds of results. Sure, the ABC could (should) have caught a couple of the obvious errors before release, but this is a non-story without some proper analysis by Crikey.</p> ]]></content:encoded> </item> <item><title>By: Maxine</title><link>http://www.webdirections.org/blog/abc-mobile-web-site-fails-accessibility-test/comment-page-1/#comment-163349</link> <dc:creator>Maxine</dc:creator> <pubDate>Tue, 17 Mar 2009 23:19:49 +0000</pubDate> <guid isPermaLink="false">http://www.webdirections.org/?p=1697#comment-163349</guid> <description>Andrew: it would be great if someone involved in the project could weigh in here and give some explanation about their decision making processes. From an outsiders point of view, all we have to go on is those test results. This whole topic officially open for discussion!</description> <content:encoded><![CDATA[<p>Andrew: it would be great if someone involved in the project could weigh in here and give some explanation about their decision making processes. From an outsiders point of view, all we have to go on is those test results. This whole topic officially open for discussion!</p> ]]></content:encoded> </item> <item><title>By: Andrew</title><link>http://www.webdirections.org/blog/abc-mobile-web-site-fails-accessibility-test/comment-page-1/#comment-163319</link> <dc:creator>Andrew</dc:creator> <pubDate>Tue, 17 Mar 2009 22:10:20 +0000</pubDate> <guid isPermaLink="false">http://www.webdirections.org/?p=1697#comment-163319</guid> <description>Please don&#039;t base criticisms on automated tests, it shows a lack of understanding of the actual underlying issues. Automated accessibility tests in particular will often return false positives that require an expert analysis to confirm or deny.I&#039;m not saying the ABC mobile site is without fault, I&#039;m just saying I would rather read an article based on informed opinion and expert review than one pointing out low test scores. Explain the issues! Then everyone can share in the learnings.</description> <content:encoded><![CDATA[<p>Please don’t base criticisms on automated tests, it shows a lack of understanding of the actual underlying issues. Automated accessibility tests in particular will often return false positives that require an expert analysis to confirm or deny.</p><p>I’m not saying the ABC mobile site is without fault, I’m just saying I would rather read an article based on informed opinion and expert review than one pointing out low test scores. Explain the issues! Then everyone can share in the learnings.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 1/10 queries in 0.007 seconds using disk: basic
Object Caching 425/431 objects using disk: basic

Served from: www.webdirections.org @ 2012-02-09 23:50:31 -->
