Skip to main content
Log in

Accessible design and testing in the application development process: considerations for an integrated approach

  • Long Paper
  • Published:
Universal Access in the Information Society Aims and scope Submit manuscript

Abstract

Accessible design principles should permeate virtually all phases of the application development cycle, using existing “best practices of software engineering” for accessibility purposes. This paper proposes a methodology for accessible design and testing that includes proven tools of software engineering, namely use cases and scenarios, to capture functional requirements. Guidelines developed through user testing and heuristics are made real using personas to exemplify accessibility requirements, reflecting a diversity of user capabilities and use contexts. For implementation and testing, test cases containing accessibility checkpoints are generated, based on the guidelines. Complementary to this methodology, expert reviews and user testing should be conducted for evaluation of the developed products and further refinement of the development process.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8
Fig. 9

Similar content being viewed by others

Notes

  1. Superstitious behavior occurs whenever someone does something in a certain way that has no correlation to facts—just because it worked that way before. For example, someone who always turns their phone off and back on at the end of a call because once they were unable to hang up without turning the phone off. Or someone who always deletes and reenters information into a new record rather than just editing the old record. Or someone that designs everything with a certain spacing because that was the rule of thumb they were given and they do not know what the basis was for deciding that spacing, so they just continue to do what they used to do (even if it is not necessary anymore—and even if it is not sufficient or correct anymore).

References

  1. Antle A.: Child-user abstractions. In: CHI ‘06 Extended Abstracts on Human Factors in Computing Systems, Montréal, Québec, Canada, pp. 478–483. ACM, New York (2006)

  2. Aoyama, M.: Persona-and-scenario based requirements engineering for software embedded in digital consumer products. In: Proceedings 13th of the IEEE International Conference on Requirements Engineering, pp. 85–94, 29 August–2 September 2005

  3. Chisholm, W., Vanderheiden, G., Jacobs, I.: Web Content Accessibility Guidelines 1.0, W3C Recommendation, 5 May 1999. http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/

  4. Cooper, A.: The Inmates are Running the Asylum. SAMS/Macmillan, Indiana (1999)

  5. Dantin, U.: Application of personas in user interface design for educational software. In: Proceedings of the 7th Australasian Conference on Computing Education, vol. 42, Newcastle, NSW, Australia. ACM International Conference Proceeding Series, vol. 106, pp. 239–247 (2005)

  6. Dayton, D.: Audiences involved, imagined, and invoked: trends in user-centered interactive information design. Proceedings of Professional Communication Conference, 21–24 Sept. 2003, pp. 327–335. IEEE International (2003)

  7. Hackos, J., Redish J.: User and Task Analysis for Interface Design. Wiley, New York (1998)

    Google Scholar 

  8. Heumann, J.: Generating Test Cases from Use Cases. Rational edge, June 2001. http://www-106.ibm.com/developerworks/rational/library/content/RationalEdge/jun01/GeneratingTestCasesFromUseCasesJune01.pdf

  9. HFES 200 Committee: Draft Standard for Trial Use: Human Factors Engineering of Software User Interfaces (BSR/HFES 200). Human Factors and Ergonomics Society, Santa Monica (2003, in revision 2006)

  10. ISO TS 16071:2003: Ergonomics of Human–System Interaction—Guidance on Accessibility for Human–Computer Interfaces

  11. Jacobson, I.: Object-Oriented Software Engineering: A Use-Case Driven Approach. Addison-Wesley, Reading (1992)

    MATH  Google Scholar 

  12. Kruchten, P.: The Rational Unified Process—An Introduction. Addison-Wesley, Reading (2004)

  13. Microsoft (2004) The Wide Range of Abilities and Its Impact on Computer Technology. Research Study by Microsoft, conducted by Forrester Research. http://www.microsoft.com/enable

  14. Mueller, J.: Getting personal with universal. Innovation, 23(1) (2004). http://www.idsa.org/webmodules/articles/articlefiles/Mueller.pdf

  15. Newell, A., Mueller, J., and Jones, M.: Promoting user sensitive inclusive design: strategies for communicating user needs to designers. In: Gibson, L., Gregor, P., Sloan, D. Accessible Design in the Digital World Conference 2005, Workshops in Computing (eWIC) Series (ISSN 1477-9358). British Computer Society, Wiltshire

  16. Norman D.A.: The Invisible Computer. Why Good Products Can Fail, the Personal Computer Is So Complex, and Information Appliances are the Solution. MIT, Cambridge (1998)

    Google Scholar 

  17. Pruitt J., Grudin J.: Personas: practice and theory. In: Proceedings of the 2003 Conference on Designing for User Experiences, San Francisco, California, pp 1–15. ACM, New York (2003)

    Chapter  Google Scholar 

  18. Randolph, G.: Use-cases and personas: a case study in light-weight user interaction design for small development projects. Inform Sci J 7,105–116 (2004)

    Google Scholar 

  19. Rönkkö, K.: An empirical study demonstrating how different design constraints, project organization and contexts limited the utility of personas. In: Proceedings of the 38th Annual Hawaii International Conference on System Sciences. IEEE International, Washington, DC, USA, 3–6 January 2005

  20. Sesto, M., Vanderheiden, G., Radwin, R.: Functional Characterization of Disability and Interface Use. RESNA 27th Annual Conference, Orlando, Florida (2004)

  21. Schmidt, A., Terrenghi, L.: Methods and guidelines for the design and development of domestic ubiquitous computing applications. In: Fifth Annual IEEE International Conference on Pervasive Computing and Communications, pp. 97–107, March 2007

  22. Shyba L., Tam J.: Developing character personas and scenarios: vital steps in theatrical performance and HCI goal-directed design. In: Proceedings of the 5th Conference on Creativity and Cognition, pp. 187–194. ACM, New York (2005)

    Chapter  Google Scholar 

  23. Souza, R. Design Accessible Sites Now, Forrester Report, December 2001. http://www.forrester.com/ER/Research/Report/Summary/0,1338,11431,00.html

  24. Vanderheiden, G.: Application Software Design Guidelines, Version 1.1, 1 June 1994. Trace Center. http://trace.wisc.edu/docs/software_guidelines/software.htm

  25. Yu, Y., Liu, Z.: Research on a user-centered design method for interactive online teaching system. In: ICCT ‘06. International Conference on Communication Technology, pp. 1–4, November 2006

  26. Zimmermann, G.: Access Technologies Group—Resources. http://www.accesstechnologiesgroup.com/Resources (2006)

Download references

Acknowledgments

This work was partially funded by the National Institute on Disability and Rehabilitation Research, US Department of Education under Grant H133E030012 as part of the Universal Interface and Information Technology Access Rehabilitation Engineering Research Center of the University of Wisconsin -Trace Center. The opinions herein are those of the authors and not necessarily those of the funding agency.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Gottfried Zimmermann.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Zimmermann, G., Vanderheiden, G. Accessible design and testing in the application development process: considerations for an integrated approach. Univ Access Inf Soc 7, 117–128 (2008). https://doi.org/10.1007/s10209-007-0108-6

Download citation

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s10209-007-0108-6

Keywords

Navigation