Colin Marsch

I've been investigating the possible resolutions to this issue and I wonder if the best path forward might be to simply disallow accessibility snapshots from being taken in the `SHRINK`...

ATF supports Compose accessibility checks on API 34+ per [this issue thread](https://github.com/google/Accessibility-Test-Framework-for-Android/issues/40#issuecomment-2127976675). ATF is also what is used under the hood in Android Studio for the Compose UI checks (also...

Just to provide an update here, I looked into this and it looks like it isn't just working out of the box unfortunately. Still have some more investigation to do...

> Any updates? Sorry for not providing an update on this earlier. The investigation that I mentioned above stalled and no more progress has been made on this. Beyond that...

Have you found any workarounds for this issue? Running into the same thing and it looks like others might be as well here: https://github.com/google/TestParameterInjector/issues/27

When does this error happen? Just trying to figure out why this fix might be needed

> this makes sense. what will this look like in practice (pointer to design doc/discussion maybe)? > > is the concept that enabling accessibility tests will automatically enable accessibility validation...

>I could see a case for keeping validation as a feature and extending it to support Compose "UI Checks" as there remain potential gaps from relying solely on the image...

> Nice, do you have an example of before and after where this is working? Maybe via a build scan I'm not exactly sure how to manually test this out....

> > I'm not exactly sure how to manually test this out. Do you have any thoughts here how to trigger a build scan or another way to verify this...