Banshee Accessibility

Over the next week or two I plan to document some work I am doing on Banshee to increase it’s accessibility. It has been a while since I was able to concentrate on a pet project without feeling guilty about my other responsibilities, recently I was able to put some time into Banshee accessibility, and have fun at the same time!

Disclaimer: I currently only working on bare-bones Banshee with UI no extensions like Last.fm. Extensions need to be worked on too, in due time.

Finding access blockers in software is an easy process, you could achieve a good measure of coverage just by using common sense. There will always be issues that you have overlooked, luckily in the Open Source world, there will always be vocal users who will be happy to point out why your application sucks just a bit. Of course you could always opt for an official audit, or refer to such documents as Section 508 for further access requirement guidelines.

In my non-methodological review, I found several issues that need addressing, I am sure there are more, in such a rich application like Banshee, it is hard to reach all the corners, if you see any glaring omissions, or even something more nuanced, please let me know, and I will add it to this master list.

Input Access

Keyboard access, or more specifically non-pointer access, is important for accessibility. Pointer access requires a minimal amount of dexterity and vision. Keyboard access, while not always as efficient or as discoverable, allows keyboard users, or users of alternative input methods to use all features of an application in an unassisted manner. Of course, by adding mnemonics and keyboard shortcuts in a smart fashion that complements the workflow in the application, you provide power users and keyboard users alike with a snappy and efficient experience when using your software.

Of course, there is the other extreme too. Your application should not require elaborate keyboard gestures as the only means of access. This too, requires an amount of dexterity that could be strenuous on keyboard users, especially on-screen keyboard users. Just like general usability, functionality should be easily learnable, users should not have to memorize keyboard commands. This limits usability for users with cognitive disabilities.

Bottom line, provide more than one way of achieving the same thing: Pointer access that will be discoverable to users, and keyboard access that is easily learnable (ctrl+n opens a new document), not too elaborate (not more than two modifiers, no timed strokes, like “double click”), conforms with expected behavior (tab moves focus, ctrl+z does undo).

Before considering shortcuts and mnemonics, a GUI should cycle focus from one component to another when pressing tab. Tab focuses on the next item in logical order, and shift+tab focuses on the previous item. If the focus widget consumes the tab key, for example a text entry widget, ctrl+tab should be used to cycle through it.

A typically sensitive area is drag and drop. Drag and drop requires simultanious pointer motion: click on an item or selection, move pointer while holding down left mouse button, let go of mouse button when pointer is over destination. Besides being a bit complex, often drag and drop operations perform non-trivial tasks that are hard to undo, like file operations. Ever drop a bunch of files over a folder icon in Nautilus, only to discover that they ended up in the parent folder because you weren’t precise enough?

Banshee Input

The first thing I tested was focus cycling. Pressing tab six or seven times returns you to the toolbar, this is good news, it means nothing is grabbing tab in a fashion that won’t let us cycle. When a toolbar item is focused, the left/right arrow keys are used for changing focus between the different toolbar items in the toolbar, this is where problems occurred. When Banshee first starts the seek bar is set to zero, and is disabled, after arrowing right a few times, focus lands on the volume item, pressing any arrow key when the volume item is in focus will invoke the volume control, the only way of returning to other toolbar items is to focus out and back into the toolbar. When a song is paused or playing, and the seek bar holds a value, it will grab focus, and won’t let you right arrow to the volume item. Unlike the volume control, when focus is stuck on the seek bar, the arrow keys don’t do anything useful like seeking, neither does page up/down help.

Knowing that the list views used in Banshee are custom widgets, I was pleasantly surprised to see that there is proper cursor control when arrowing down or up with the control key pressed. This allows selecting multiple items using the keyboard, and exploring the list without changing the selection.

When clicking on the column headers in the track list view, I was able to change the sorting order of the tracks. This doesn’t seem to be possible with the keyboard. The vanilla GtkListView focuses on the column headers before focusing on the list cells. This allows keyboard interaction with the column headers. The Banshee ListView does not implement this.

There seems to be no way to search in a track with the keyboard, I found an open bug that says it used to be possible with ctrl+left/right, this should be reintroduced.

There seems to be alternative methods for drag and drop tasks. I was able to queue and add songs to playlists with the keyboard alone. I may have missed some drag and drop features, if I did let me know.

Theming

While application developers and designers often have a good idea of the look and feel an application should have, it is still necessary to allow users to tweak the user interface’s appearance to achieve higher contrast and comfortable colors. As the computer-literate population ages, the sleek, fine print, interfaces that used to be sexy and awesome will become more of a liability, and something more easy on the eyes will be required.

Specific colors should not be relied on to convey status or information, if they do, there should be a textual alternative.

The text size limit that a GUI could handle should ultimately be the physical display used. For example, I should be able to set the application font to 36 points, and still have the application usable and mildly aesthetic on a 40 inch display.

Banshee Theming

Before trying any special themes with Banshee, I noticed when testing the focus cycle that the Banshee ListView widgets don’t have a clear focus indicator. Anyone who could tell me where keyboard focus is in the screenshot below will receive a free gmail account.

Banshee screenshot: Where is the current focus?

Next I tried all the different contrast themes.

Banshee screenshot: Low contrast themeBanshee screenshot: High contrast themeBanshee screenshot: High contrast inverse theme

You will notice that it is not possible to read the selection on the left treeview, this is a transient issue that rears it’s head only in certain focus states. The icons in the high-contrast theme are not all high contrast, and their size is not consistent. This is a long-standing, system-wide, issue with accessibility theming, it isn’t Banshee specific, but it needs to be fixed too. The other noticeable issue in the inversed contrast theme is the invisibility of the column header borders in the mail track ListView. Overall, I am pretty pleased with Banshee’s behavior in contrast themes.

As ugly as Banshee looks with large fonts, it renders fairly well, without any serious issues.

Banshee screenshot: Custom large fonts

One cute UI elements I was not able to personally explore is the capacity bar displayed when a portable music player is plugged in.

Banshee screenshot: Portable player capacity bar widget

The text alternative here seems to do the job, if we were left to colors alone, it would have been an issue. I couldn’t directly test this for ATK support, as I stole this screenshot from the Banshee website.

AT-SPI Support

A recent requirement for applications with GUIs is that they provide out-of-process programmatic access to their interface. This allows assistive technologies to provide alternative output and input for the application. In GNOME we are very fortunate to have AT-SPI, which is a relatively clean accessibility API.

AT-SPI Support in Banshee

A quick way to test AT-SPI support is to use Orca when keyboarding through the application. When tabbing through Banshee, I hardly heard anything. When navigating the top toolbar, I mostly just heard “button”. Browsing artists, albums or tracks brought up no speech at all. We can now use Accerciser to get a better idea why Orca was not providing useful speech for Banshee. Browsing Banshee with Accerciser quickly shows us the reasons for Orca’s muteness.

  • The play button does not have a text alternative in the accessible object to complement the play icon.

Highlighted play button

Play button in Accerciser's tree view

  • The biggest omission in Banshee’s AT-SPI tree is the custom ListView widget. As seen in the Accerciser screenshot below, a childless accessible object with the role on ‘unknown’ is in place of where we would expect a ‘table’ accessible. This is probably the biggest single access blocker in Banshee, since the ListView widget is the principal component in Banshee, and is part of what makes it such a great media manager.

Highlighted artists ListView widget

Artists ListView in Accerciser's tree view

Summary

Here is a final task list I hope to check off. Might not get to all of this, but I hope to follow up with posts soon when I do.

  • Banshee’s ListView AT-SPI support (bug #533030).
  • Text alternatives to icon buttons (bug #595294).
  • Visible focus indicator for Banshee’s ListView (bug #595296).
  • ListView column headers’ borders visible in high-contrast inverse (bug #595297).
  • Keyboard control of ListView column headers (bug #595299).
  • Add keyboard support for in-track seeking (bug #535924).
  • Fix top toolbar keyboard navigation (bug #595300).
Banshee Accessibility

3 thoughts on “Banshee Accessibility

  1. anonymous coward says:

    My main complaints about Banshee are keyboard-related:
    1) The treeviews do not support type-ahead find
    2)The keyboard shortcuts are non-standard and often don’t use modifier keys (such as ctrl, alt, etc).

    Together, these two issues become a nightmare. For example, if you type N you will skip to the next song. Now, if you are used to type-ahead find and would like to find a specific song in the treeview, you would focus the treeview and start typing. In the process you would possibly skip several songs (N), go back (B), or even edit the selected track’s metadata (E). A disaster!

    1. Eitan says:

      Thanks, Coward.

      Your feedback is very correct. Using space as a keyboard shortcut is a bad idea! We should stick to standard keys.

Comments are closed.