This is an update for all who are interested in our Mac accessibility implementation.

After I blogged about this topic last time, we entered into a bit of a rough time having to do with the text interface of the Universal Access protocol. If you want to read the full details, look at this epic bug.

After that was finally done, which added the capability to interact with text using regular VoiceOver commands, and an associated children caching bug was also fixed, work has now picked up pace again in implementing the finer points of web content accessibility:

  1. Password fields are now accessible, as well as many other types of edits.
  2. Labels are now properly exposed. This includes that input elements nested within labels are now being seen by VoiceOver.
  3. List items on web pages will very soon be exposed properly.

With these all out of the way, I believe it’ll be very very soon that we can offer you all a build to test.

A few known issues we will be working on next:

So the list is down, and I actually don’t deem any of these bugs critical in blocking a release to a wider audience. But I am not the one making that decision here, so this is not an announcement. 😉

Stay tuned to this blog for further information if you’re interested in testing out a Firefox build on the Mac that has VoiceOver support enabled!

After my blog post about the accessibility of Firefox on Mac OS X ramping up stirred up so much interest (thanks again to everyone who commented!), I thought you’d like to hear a bit about the progress we’ve made since then.

When I wrote the original blog post, what we had was very basic content rendering to VoiceOver or Accessibility Verifier. And I mean really basic. We had just crossed the point where loading a second page, or opening a new tab, would actually tell VoiceOver what content there was. Previously, it would not even take notice of the new content and still show the old stuff. Also, the web area was just now then being announced as “HTML content” by VoiceOver, like in Safari.

Since then Hub:

Pretty amazing, eh?

Of course, there are still quite a number of things left to do. To name a few:

As you can see, we still have quite some work ahead of us, and we’ll undoubtedly find more along the way, and with your help once I announce a build that has less known bugs than this above list. 😉