<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Marco's accessibility blog &#187; Gecko</title>
	<atom:link href="http://www.marcozehe.de/tag/gecko/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.marcozehe.de</link>
	<description>Musings, tips and tricks about the accessible software world</description>
	<lastBuildDate>Tue, 22 Jun 2010 07:26:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Last week in the &#8220;Accessible&#8221; module, March 9, 2009</title>
		<link>http://www.marcozehe.de/2009/03/09/last-week-in-the-accessible-module-march-9-2009/</link>
		<comments>http://www.marcozehe.de/2009/03/09/last-week-in-the-accessible-module-march-9-2009/#comments</comments>
		<pubDate>Mon, 09 Mar 2009 10:52:53 +0000</pubDate>
		<dc:creator>Marco</dc:creator>
				<category><![CDATA[ARIA]]></category>
		<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[Gecko]]></category>

		<guid isPermaLink="false">http://www.marcozehe.de/?p=119</guid>
		<description><![CDATA[Last week&#8217;s work saw quite some code cleanup. Unification of role and finalRole Previously, our nsI*Accessible interfaces exposed both role and finalRole properties. While role returned a preliminary role, finalRole always returned the finally determined role after all markup and ARIA processing had taken place. It turned out that the role was hardly ever used, [...]]]></description>
			<content:encoded><![CDATA[<p>Last week&#8217;s work saw quite some code cleanup.</p>
<h3>Unification of role and finalRole</h3>
<p>Previously, our nsI*Accessible interfaces exposed both role and finalRole properties. While role returned a preliminary role, finalRole always returned the finally determined role after all markup and ARIA processing had taken place.</p>
<p>It turned out that the role was hardly ever used, but everyone always asks for the finalRole. So, the decision came about to file <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=481357">bug 481357</a> and get rid of finalRole and make role do what finalRole did previously.</p>
<p>As a prequel to that, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=482013">bug 482013</a> was fixed, refactoring all test files to use the common getRole and testRole functions in the testing framework. As a result, only one instance of .finalRole had to be dchanged to .role in the bug linked to above, to make all tests still work right.</p>
<p>This change will be exclusive to Gecko 1.9.2, since it will need some adjustments in DOM Inspector and other extensions that use our accessibility interfaces.</p>
<h3>Crash fix in tree table code with some side effects</h3>
<p>Alex also fixed <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=471493">a crasher in the tree tables implementation</a> of getChildAtPoint/getDeepestChildAtPoint. After a fix for a <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=481617">leak</a> that was uncovered by the test, the tests are still failing on Linux because of wrong coordinates we&#8217;re getting back. Investigation into this is still ongoing.</p>
<p>Originally, bug 471493 was also supposed to introduce crashtests specific to a11y. However, it appears that, once a crash test has turned on accessibility, that remains on for the remaining crash tests, and some of the others didn&#8217;t react well to that. A solution is under investigation.</p>
<h3>Speaking of leaks</h3>
<p>While investigating <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=420068">bug 420068</a>, Alex found <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=481624">this memory leak</a>. After he fixed that, the other bug seems to have been resolved, too.</p>
<h3>Further test refactoring</h3>
<p>I took on our table testing code and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=481435">refactored it</a> to use the new infrastructure. 4 more files that no longer use their separate implementations of retrievals of accessibles etc. That leaves 3 more files to go, and one of them is disabled right now because of <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=437980">bug 437980</a>.</p>
<p>I also finally got the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=462527">tests for aria-activedescendant refactor</a> off my back. This one had been going on forever (or so it felt).</p>
<h3>HTML 5 features</h3>
<p>One thing I forgot to mention last week was that a few weeks back, the &#8220;indeterminate&#8221; property new to HTML5 was introduced to HTML:input @type=&#8221;checkbox&#8221; elements, effectively giving them the ability to be partially checked, for example as a master checkbox to dependent checkboxes. As expected, we didn&#8217;t expose the mixed state properly on these yet, so I took on <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=477572">that task</a>. As a sequel, I&#8217;m currently working on <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=477975">exposing a proper action name</a> for these as well. I&#8217;m having some trouble getting the tests to run properly, though. The tests go into an endless loop when I run them locally, so until I found out why, I&#8217;m hesitant to throw these at the tinderboxen. If anyone has seen this happen at all, suggestions are welcome. A sample log excerpt can be found <a href="http://pastebin.mozilla.org/631042">here</a>. The tests start running this test_comboboxes.xul file, then the whole a11y test suite starts running all over.</p>
<h3>More text attribute fixes</h3>
<p>Alex got the <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=473570">font-weight bug</a> resolved, so font-weights are now properly exposed according to the visual representation and not through some seemingly arbitrary numbers.</p>
<h3>aria-sort, aria-grabbed, and aria-expanded action exposure</h3>
<p>David has been sinking his teeth into <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=473732">this one</a> and has come up with a great idea to solve this. Since no desktop app ever exposed many of these things especially when it comes to a <strong>controlled</strong> drag and drop action from a screen reader&#8217;s point of view, this one requires careful thinking and design as well as good communication with AT vendors to get right.</p>
<h3>Progress on plugging in accessible trees from plugins</h3>
<p>Recently, community member <a href="http://brad.getcoded.net/">Brad Taylor</a> approached us with the question of plugging in accessible trees from plugins into our accessible tree on Linux, integrating third party plugin accessibility nicely with ours. A <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=480317">bug</a> was filed, and Brad has been working on this, regularly communicating on the accessibility channel with David. A first WIP patch was posted on Friday.</p>
<p>That&#8217;s it for this week.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.marcozehe.de/2009/03/09/last-week-in-the-accessible-module-march-9-2009/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
