Note that the bug above suggests a different accessibility service too:

"But there are other services that modify content as well. For example, https://developer.android.com/training/accessibility/testing.html lists Voice Access:

"Voice Access lets users control an Android device with spoken commands. Voice Access is available in a limited English-only beta on devices running Android 5.0 (API level 21) and higher. To test your app with Voice Access, learn how to install and turn on Voice Access."

The Voice Access Play Store page (https://play.google.com/store/apps/details?id=com.google.android.apps.accessibility.voiceaccess) says it has 1M - 5M installs."

I'm puzzled by the phrase, "using talkback as a screen reader". TalkBack /is/ a screen reader.

What corner cases are we obligated to test which are not covered by TalkBack?

Does Clank test with any accessibility services other than TalkBack?

You're referring to b/64951517#comment18, which says "TalkBack is just one implementation of accessibility services, and it provides 'read-only' accessibility, i.e., it reads contents of the screen and convert to speech, but it does not modify the contents of the screen." That's incorrect. With TalkBack on, there's a different set of gestures (touch-to-explore, double-tap, 2-finger scroll, etc.) which allow you to perform all the same actions as when TalkBack is off. If this claim is the basis for our belief that testing with TalkBack is insufficient, then there's nothing we need to do here.

the cornercase is the bug itself, see b/64951517 comment #1 and #22. 

I do not believe clank tests with any other accessibility services. 

for your comment on #18: IMO, one of these are correct:

1. Talkback can be used to test for the case that they are bringing in the bug, but we don't know how to test it

2. Talkback is not a full implementation as they claim in #20, and we need to test using a different accessibility service

3. Their test case is wrong

If you can help me untangle this, I appreciate :)

If I'm understanding correctly, the relevant thing Talkback doesn't do, but which accessibility supports, is directly modifying the state of input fields via the accessibility APIs. Talkback just defers to the IME for this (you use the regular keyboard, with speech feedback to let you know which keys you're hitting).

The accessibility service inserting text into fields needs to be treated as a user gesture, because the accessibility service is presumed to be the user's agent.

There's no such thing as a "full" vs "not full" implementation of accessibility services here - there's a bunch of different APIs and different services use different subsets, because they're supporting different accessibility requirements and user preferences.

(for example, Voice Access supports saying "type hello" into the microphone, and it will enter "hello" into the currently focused field directly, without the IME being involved)

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot