Evaluating Mozilla's Shortcut Commands

 

Summary

Mozilla Internet Suite makes use of many of the standard shortcut commands that most Internet browsers use. A shortcut command is a combination of keys that, when pressed in unison, causes an action to be performed within the program. For example, pressing Ctrl-A on this Internet page will select everything that is on this page. Commands like Ctrl-A are quick and easy to use, but many of the other commands are difficult to use because the combination of keys are located in places on the keyboard that require two hands or are awkward.

Application Description

Mozilla Internet Suite is a free web suite designed by Mozilla.org. Included in the suite are an Internet browser, an address book, a mail and newsgroup reader, and a program debugger.

Test Design

This example demonstrates the use of Scenario testing. In scenario testing, we create a hypothetical situation the program could be run through, and then we run through it ourselves based on that situation. This helps us to evaluate the program's real-world adaptibility, as well as help us to test many functions that are not frequently used or tested (or simply aren't tested thoroughly enough).

For this presentation, we will examine the shortcut commands in Mozilla by pretending to be a right-handed user whose right hand (or alternatively, a left-handed user whose left hand) is broken. This means the user will have difficulty using the mouse and will have to use shortcut commands, but it also means that when using these shortcut commands the user will only be able to use one hand. We have chosen this scenario because it would seem shortcut commands serve two primary purposes: to provide quick access to commands and to make the program accessible to disabled users. Testing for quick access is a simple enough test, however testing for accessibility requires the tester to be very understanding of the need the program is addressing, which is why scenario testing is key.

Scenario testing helps a tester place themselves into the position of the user, a task that is often very difficult. By working through a scenario test, a tester has certain conditions that help keep them more aware of certain ways a program acts. For instance, in this test, we are more aware of how the shortcut commands work now that we have a scenario that limits our ability to use a keyboard or mouse.

Performing the Test

  1. Open the Mozilla browser:

  2. Click on the horizontal menu options, such as File, Edit, View, etc. Look for shortcut commands next to actions. For example, under the File menu is the action Open Web Location, and next to that is printed Ctrl-Shift-L. That means instead of clicking on this menu option with a mouse, we could also use Ctrl-Shift-L to open up a website.
  3. Try out some of the other commands, such as Ctrl-U to view the source code,

Results/Relevance

For many of the shortcut commands, did it seem difficult to do them use only one hand? Now take into consideration that depending on the size of the user's hands, these could be very difficult commands if they could only use one hand. For example, Ctrl-U is very difficult to press with one hand, even for a user with large hands. For navigation, Alt-Left Arrow and Alt-Right Arrow were also very awkward and difficult to press with only one hand, more frustrating due to how often those commands would be used by the average user.

What is important when considering the results of this scenario test is that there is no work-around (no alternative the user could use in place of this). A user with a broken hand has no choice but to either only use the mouse or the keyboard, and either choice will be somewhat awkward. The program should, as best as possible, accommodate the user in navigating and commanding the program.

This is not critical and does not affect the file or program in any serious way, but it certainly presents an obstacle to ease of use. It also alienates disabled users from using the product.

Scenario testing allowed us to view the program through a different mindset, one through which many of the customers might also be viewing the program. By scenario testing, we have a much better chance of understanding how customers will feel using the program and how we can help make it easier to use the program.

Similar Tests/Additional Notes

Try using some of the other Internet browsers, such as Opera or Internet Explorer, and look through the shortcuts. Are most of them the same? The commands that differ, how do they differ? Are they easier or harder to use? Easier or harder to remember? For Opera, you might also look at their newest shortcut command system, mouse gestures, which allows the user to move the mouse in certain patterns to perform actions.

Configuration Notes

Testing Mozilla's Internet Suite v1.4.1 on:

Created 26 May 2004 for the CSTER

All images and written material ©Copyright Sam Oswald 2004

This work is licensed under the Creative Commons Attribution-ShareAlike License.
To view a copy of this license, visit
http://creativecommons.org/licenses/by-sa/2.0/
or send a letter to
Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305,
USA.