topic Re: Accessibility Bug: search in playlist on Android in Android

Accessibility Bug: search in playlist on Android

JR_8000 — Thu, 26 Mar 2026 21:42:44 GMT

Accessibility bug Android

Re: Accessibility Bug: search in playlist on Android

JR_8000 — Thu, 26 Mar 2026 21:46:58 GMT

Android: “Search in playlist” not accessible with TalkBack
•
TalkBack cannot find or focus the “Search in playlist” field
•
Explore by touch does not reveal it
•
External keyboard cannot access it
•
Feature is unusable with screen reader
This is a core function and currently broken for accessibility.
. Spotify has neglected accessibility again once more as a no surprising action from their side. Spotify versio 9.1.34.2060 Android 15 Moto G55 but very likely with all Android phones I presume due to very badly designed and inferior interface with screen readers. Talkback 16.2. Logitech K380 or HP350, Gboard versio 16.9.1.873986071-release-arm64-v8a Please also note: if this message is not prepared properly the Talkback tells me as a blind paying customer "Please correct the highlighted fields before proceeding." Highlighted is a graphical aspect not recognised by a screen reader. am sorry for being a blind customer on this platform.

Re: Accessibility Bug: search in playlist on Android

MihailY — Fri, 27 Mar 2026 09:34:48 GMT

Hey @JR_8000,

We're sorry to hear about the issues you're experiencing with our service and the Spotify Community page.

Accessibility has always been a top priority here at Spotify and we're always looking for ways to improve. That being said, we appreciate you taking the time to reach out and share your thoughts on this with us and we've made the right team aware of these two issues.

While our team looks into things further backstage, we'd be more than happy to answer any other questions you may have.

Re: Accessibility Bug: search in playlist on Android

JR_8000 — Fri, 27 Mar 2026 10:55:22 GMT

Thank you for Your message. One way of implementing the Search in playlist function is to place it under the "Three dots menu". I am not exactly sure but it seems that the current implementation could now be having a certain focus on screen area which just shows the search field on the top of the screen and if it is a focused-based implementation it is a pure challenge for screen reader applications.