I wish there was a unified back end for accessibility that screen readers could plug into and other accessibility automated tools.
Their domain use cases are close in use but not the same. However, automation for testing has money behind it. Perhaps the use case could be bridged where both domains could benefit.
Very interesting point. I'm aware of the Microsoft UI Automation interface, which at least on Windows I think does exactly this: https://en.wikipedia.org/wiki/Microsoft_UI_Automation - and most Windows UI test-automation tools depend on this.
Their domain use cases are close in use but not the same. However, automation for testing has money behind it. Perhaps the use case could be bridged where both domains could benefit.
reply