Implementation for FLUID-3711

Colin Clark colinbdclark at
Mon Dec 13 15:09:31 UTC 2010


On 2010-12-13, at 9:59 AM, Justin Obara wrote:

> Hi Antranig, 
> Some comments below.
> On 2010-12-13, at 3:40 AM, Antranig Basman wrote:
>> At length I have come up with an implementation of FLUID-3711/FLUID-3708 that apppears to work under NVDA. A lot of my initial problems seem caused by the fact that live regions simply do not function at all with NVDA under Windows 2000, which is the OS I have in my VM. Switching to Windows XP allows at least some functionality for live regions - however some aspects of ARIA still seem broken, for example audible feedback for progress bars. We will most likely be looking at this issue wrt. the Uploader today. I am using the stable "2010.2" release of NVDA for testing.
> For this release we put in some work on the Progress component. Unless the uploader does something to block the aria from the progress bar, I don't think you will need to worry about it too much, but I might be missing something.

In NVDA 2010.2b2, I didn't hear the telltale progress bar beeps on the Uploader's total progress bar. I think this may well be a regression in the Uploader.

Mike, can you do a side-by-side comparison between the version of Uploader in the AEGIS demo branch and trunk to see if we've got a bug? If it didn't work in the AEGIS demo branch, we should decide if this is required functionality for the release (I think it probably is) and implement it.

>> A patch is attached to this issue which implements the required functionality, with the odd caveat that NVDA needs to be put into something called "focus mode" when operating the reorderer (this is apparently completely unrelated to the labelling function of the patch) otherwise the reorderer and browser will go bananas as they fight with NVDA over the binding of the arrow keys and TAB key. I presume this is a known issue with the reorderer.
> This is a known issue, and is why Harris had been looking at Honestly, I think this is  a bit of a bug with screen readers at the moment, since the reorder already sets roles. It seems that the current crop of screen readers are only auto-switching on the application role. 

Would wrapping the Reorderer in role="application" resolve this issue?

>> We should consider whether it's still appropriate at this point in the release cycle to commit this patch, and whether also to dedicate the resources to test whether it is functional under JAWS also.
> We should talk about this today.

Here's a suggestion: if someone has time this morning, let's apply Antranig's patch and do some early testing. If the fix looks promising, let's include it in the release. If we find any issues with it, let's punt for 1.4.


Colin Clark
Technical Lead, Fluid Project

More information about the fluid-work mailing list