Talkback reading of ExposedDropdownMenuBox does not work like the layout system and is buggy [257209915]

Fixed

Bug

Status Update

No update yet.

Description

da...@well.co

created issue #1

Nov 3, 2022 04:17PM

Jetpack Compose version: 1.3.0 Jetpack Compose component used: ExposedDropdownMenuBox,TextField Android Studio Build: 2022.1.1 Canary 2 Kotlin version: 1.7.10

How the layout system would read a dropdown

Focus on drop down it reads: "[SELECTION] drop down list [Drop Down Label]. Double tap to change."
Click on Drop down it reads: "Popup window [FIRST SELECTION] in list. Double tap to activate"
Scroll to second option in popup window it reads: "[SECOND SELECTION] double tap to activate"
Select second option in drop down it reads: "[SECOND SELECTION] drop down list [Drop Down Label]. Double tap to change."

Which the above is pretty reasonable

Compose for the same situation and configuration reads:

Focus on drop down it reads: "drop down menu double tap to activate."
Click on Drop down it reads: Nothing but if you swipe again it reads "[FIRST SELECTION] EditBox Label. Then if you swipe again it reads the Label "Blah 2" as you can see in the video. Swipe again "Window popup window" then swipe again
Scroll to second option in popup window it reads: "[SECOND SELECTION] double tap to activate"
Select second option in drop down it reads: "2 replaced 1" then moves focus to the text below which is "Blah2"

So there is multiple things wrong above. I am not saying it needs to be the same as layout system but the same or better.

Also if you look at second 0:40-0:50 you will see it reads out the drop down and edit box separately. This is not working like a user would expect.

This is a really bad UX and I think the only reasonable work around is to use the layout system for all drop downs.

Appreciate you looking into this ADA issue.

XRecorder_03112022_110635.mp4

1.7 MB

Download

Comments

da...@well.co <da...@well.co> #2Nov 3, 2022 04:18PM

There is a report about it in kotlinlang Slack: https://kotlinlang.slack.com/archives/C01D6HTPATV/p1706005056105739

co...@google.com <co...@google.com> #3Nov 9, 2022 06:34PM

Thanks for the report!

da...@well.co <da...@well.co> #4Nov 9, 2022 07:36PM

The release notes documentation has been edited to clarify this change in behavior for line height.

To support non-standard text sizes, we encourage users to follow the Material design system and use a different type scale rather than changing the font size directly. Alternatively, users can overwrite the line height like so: style = LocalTextStyle.current.copy(lineHeight = TextUnit.Unspecified), or create a custom Typography entirely.

ya...@well.co <ya...@well.co> #5Oct 18, 2023 01:36PM

deleted

ya...@well.co <ya...@well.co> #6Nov 2, 2023 01:29PM

In my case, I have multiple font sizes in the same Text (using SpanStyle in AnnotatedString). There are legitimate reasons for this. For example, when combining Chinese and English (phonetic) together (for language-learning purposes).

da...@gmail.com <da...@gmail.com> #7Nov 4, 2023 07:28AM

dependencies { implementation "androidx.compose.material:material:1.5.4" }

android { buildFeatures { compose true }

composeOptions {
    kotlinCompilerExtensionVersion = "1.5.3"
}

kotlinOptions {
    jvmTarget = "1.8"
}

}

ap...@google.com <ap...@google.com> #8Apr 5, 2024 07:26PM

Marked as fixed.

Project: platform/frameworks/support
Branch: androidx-main

commit b01be1f0984e1ae035582524be989edc14b83b42
Author: Max Alfonso-Ying <maxying@google.com>
Date: Fri Apr 05 00:22:27 2024

Improve a11y of editable ExposedDropdownMenus

Updated `Modifier.menuAnchor` to support icons in addition
to text fields. Now takes a parameter for MenuAnchorType
so we can set popup flags accordingly. Also added an enabled
parameter to control if the anchor is enabled.

This means editable EDMs can use 2 menu anchors to
support both flows of typing and direct selection when
a11y services are enabled.

Updated sample to show this usage.

Fixes:

b/257209915

b/308840226

Test: Added unit tests for enabled/disabled menuAnchor. Manual testing with TalkBack
Relnote: "`ExposedDropdownMenuBoxScope` no longer permits subclasses.
Exposed dropdown menus now have a `MenuAnchorType` which
should be passed to `menuAnchor` to support better a11y.
This should be used instead of passing `focusable` to
`ExposedDropdownMenu`, which is now deprecated.
`menuAnchor` has a new parameter to control `enabled` state."
Change-Id: I55ee632daf66ef4df90297350cbff901e26ea446

M compose/material3/benchmark/src/androidTest/java/androidx/compose/material3/benchmark/ExposedDropdownMenuBenchmark.kt
M compose/material3/material3/api/current.txt
M compose/material3/material3/api/restricted_current.txt
M compose/material3/material3/samples/src/main/java/androidx/compose/material3/samples/ExposedDropdownMenuSamples.kt
M compose/material3/material3/src/androidInstrumentedTest/kotlin/androidx/compose/material3/ExposedDropdownMenuTest.kt
M compose/material3/material3/src/androidMain/kotlin/androidx/compose/material3/ExposedDropdownMenu.android.kt
M compose/material3/material3/src/androidMain/kotlin/androidx/compose/material3/internal/Strings.android.kt
M compose/material3/material3/src/androidMain/res/values/strings.xml
M compose/material3/material3/src/commonMain/kotlin/androidx/compose/material3/internal/Strings.kt
M compose/material3/material3/src/desktopMain/kotlin/androidx/compose/material3/internal/Strings.desktop.kt

https://android-review.googlesource.com/3028145

na...@google.com <na...@google.com> #9Apr 17, 2024 05:17PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.compose.material3:material3:1.3.0-alpha05
androidx.compose.material3:material3-android:1.3.0-alpha05
androidx.compose.material3:material3-desktop:1.3.0-alpha05