<?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: Extension developers: Give your extension an accessibility checkup for Firefox 3!</title>
	<atom:link href="http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/</link>
	<description>Musings, tips and tricks about the accessible software world</description>
	<lastBuildDate>Thu, 22 Jul 2010 22:41:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Bite Size projects for open web a11y &#171; Access Garage</title>
		<link>http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/comment-page-1/#comment-3743</link>
		<dc:creator>Bite Size projects for open web a11y &#171; Access Garage</dc:creator>
		<pubDate>Thu, 11 Sep 2008 09:03:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/#comment-3743</guid>
		<description>[...] Test &amp; provide a11y feedback to the developers on a11y issues. Are they even keyboard navigable? Do they work with a screen reader? Help developers understand the XUL accessibility guidelines and the most common accessibility issues in extensions. [...]</description>
		<content:encoded><![CDATA[<p>[...] Test &amp; provide a11y feedback to the developers on a11y issues. Are they even keyboard navigable? Do they work with a screen reader? Help developers understand the XUL accessibility guidelines and the most common accessibility issues in extensions. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco&#8217;s accessibility blog &#187; Blog Archive &#187; Extension developers: 10 things to make your extension more accessible</title>
		<link>http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/comment-page-1/#comment-1663</link>
		<dc:creator>Marco&#8217;s accessibility blog &#187; Blog Archive &#187; Extension developers: 10 things to make your extension more accessible</dc:creator>
		<pubDate>Tue, 01 Jul 2008 12:38:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/#comment-1663</guid>
		<description>[...] my first reach out to extension developers, Aaron and I have brainstormed and come up with the 10 common things you as [...]</description>
		<content:encoded><![CDATA[<p>[...] my first reach out to extension developers, Aaron and I have brainstormed and come up with the 10 common things you as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco&#8217;s accessibility blog &#187; Blog Archive &#187; Extension developers: 10 things to make your extension more accessible</title>
		<link>http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/comment-page-1/#comment-1664</link>
		<dc:creator>Marco&#8217;s accessibility blog &#187; Blog Archive &#187; Extension developers: 10 things to make your extension more accessible</dc:creator>
		<pubDate>Tue, 01 Jul 2008 12:38:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/#comment-1664</guid>
		<description>[...] my first reach out to extension developers, Aaron and I have brainstormed and come up with the 10 common things you as [...]</description>
		<content:encoded><![CDATA[<p>[...] my first reach out to extension developers, Aaron and I have brainstormed and come up with the 10 common things you as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wladimir Palant</title>
		<link>http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/comment-page-1/#comment-1225</link>
		<dc:creator>Wladimir Palant</dc:creator>
		<pubDate>Thu, 22 May 2008 14:54:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/#comment-1225</guid>
		<description>Due to the way Adblock Plus initializes its shortcut keys, the &quot;clashes&quot; are always going at the expense of Adblock Plus. So the web developer extension always wins, and its users can edit CSS while not being able to open Adblock Plus preferences. The only improvement that I want to implement is removing Adblock Plus shortcut keys entirely if conflicts are detected - just to make sure no dysfunctional shortcut keys are displayed in menus.

That unfortunately doesn&#039;t really solve the problem for Adblock Plus power users who have to open preferences regularly because of building their own filter list.</description>
		<content:encoded><![CDATA[<p>Due to the way Adblock Plus initializes its shortcut keys, the &#8220;clashes&#8221; are always going at the expense of Adblock Plus. So the web developer extension always wins, and its users can edit CSS while not being able to open Adblock Plus preferences. The only improvement that I want to implement is removing Adblock Plus shortcut keys entirely if conflicts are detected &#8211; just to make sure no dysfunctional shortcut keys are displayed in menus.</p>
<p>That unfortunately doesn&#8217;t really solve the problem for Adblock Plus power users who have to open preferences regularly because of building their own filter list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco</title>
		<link>http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/comment-page-1/#comment-1198</link>
		<dc:creator>Marco</dc:creator>
		<pubDate>Mon, 19 May 2008 10:22:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/#comment-1198</guid>
		<description>@Wladimir: Thanks for your reply! I know that finding shortcut keys that don&#039;t clash is almost impossible with applications that are as extensible as Firefox, Thunderbird &amp; Co. Since Adblock Plus also puts an entry in the Tools menu, and adds itself to the context menu of items on pages as well, it is both reachable and discoverable for keyboard users. So, you&#039;re not becoming inaccessible by removing these shortcut keys.

As for the number of times a particular dialog is needed: I&#039;ve subscribed to two filter sets and have not needed to open the Adblock Plus preferences dialog ever since. Whereas I can very well see that web developers will need to edit CSS very frequently, I would really consider not clashing with it, as one commenter on your blog post also suggested.</description>
		<content:encoded><![CDATA[<p>@Wladimir: Thanks for your reply! I know that finding shortcut keys that don&#8217;t clash is almost impossible with applications that are as extensible as Firefox, Thunderbird &#038; Co. Since Adblock Plus also puts an entry in the Tools menu, and adds itself to the context menu of items on pages as well, it is both reachable and discoverable for keyboard users. So, you&#8217;re not becoming inaccessible by removing these shortcut keys.</p>
<p>As for the number of times a particular dialog is needed: I&#8217;ve subscribed to two filter sets and have not needed to open the Adblock Plus preferences dialog ever since. Whereas I can very well see that web developers will need to edit CSS very frequently, I would really consider not clashing with it, as one commenter on your blog post also suggested.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wladimir Palant</title>
		<link>http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/comment-page-1/#comment-1196</link>
		<dc:creator>Wladimir Palant</dc:creator>
		<pubDate>Mon, 19 May 2008 07:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/#comment-1196</guid>
		<description>Yes, I am all for accessibility, but... http://adblockplus.org/blog/shortcut-keys-are-hard - if I only knew what can be done about shortcut key conflicts.</description>
		<content:encoded><![CDATA[<p>Yes, I am all for accessibility, but&#8230; <a href="http://adblockplus.org/blog/shortcut-keys-are-hard" rel="nofollow">http://adblockplus.org/blog/shortcut-keys-are-hard</a> &#8211; if I only knew what can be done about shortcut key conflicts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pages tagged "topics"</title>
		<link>http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/comment-page-1/#comment-1194</link>
		<dc:creator>Pages tagged "topics"</dc:creator>
		<pubDate>Mon, 19 May 2008 03:33:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcozehe.de/2008/05/18/extension-developers-give-your-extension-an-accessibility-checkup-for-firefox-3/#comment-1194</guid>
		<description>[...] tagged topicsOwn a Wordpress blog? Make monetization easier with the WP Affiliate Pro plugin. Marco’s accessibility blog � Blog Archive � ...&#160;saved by 1 others  &#160;&#160;&#160;&#160;kneecole22 bookmarked on 05/18/08 &#124; [...]</description>
		<content:encoded><![CDATA[<p>[...] tagged topicsOwn a WordPress blog? Make monetization easier with the WP Affiliate Pro plugin. Marco’s accessibility blog � Blog Archive � &#8230;&nbsp;saved by 1 others  &nbsp;&nbsp;&nbsp;&nbsp;kneecole22 bookmarked on 05/18/08 | [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
