  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.
