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.

中文翻译：

---

持续集成和自动辅助功能测试中当前软件工程实践的简要概述

长期以来，人们一直接受软件工程中的持续集成（CI）提高了从业人员对其的遵守程度，从而提高了企业项目的代码质量。但是，是否有任何旨在提高代码质量和速度的工作来改善软件可访问性呢？文献中引用了哪些潜在的好处？它是否适合大多数企业中团队运作的现代敏捷方式？本文试图描绘出通过持续集成来改善可访问性所花费的软件工程工作的当前状况，这是研究人员所引用的障碍。