You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Accessibility: Redundant descriptions on decorative elements and critical UI fixes #40
Hi! I’m Ana Ferreira, a Master's student in Computer Science.
As part of my research on mobile accessibility, I am analyzing open-source Android applications to help identify and correct accessibility barriers so users can utilize assistive technologies more effectively.
I’ve been exploring Logline - MovieApp and identified several accessibility issues on the Movie Discovery and Details screens, so I wanted to propose a fix.
1. The Issue
On the Main Discovery Screen, several decorative elements (such as background posters or divider icons) present the following behavior:
Current behavior: Non-essential or purely decorative images have been assigned content descriptions. TalkBack announces them, interrupting the flow of information (violating WCAG 1.1.1 Non-text Content).
Impact: This creates "auditory clutter" for blind users, making it harder to find the actual content (movie titles/summaries) amidst unnecessary descriptions of decorative assets.
2. Proposed Solution
To fix this, I suggest setting android:contentDescription="@null" or android:importantForAccessibility="no" for all non-interactive and purely decorative elements.
thanks a lot for analyzing my app and for pointing out these accessibility issues you noticed.
Accessibility is an area I care about, but I haven’t had the time or resources to properly address it yet. So your concrete feedback is genuinely helpful. I am not sure when I'll find the time to implement a fix for that, but I’ll definitely keep this in mind for future updates
Feel free to share the other accessibility improvements you identified here in this issue.
Activity
Patch4Code commentedon Feb 4, 2026
Hey there,
thanks a lot for analyzing my app and for pointing out these accessibility issues you noticed.
Accessibility is an area I care about, but I haven’t had the time or resources to properly address it yet. So your concrete feedback is genuinely helpful. I am not sure when I'll find the time to implement a fix for that, but I’ll definitely keep this in mind for future updates
Feel free to share the other accessibility improvements you identified here in this issue.
Thanks again for your feedback :)