Abstract
The Accessibility Passport has been developed to enable a dialogue between the specifier, developer, tester (including teacher/tutor) and user (student) of software or learning objects in development. By stating the original brief, the specifier can express what accessibility requirements were, or were not, expected to be included. The developer can outline any accessibility features built in and any user testing undertaken. Crucially users of the software or learning object (teachers and learners) can communicate their experiences back into the development process for future modifications or adaptations.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Kelly, B., Sloan, D., Brown, S., Seale, J., Petrie, H., Lauke, P., Ball, S.: Accessibility 2.0: People, Policies and Processes. In: WWW 2007, Banff, Canada (2007), www.w4a.info/2007/prog/15-kelly.pdf
Seale, J.: E-Learning and Disability in Higher Education. Routledge (2006)
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 2008 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Ball, S., Sewell, J. (2008). Accessibility Standards Are Not Always Enough: The Development of the Accessibility Passport. In: Miesenberger, K., Klaus, J., Zagler, W., Karshmer, A. (eds) Computers Helping People with Special Needs. ICCHP 2008. Lecture Notes in Computer Science, vol 5105. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-70540-6_39
Download citation
DOI: https://doi.org/10.1007/978-3-540-70540-6_39
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-70539-0
Online ISBN: 978-3-540-70540-6
eBook Packages: Computer ScienceComputer Science (R0)