1 / 8

Methodology for Accessibility Testing User Interface Design summer semester 2003/04

Methodology for Accessibility Testing User Interface Design summer semester 2003/04. Tomas Zanka Czech Technical University in Prague Czech Republic. Content. information validity result from real testing: I did cognitive walkthrough basics of cognitive walkthrough doing the tests

newton
Download Presentation

Methodology for Accessibility Testing User Interface Design summer semester 2003/04

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Methodology for Accessibility TestingUser Interface Designsummer semester 2003/04 Tomas Zanka Czech Technical University in Prague Czech Republic

  2. Content • information validity • result from real testing: I did cognitive walkthrough • basics of cognitive walkthrough • doing the tests • practical notes • more information

  3. Information validity This document is based on experiences with following applications: • NetBeans 3.5.1 • Java SDK 1.4.2_03 • Java Access Bridge 1.1_GA • JAWS 5.0 • all running on Windows 2000

  4. Results from real testing • I started intuitively with the testing. • While making work more and more systematical,I intuitively ended with small modification of cognitive walkthrough. • Cognitive walkthrough is methodology for testing user interfaces in general.

  5. Basics of cognitive walkthrough • 4 prerequisities: • system prototype or precise description • detailed user profile • list of tasks to be done by the user in the system • detailed list of actions for each task • 4 verification questions asked on each step: • Chooses user correct goal? • Is the action he should choose heard? • Is the chosen action the right one? • Understands user to feedback provided by the action?

  6. Doing the tests • detail action lists act here as checklists – can/cannot be done by blinds (+ why, limitations)(marking problem points is enough) • using display is desirable, but ONLY to: • check completeness of aural information(eg. disabled menu items are not read) • check consistency of visual & aural information(eg. code completion window appears, but blind user does not know about it) • bypass discovered problems and continue in testing(something cannot be done by keyboard, but further steps are clear)

  7. Practical notes • tester must maintain great selfcontrol and keep track of which information blind user (can) have • start with default configuration, alter it as a blind • work slowly and precisely - hurry leads to errors • try to use help as a blind when in trouble(may be you will discover problems with help, like I did) • analyse cause of problems(eg. it’s application/system-wide or local problem)

  8. More information • my work:http://taz.mystik.cz/Skola/NUR/(URL is case sensitive; index is in czech, but most linked pages are in english) • information on cognitive walkthrough:http://www.google.com/search?q=cognitive+walkthrough

More Related