Short answer

Embed accessibility checks and user testing with diverse groups throughout the agile development sprints, not just at the end.

Field
User-Centred Design
Source
Aaltodoc (Aalto University) (2019)
Method
Combined embedded single-case study and constructive research.
Sample
20 participants
Evidence
Moderate effect

Proactive integration of accessibility practices within agile software development frameworks is crucial for ensuring digital products are usable by a wider audience, including individuals with disabilities. This user-centred design research insight is drawn from a 2019 study published in Aaltodoc (Aalto University). Using Combined embedded single-case study and constructive research. with 20 participants, researchers explored how this design variable affects real-world outcomes. The key design takeaway: Embed accessibility checks and user testing with diverse groups throughout the agile development sprints, not just at the end.

Study
User-Centred DesignHigh ImpactModerate effect

Integrating Accessibility into Agile Software Development Boosts User Inclusivity

Proactive integration of accessibility practices within agile software development frameworks is crucial for ensuring digital products are usable by a wider audience, including individuals with disabilities.

Aaltodoc (Aalto University) · 2019

01

Key Findings

  • 01The current state of digital accessibility is often weak, with significant variation in understanding among practitioners.
  • 02An empathetic connection to people with disabilities can strongly influence the perceived importance and consideration of accessibility.
  • 03Lack of knowledge, understanding, resources, and current practices are significant challenges to accessibility.
  • 04Economic, societal, professional, and qualitative factors can motivate organizations and practitioners towards accessibility.
  • 05Accessibility knowledge, understanding, resources, and business/management support are enablers for accessibility realization.
02

Application

Design takeaway

Embed accessibility checks and user testing with diverse groups throughout the agile development sprints, not just at the end.

How to apply

Introduce accessibility checklists at each stage of the agile development process and conduct regular user testing with individuals representing diverse abilities.

Project actions

  • 01When researching user needs, actively seek out and include participants with diverse abilities.
  • 02Consider how your design choices might create barriers for certain user groups.
  • 03Document the accessibility considerations and testing throughout your design process.
03

Method & Evidence

AimTo define processes and practices that promote the realization of accessibility in agile software development.
MethodCombined embedded single-case study and constructive research.
ProcedureEmployees from a case company (N=20) were interviewed and observed, focusing on three product teams. The accessibility of three digital products from these teams was also evaluated. An accessibility improvement process was then constructed and its initial stages were evaluated.
Sample20 participants
ContextAgile software development within a digital product company.

Variables

IVImplementation of accessibility practices within agile software development.
DVRealization of accessibility in digital products.
CVCompany size, type of digital product, specific agile methodologies used.
04

Strengths & Limitations

Strengths

  • +Combines qualitative (interviews, observations) and quantitative (product evaluation) data.
  • +Constructive research approach leads to a practical output (Accessibility Improvement Process).

Limitations

A single case study might not reflect the challenges or successes of accessibility implementation in all agile teams. The evaluation of the proposed process was preliminary.

Reliability & validity

The use of multiple data collection methods (interviews, observations, product evaluation) enhances the validity of the findings. However, the single-case study design may limit external validity.

Think critically

How can the principles of agile development, which often prioritize speed and iteration, be effectively balanced with the thoroughness required for comprehensive accessibility implementation?

05

Design Principles

"Design for inclusivity by default; accessibility is a fundamental aspect of user-centered design."

As digital products become increasingly prevalent, overlooking accessibility excludes a significant portion of the user base. Implementing accessibility from the outset in agile processes ensures that diverse user needs are considered throughout the development lifecycle, leading to more equitable and widely adopted digital solutions.

06

What This Means for Your Design

Making sure digital products can be used by everyone, including people with disabilities, is important and needs to be built into how we create software quickly.

How to use in your project

  • 1.Reference this study when discussing the importance of user diversity and the need for inclusive design practices in your design project.
  • 2.Use the findings to justify the inclusion of accessibility testing and user research with diverse groups in your methodology.
07

Add to My Project

08

Quick Cite

Paragraph starter

This research underscores the critical need to embed accessibility practices within agile software development. Findings indicate that current accessibility implementation is often weak, with significant knowledge gaps among practitioners. The study proposes an 'Accessibility Improvement Process' to integrate accessibility into routine workflows, emphasizing that empathy, knowledge, resources, and organizational support are key enablers for creating inclusive digital products. This highlights the importance of proactive, user-centered design that considers diverse needs from the outset.

09

Source

Aaltodoc (Aalto University)

A Digital Society For All – Defining Accessibility Practices in Agile Software Development

journal · 2019

View source

Questions About This Research

What does the research say about integrating accessibility into agile software development boosts user inclusivity?
Embed accessibility checks and user testing with diverse groups throughout the agile development sprints, not just at the end. Evidence: Aaltodoc (Aalto University) (2019).
Why does "Integrating Accessibility into Agile Software Development Boosts User Inclusivity" matter for design?
As digital products become increasingly prevalent, overlooking accessibility excludes a significant portion of the user base. Implementing accessibility from the outset in agile processes ensures that diverse user needs are considered throughout the development lifecycle, leading to more equitable and widely adopted digital solutions.
How can designers apply this research?
Embed accessibility checks and user testing with diverse groups throughout the agile development sprints, not just at the end.
What were the main findings?
The current state of digital accessibility is often weak, with significant variation in understanding among practitioners.. An empathetic connection to people with disabilities can strongly influence the perceived importance and consideration of accessibility.. Lack of knowledge, understanding, resources, and current practices are significant challenges to accessibility.. Economic, societal, professional, and qualitative factors can motivate organizations and practitioners towards accessibility.
What research method was used?
Combined embedded single-case study and constructive research. with 20 participants.
How strong is the evidence?
Evidence strength is rated Moderate effect, based on a 2019 journal from Aaltodoc (Aalto University).
What should I do differently in my next project?
Introduce accessibility checklists at each stage of the agile development process and conduct regular user testing with individuals representing diverse abilities.
What are the limitations?
Findings are based on a single case study, which may limit generalizability to other organizational contexts. The constructed accessibility improvement process was only partially evaluated.