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:
- got headings to be announced.
- got tabs to count correctly, and all roles to be spoken.
- got dialog texts and other text to speak completely.
- got links to be pressable through VoiceOver.
Pretty amazing, eh?
Of course, there are still quite a number of things left to do. To name a few:
- Navigating by character, or interacting with, the text in the awesome bar does not speak the character.
- Firefox doesn’t tell VoiceOver when a page has finished loading.
- password entry fields not identified as such, entering password does not generate typical audible click.
- VoiceOver does not see form fields that are nested inside label elements
- VoiceOver says “text” after each chunk of text it reads inside paragraphs, does not do that in Safari.
- Various form element states not communicated to VoiceOver
- WAI-ARIA landmarks are not communicated to VoiceOver.
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. 😉