mabl Introduces Automated Accessibility Testing To Mitigate Brand and Compliance Risks

mabl has announced the beta release of its automated accessibility testing feature, which is now integrated within the company's software-as-a-service (SaaS) platform for application testing. This move comes at a time when organizations are increasingly facing the need to meet accessibility requirements early in the application development life cycle to avoid liabilities and potential brand reputation damage stemming from noncompliance with Web Content Accessibility Guidelines (WCAG).

Dan Belcher, co-founder of mabl, explained that alongside the increasing prevalence of accessibility requirements in various compliance mandates there is an accelerated need to cover such issues at the beginning stages of the application development life cycle. Failing to address these requirements can leave organizations vulnerable to not only regulatory repercussions but also negative publicity on public social media forums.

In response to these concerns, the mabl SaaS platform enables the creation of reusable tests using a low-code engine known as axe-core. With this feature, organizations can easily incorporate these tests into their DevOps workflows. This approach allows dedicated testing teams to develop tests without being directly reliant on a DevOps platform.

Belcher highlighted the importance of considering end users with disabilities within the ever-expanding digital landscape. He noted that the software industry as a whole is only starting to consider accessibility as a top priority. Ideally, fast feedback via accessibility regression tests encompassing contrast checks should be implemented. While he believes that automated accessibility tests are unlikely to replace periodic audits by subject matter experts, Belcher expressed hope that up to 50% of accessibility issues identified in WCAG guidelines could one day be addressed through automation. This would help prevent the buildup of accessibility debt and reduce overall costs associated with addressing such issues post-application deployment.

Belcher further emphasized that, although automation is unlikely to ever completely replace dedicated testing teams, platforms like mabl are designed to help finite testing resources cope with rapidly accelerating application development. Accessibility remains a vital component of any comprehensive software quality review; recognizing this fact will go a long way in preventing organizations from having to apologize for shortcomings at a later stage.

While mabl is working on improving accessibility compliance through automation, no-code platforms such as AppMaster have significantly reduced barriers to application development. These platforms facilitate the creation of web and mobile applications, ensuring a more inclusive ecosystem for all users in the process.