Empowering Agile Project Members with Accessibility Testing Tools: A Case Study

There is a growing interest in making software more accessible for everyone, which is emphasized by the numerous suggestions passed into law in many countries. However, many software organizations that use agile methods postpone or neglect accessibility testing. We aimed to understand how accessibility testing can be better integrated into the daily routine of agile projects by conducting a case study in a Norwegian software company. We investigated three accessibility testing tools: automatic checker, simulation glasses, and a dyslexia simulator. We hosted sessions at which agile project members used the tools while thinking out loud, responded to questionnaires, and were interviewed at the end. Additionally, we observed the project members for 18 workdays. Our results show that all three tools are suitable for agile projects. Especially the automatic checker and simulation glasses worked well in finding accessibility issues and were described as easy to use by the project members. Software organizations should empower their agile project members with low-cost and efficient accessibility testing tools to make their products more accessible for all. Doing this early and often in the development cycle may save the project from potential high costs at a later stage.

[1]  Lourdes Moreno,et al.  Toward an Integration of Web Accessibility into Testing Processes , 2013, DSAI.

[2]  Gregg C. Vanderheiden,et al.  Accessible design and testing in the application development process: considerations for an integrated approach , 2008, Universal Access in the Information Society.

[3]  Robert Biddle,et al.  Agile Development Iterations and UI Design , 2007, Agile 2007 (AGILE 2007).

[4]  John Eklund,et al.  Usability in Agile development , 2008 .

[5]  R. Edwards,et al.  What Is Qualitative Interviewing , 2013 .

[6]  Viktoria Stray,et al.  Agile Digital Transformation: A Case Study of Interdependencies , 2018, International Conference on Interaction Sciences.

[7]  Christine Nadel,et al.  Case Study Research Design And Methods , 2016 .

[8]  Randolph G. Bias,et al.  Cost-Justifying Usability: An Update for the Internet Age , 2005 .

[9]  Esther Derby,et al.  Agile Retrospectives: Making Good Teams Great , 2006 .

[10]  James B. Dabney,et al.  Error Cost Escalation Through the Project Life Cycle , 2004 .

[11]  Helen Petrie,et al.  The Evaluation of Accessibility, Usability, and User Experience , 2009, The Universal Access Handbook.

[12]  Aleksander Bai,et al.  Categorization and Comparison of Accessibility Testing Methods for Software Development. , 2018, Studies in health technology and informatics.

[13]  Viktoria Stray,et al.  A Cost-Benefit Analysis of Accessibility Testing in Agile Software Development: Results from a Multiple Case Study , 2017 .

[14]  Agustín Yagüe,et al.  Agile User Stories Enriched with Usability , 2012, XP.

[15]  A. D. Angeli,et al.  Focal Points for a More User-Centred Agile Development , 2016, XP.

[16]  Neil A. M. Maiden,et al.  Towards a Framework for Integrating Agile Development and User-Centred Design , 2006, XP.

[17]  Viktoria Stray,et al.  Autonomous agile teams: challenges and future directions for research , 2018, XP Companion.

[18]  Sylwia Męcfal Recenzja książki. Robert K. yin, Case Study Research. Design and Methods (fourth Edition), thousand Oaks, CA: Sage Publications, 2009 , 2012 .

[19]  James B. Dabney,et al.  8.4.2 Error Cost Escalation Through the Project Life Cycle , 2004 .

[20]  David Kane,et al.  Finding a place for discount usability engineering in agile development: throwing down the gauntlet , 2003, Proceedings of the Agile Development Conference, 2003. ADC 2003.

[21]  Sergio Luján-Mora,et al.  Integration of Web Accessibility into Agile Methods , 2012, ICEIS.

[22]  Gerard Meszaros,et al.  Adding usability testing to an agile project , 2006, AGILE 2006 (AGILE'06).

[23]  Viktoria Stray,et al.  Daily Stand-Up Meetings: Start Breaking the Rules , 2018, IEEE Software.