Documentation - Add comparison with Accessibility Scanner about a11y-ally HOT 2 OPEN

Greetings. From what I've seen so far, the great advantage of a11y is using it as a background service. Meanwhile, another tool / technique exploits the mobile application. In the end, we have the accessibility report as a result. Example: start recording a11y, run monkey (random testing tool), stop recording a11y. Would the disadvantage of a11y be the evaluated accessibility criteria? Scanner evaluates a greater number of accessibility criteria, but requires manual interaction by the tester. Was it something along those lines?

from a11y-ally.

Hey, I haven't looked into putting this together yet but A11y Ally aims to be a super set of the current Accessibility Scanner features.

• Real-time highlighting of issues (like Accessibility Scanner supports)
• Report generation
• Accessibility feature x-ray (like displaying contentDescriptions)
• Linear Navigation as an alternative app consumption experience

When looking into using screen recording techniques to detect other accessibility issues like text size or color contrast, I discovered that one of the big disadvantages of real-time highlighting was that displaying that there are issues on top of the live app caused a feedback loop where A11y Ally would detect or be blocked from detecting issues like text size or color contrast by the very feedback boxes it drew on the screen. This may be one of the reasons the existing tooling doesn't do real-time highlighting.

Despite the setbacks on real-time highlighting, I plan on doubling down on the other, more unique experiences my app provides. I think in the end, A11y Ally will no longer compete with Accessibility Scanner in terms of rules, but instead focus on raising visibility into other, more subjective aspects of accessibility.

@neves01, does this answer your question? If you have used A11y Ally already, what were you using it for and did it serve you well?

from a11y-ally.