[Paper Review] A Brief Survey of Current Software Engineering Practices in Continuous Integration and Automated Accessibility Testing

Parth Sane|arXiv (Cornell University)|Feb 26, 2021

Digital Accessibility for Disabilities23 references9 citations

TL;DR

This paper surveys current practices in integrating automated accessibility testing within continuous integration (CI) and continuous delivery (CD) pipelines, proposing a visual workflow for CI-based accessibility testing and a training framework for agile teams. It demonstrates that embedding accessibility testing in CI/CD improves code quality, reduces technical debt, and enables early issue detection, with key contributions including Fig. 1 (CI accessibility testing pipeline) and Fig. 2 (training cycle diagram).

ABSTRACT

It's long been accepted that continuous integration (CI) in software engineering increases the code quality of enterprise projects when adhered to by it's practitioners. But is any of that effort to increase code quality and velocity directed towards improving software accessibility accommodations? What are the potential benefits quoted in literature? Does it fit with the modern agile way that teams operate in most enterprises? This paper attempts to map the current scene of the software engineering effort spent on improving accessibility via continuous integration and it's hurdles to adoption as quoted by researchers. We also try to explore steps that agile teams may take to train members on how to implement accessibility testing and introduce key diagrams to visualize processes to implement CI based accessibility testing procedures in the software development lifecycle.

Motivation & Objective

• To investigate how accessibility testing is currently integrated into CI/CD pipelines in enterprise software development.
• To identify barriers and enablers for adopting automated accessibility testing in agile environments.
• To propose practical workflows and training models to help agile teams implement accessibility testing effectively.
• To evaluate the benefits of integrating accessibility testing into CI/CD from both technical and business perspectives.

Proposed method

• Conducted a literature review of academic and industry sources on CI/CD, accessibility testing, and agile methodologies.
• Mapped existing accessibility testing tools and their integration capabilities with CI/CD platforms such as GitLab.
• Proposed a visual workflow (Fig. 1) for integrating automated accessibility tests into the CI pipeline using tools like AXE.
• Developed a pseudo-use-case diagram (Fig. 2) to model a sustainable training cycle for developers on accessibility.
• Evaluated training models such as Adobe and Teach Access for applicability in corporate agile environments.
• Analyzed qualitative findings from studies on developer awareness, tooling limitations, and organizational adoption barriers.

Experimental results

Research questions

• RQ1 RQ1: What are the challenges to adopting automated accessibility testing in CI/CD pipelines?
• RQ2 RQ2: Which software accessibility tools can be integrated into CI/CD pipelines for automated testing?
• RQ3 RQ3: What are the measurable benefits of implementing accessibility testing in CI/CD?
• RQ4 RQ4: Can accessibility testing be effectively incorporated into agile development methodologies?
• RQ5 RQ5: How can agile teams adopt accessibility testing if their members lack prior familiarity?

Key findings

• Accessibility testing is more cost-effective when integrated early in development, reducing long-term technical debt.
• Tools like the IBM Mobile Accessibility Checker detect 67% of accessibility issues, supporting the use of automated tools in CI.
• Quantitative metrics such as Inaccessible Element Rate (IAER) and Accessibility Issue Rate (AIR) can benchmark accessibility levels.
• Agile teams can integrate automated accessibility tests into their CI/CD pipelines by treating them as part of standard unit testing workflows.
• Training models like Adobe’s 8-hour engineering course and Teach Access’s train-the-trainer approach improve developer competence and awareness.
• Physical simulation tools (e.g., Cambridge Simulation Glasses, dyslexia simulators) and personas help developers empathize with users with disabilities.