Archive for the ‘Mozilla’ Category

A few important changes to the accessibility of the Location Bar

Friday, January 25th, 2008

As those of you working with Nightly builds may have already noticed, there have been a few important bug fixes made for the Location bar and a few other Places-related controls. Here’s a summary of them:

  • The Location bar pop up no longer announces itself to screen readers as being a menu. As a result, those screen readers who had difficulties dealing with the Location bar in the past few months will now do a better job of tracking selected items.
  • Speaking of items: In the AutoComplete popup, Download Manager and other spots throughout the browser where RichListboxes are being used, items within these now announce themselves as list items rather than listboxes. Screen readers should now properly read these without repeating “listbox” or similar announcements for each selection.
  • The Add Bookmarks dialog now announces itself as a panel/grouping rather than a menu. Same applies as stated above: Screen readers should now be able to read this dialog much better.
  • Larry is now keyboard accessible. Larry is a button in the vicinity of the Location bar that provides useful immediate information about a site’s status. On secure sites such as https://bugzilla.mozilla.org, the button label itself already states the signer of the page. Pressing it using SPACE gives a bit more immediately useful information. This saves one from going to Tools, Page Info… and navigating to the Security tab. The Larry button can be found by going to the Location bar with CTRL+L and pressing SHIFT+TAB.
  • Alerts should now no longer be double-spoken or even triple-spoken by screen readers.

Please give these areas a whirl, and report problems either to this blog post or to bug 407359. Although we thoroughly tested it, there may still be scenarios we overlooked. For example, F6 currently focuses the Larry button instead of the Location bar, and we’re considering to change that bit of behaviour. CTRL+L or ALT+D will still get you to the Location bar directly.

Happy browsing!

Firefox integration into Linux also sounds native to the platform

Thursday, January 10th, 2008

Michael Ventnor, a Mozilla intern working on the Linux integration of Firefox 3, just posted a great summary of the work that has been done for Firefox 3. For those of you who can see, he also has a bunch of screen shots that show Firefox nicely integrating into the Gnome Desktop on Ubuntu.

I’d like to add a few items that a blind user who uses Firefox 3 with Orca will notice.

Aside from the obvious, the web browsing itself, great attention has been paid to make dialogs such as the Preferences dialog behave like dialogs in other Gnome apps: The Cancel button comes before the OK button while tabbing through the dialog. The dialog itself is found under the Edit menu, as is usual for other Gnome apps, and it’s called “Preferences”, not “Options” like on Windows.

The Location Bar is an AutoComplete, a widget type not found on Windows, but used natively on Linux.

The Places Organizer tree tables are native tree tables, displaying hierarchical information in multi-column view.

As you would expect, the Open File, or any kind of Save As dialogs are the native Gnome dialogs, so if you’re used to using GEdit, OpenOffice etc., you’ll feel right at home, Firefox is not requiring you to learn something new here.

One inconsistency I found–and I’ll have to find out whether a fix for this is planned– is the fact that above mentioned Tree Tables cannot be navigated like, for example, in Nautilus: In Nautilus, you expand a collapsed item using the + key, and collapse it using the - key. Pressing Right Arrow moves you one column to the right, Left Arrow moves you one column to the left. This does not yet work in Firefox (or Thunderbird, for that matter). There, Right Arrow expands, Left Arrow collapses an expandable node, and moving between columns isn’t possible at all currently. So this is typical Windows-style still, but within that, consistent across platforms.

All in all, I expect the browsing experience with Firefox 3 on Linux to be a great one. The Orca team is putting hard work into making Orca work well with Firefox, and the past month alone has brought an emense boost in speed, as discussed here.

Orca is gearing up with Firefox!

Friday, December 21st, 2007

Last night, the Orca team announced on their mailinglist that, due to a recent bugfix in the Firefox 3 nightly builds, they were able to drastically improve speed while navigating a web page line by line. I tried it out, and I must say you guys really understated this achievement! It feels like Orca with Firefox is really gearing up now!

A big thanks to both developers of the Mozilla accessibility module and the Orca team for working so closely to make these improvements possible! It shows that the open-source model is one that is really there to benefit all users wherever possible.

If you’re interested in trying out these improvements in responsiveness, get the latest nightly build of Firefox 3, install Py-ATSPI and Orca from source, read the notes on installing and using Firefox 3 with Orca, and have fun with this great improvement!

Note note note: Both Firefox nightlies and Orca installed from source arre products currently under development, so you should use them only for testing, but not expose any valuable data to them without a good backup strategy!

Please see also Orca developer Joanmarie Diggs’s announcement to the Orca list, which tells you all the details of the speed improvement.

By the way: This blog post was created using Firefox nightly of December 20, 2007, and latest Orca trunk from early December 21, which has the speed improvements.

Funny language announcements when reading messages in Thunderbird

Thursday, December 20th, 2007

Have you ever noticed announcements like “x-western” or “x-cyrillic” when reading messages in Thunderbird? JAWS and possibly other screen readers that support the detection of language attributes in HTML content may announce this. The reason is that Thunderbird puts the encoding of a message into the “lang” attribute for each paragraph of content.

The problem is: Screen readers such as JAWS usually do not know what to do with these language names. They’re familiar with regular language names such as “en-us” or “de”, but not “x-western” or the like. As a result, the “language” is indicated with its attribute value. JAWS would also do this if you used Eloquence as your speech synthesizer, but encounter a web site that is tagged with lang=da” for the “Danish” language. JAWS would indicate to you that the web site is meant to be in Danish, but that the current speech synthesizer does not support this language. If you used RealSpeak and had the Danish voice installed, that voice would be then switched to, and the Danish text read out in the native tongue.

So what do we do to get rid of these announcements? There are two possibilities:

Turn off language detection for Thunderbird

One possibility is to turn offf the Language Detection feature for Thunderbird alltogether. The steps are rather simple, but you’d lose language switching if you read a blog feed or properly language-tagged HTML message. To turn off Language Detection, in JAWS you would do the following:

  1. Start Thunderbird.
  2. Press INSERT+F2 to bring up the List of Managers.
  3. Chooose the Configuration Manager entry.
  4. Inside Configuration Manager, go to the Set Options menu, then select Text Processing.
  5. Within the Text Processing dialog, tab to the checkbox that says “Detect Languages”, and uncheck it.
  6. Press ENTER to accept the changes, CTRL+S to save the configuration, and ALT+F4 to close Configuration Manager and return to Thunderbird.

See the relevant steps if you’re using a different screen reader and also want to turn off Language Detection.

Make those encoding languages simply use your default synthesizer language

A less drastic, yet a bit more involved method is to introduce those encodings to JAWS by making them simply use the default Eloquence language you’re using.

JAWS stores language mappings in a [ShortName Language Aliases] section in the DEFAULT.JCF configuration file. There, language attributes such as “en-us” are mapped to Eloquence languages such as “American English”. This section can be enhanced or changed in application specific JCF files. To enhance the Thunderbird JCF file with the encodings that you no longer want announced:

  1. In your User Settings directory, locate the Thunderbird.jcf file. If it is not already there, create one using NotePad or your favorite plain text editor. Note: You can go to your JAWS User Settings directory by going to Start Menu, All Programs, JAWS 8.0 (or 7.10 or 9.0), Explore JAWS, Explore My Settings.
  2. In that newly created or existing Thunderbird.jcf file, add the following lines:
    [Eloq Language Aliases]
    x-western=American English
    x-unicode=American English
    x-central-european=American English
    x-cyrillic=American English
  3. Save the file.

Let’s break this down a bit so you know what you just pasted:

  • The [Eloq Language Aliases] section heading tells JAWS that this is a Language Aliases section for Eloq, the short name for the Eloquence synthesizer.
  • To the left of each equals sign is the value that’s being put in the “lang” attribute, and which is not recognized by JAWS by default.
  • To the right of the equals sign is the Eloquence language that is to be used whenever this “lang” attribute value is encountered.

Happy reading!

What’s new in accessibility for Firefox 3 article

Thursday, December 20th, 2007

I recently posted an article to Mozilla Support that tells a bit about the new features of Firefox 3 accessibility, and what each feature is useful for. This article has now gone live, and you can read it here.

Enjoy!

Firefox 3 Beta 2 now available for download!

Wednesday, December 19th, 2007

If you haven’t heard it already, Firefox 3 Beta 2 is now available for download. One immediately noticeable difference from Beta 1 is, if you surf to a page that contains combo boxes, JAWS will no longer read all entries of such combo boxes in the virtual document, but will once again read the selected item only. On pages that contain, say, a combo box to select your country of origin, this is a huge relief.

One known issue is that the AutoComplete list that pops up in the Location bar announces itself to be a “menu” to screen readers. While JAWS 8.0, NVDA on Windows, and Orca on Linux cope well with this, Window-Eyes has problems reading the entries and keeping track of the focus. JAWS 9.0 will even announce the list as being a context menu, causing its automatic highlighting feature to always select the first found entry, making address entry a really cumbersome experience. The same is true in part for the Add Bookmarks dialog, which also announces itself to be a menu when it truly is a panel. For interested parties, we’re working on this issue in this bug report.

JAWS 9.0 also will not read any text in forms mode in Firefox 3. This is something Freedom Scientific must fix in a JAWS update. For this and the above reason, I strongly suggest to use JAWS 8.0 for surfing with Firefox 3 Beta 2.

Other than that, happy surfing! And feedback is always welcome!