Clarify whether "WebView unsupported" is a failure of SC 1.3.5

[mitchellevan]

Currently

I haven't seen this happen in the wild yet, but I notice in the code that a toast message of "WebView unsupported" is possible. This message might mean that the app being tested does not support autofill via a webview, or it might mean that the InputPurposeAutofill tool does not support testing of certain kinds of webviews. Without this clarity, a tester won't know whether to report a failure of SC 1.3.5 Input Purpose or report an indeterminate result.

Proposed

Make the message clearer and/or explain it in documentation for the tool.

[mitchellevan]

By the way, this issue has not actually caused me any problems. Today I was testing a login page embedded in a webview, and I did not get the "WebView unsupported" message. I did get "Autofill hint: on", which I've reported as a failure of SC 1.3.5 in the app I was testing. So it seems webviews are not always unsupported.

@jwlilly I'm mentioning my experience for the first time using this tool, for context and as one of the cases that might be worth explaining in instructions for the tool. Thanks for developing this useful tool!

[jwlilly]

When you get a few minutes, can you test that in the chrome app with some pages that have the autocomplete attribute assigned properly? They may have updated chrome to properly support this. (Webviews are just a stripped down chrome usually)

[mitchellevan]

Trying on this page: Contact TPGi. Inspecting in desktop browser DOM tools I see correct autocomplete attributes, like autocomplete="given-name". In Chrome (Pixel 7a, Android 15) the InputPurposeAutofill tool reports "WebView unsupported" when I tap the fields.

This was on the same Android device where earlier today I got "Autofill hint: on" for a webview not in a browser. The app is confidential so I'll message you separately about that.

[jwlilly]

I wouldn't consider this a failure of 1.3.5. WebViews (at least the default Chrome WebView) doesn't expose the autofill property. Its just not testable without looking at the HTML to see the autocomplete value.

I would file this as an issue with user agents rather than an issue for a developer to fix