HorizontalPager accessibility focus issues [354109776]

Fixed

Bug

Status Update

No update yet.

Description

np...@mirego.com

created issue #1

Jul 19, 2024 02:11PM

Versioning and Device Details

Jetpack Compose version: 1.7.0-beta05
Android Studio Build: Android Studio Koala | 2024.1.1 RC 2
Kotlin version: 1.9.0

Device Model: Pixel 8
Android Version: 14
TalkBack Version: 14.2

Issue Description

The accessibility focus does not navigate between pages, in our case the pager is nested in a scrollable column but I could reproduce it with this minimal reproduction case:

Scaffold(modifier = Modifier.fillMaxSize()) { innerPadding ->
	HorizontalPager(
		modifier = Modifier
			.padding(innerPadding)
			.fillMaxWidth(),
		state = rememberPagerState {
			10
		}) {
		Text(
			text = "Page $it",
			modifier = Modifier
				.fillMaxWidth()
				.background(Color.Gray)
				.padding(16.dp)
		)
	}
}

Expected behavior:

The accessibility focus should focus on the next / previous page when swiping left and right with accessibility gestures. Additionally it should say the number of items.

Actual behavior:

The accessibility focus does not focus on next our previous page, it also does not return the number of items.

Steps to Reproduce or Code Sample to Reproduce:

Run PagerAccessibility-focus project attached to bug report.
Run sample with talkback and try to focus to next page.
Notice it won't work with 1.7.0-beta05 but it does with 1.6.8

You can swap out these lines in the libs.version.toml to notice the changed behavior from the previous compose stable release.

#androidx-compose-bom = { group = "dev.chrisbanes.compose", name = "compose-bom", version = "2024.07.00-alpha01" }
androidx-compose-bom = { group = "androidx.compose", name = "compose-bom", version = "2024.06.00" }

PagerAccessibility-focus.zip

395 KB

Download

Comments

mo...@google.com <mo...@google.com> #2Jul 19, 2024 05:20PM

Reassigned to le...@google.com.

We have some support in androidx.compose.ui.autofill

Leaving this bug open in case Ralston wants to add more info

le...@google.com <le...@google.com> #3Jul 24, 2024 01:54PM

I found an example here. One problem is that it only works with the Google autofill service. When using any other service like Microsoft Authenticator or OneKey, the following error is shown:

D/Autofill Status: Autofill popup isn't shown because autofill is not available.
    
    Did you set up autofill?
    1. Go to Settings > System > Languages&input > Advanced > Autofill Service
    2. Pick a service
    
    Did you add an account?
    1. Go to Settings > System > Languages&input > Advanced
    2. Click on the settings icon next to the Autofill Service
    3. Add your account

Is this a bug on your side or do the app developers of these password managers need to change their implementation?

mo...@johnlewis.co.uk <mo...@johnlewis.co.uk> #4Sep 9, 2024 07:50PM

Another problem I am facing with autofill is that it won't save my credentials. I tried forcing to finish the context as described here, but it won't do that either although I filled in the username with the one provided by the Google autofill service.

le...@google.com <le...@google.com> #5Sep 10, 2024 07:34AM

deleted

ap...@google.com <ap...@google.com> #6Sep 20, 2024 06:51AM

Marked as fixed.

Facing the same issue here, Google autofill service seems to work. Zero documentation on adding support for Autofill framework on jetpack compose.

pr...@google.com <pr...@google.com> #7Oct 2, 2024 05:37PM

Hello, I am trying to implement the same thing - it seems like there's no way for current password managers like 1Password or Bitwarden, to automatically pick up the fields. Is there a possible solution?