• Skip to content
  • Skip to link menu
KDE Usability Project
  • KDE Usability Project / Current Projects / Usability Reports
 
 

Accessibility Meets Usability Weekend

Project name:Accessibility Meets Usability Weekend
Software version:KDE Accessibility Features - KDE 3.5 under Ubuntu 5.10
Usability engineer:Ellen Reitmayr and Tina Trillitzsch
Project maintainer(s) at time of test:Olaf and Gunnar Schmidt, Gary Cramblitt
Date of report:May 2006
Related URL:Accessibility meets Usability Weekend - Full Report (PDF, 2,5 MB)
Accessibility meets Usability Weekend - Report on the KDE Screen Magnifier (PDF, 1,4 MB)
Executive Summary:

In user tests with three partially sighted and two blind users, the accessibility features of KDE and Gnome were tested. As a general conclusion we found that while both KDE and Gnome provide very good tools to make the Linux desktop usable for partially sighted and blind users, they are lacking consistent support among the major desktop applications. In KDE, key applications like the text editor Kate or the shell Konsole did not apply high contrast colour schemes; in Gnome, the contents of crucial tools like the software installation (Ubuntu) could not be read by Gnopernicus and were therefore "invisible" for the blind users.

Many of the described problems could be avoided if you try to keep the following guidelines in mind while developing:

  • Use scroll panels -
    with extremely high font sizes, a panel's height may exceed the screen height. If you do not provide scrollbars, the panels are likely to be "cut off" and a user will not be able to reach all contents without resizing.
  • Make dialogs resizable -
    if a dialog is not resizable and has no scrollbars, users may be unable to reach contents at the bottom. Make dialogs resizable anyway to allow every user to reach the confirmation buttons.
  • Make scrollbars exclude the tabs -
    to keep the tabs as navigational device visible on the screen, set the scrollbar below the tab navigation.
  • Avoid complex and visually cluttered user interfaces -
    for example double-nested group boxes, checkbox and button deserts, or overcrowded toolbars. Otherwise it is especially hard for partially sighted users to keep track of related items.
  • Avoid fixed background colours or images -
    make them adjust to the overall colour scheme (except there are compelling reasons not to do so).
  • Allow your contents to adjust to the overall colour scheme -
    you do not need to default the contents to the overall colour scheme, but allow the user to manually do so in an easy way.
  • Make all interface elements accessible via the keyboard -
    fancy html widgets are cool, but make sure they are accessible.
  • Use the standard interfaces and widgets -
    to make sure your application is and will be accessible later, use standard interfaces and widgets.
Success story:

The Accessibility meets Usability Weekend strengthened the collaboration between accessibility and usability in KDE and resulted in a number of guidelines and concepts.

[ Edit ]

Information

Skip menu "Information"
  • KDE Usability Home
  • KDE.org Home
  • About the Project
  • People Involved
  • Frequently Asked Questions
  • News Archives

Communication

Skip menu "Communication"
  • Contact Us
  • Mailing List
  • Contributing

Development

Skip menu "Development"
  • Current Projects
  • Human Interface Guidelines
  • Usability Reports

Explore

Skip menu "Explore"
  • Usability Resources
  • Books on Human Factors
  • Projects & Associations

Global navigation links

  • KDE Home
  • KDE Accessibility Home
  • Description of Access Keys
  • Back to content
  • Back to menu

Search:


Maintained by usability.kde.org Webmaster
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V. | Legal