Skip to content

Accessibility: Redundant descriptions on decorative elements and critical UI fixes #40

Open

Description

@AnaFerreira015

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.

Code snippet / XML suggestion:

<ImageView
    ...
    android:contentDescription="@null"
    android:importantForAccessibility="no" />

3. Additional fixes (Need your input)

I have identified 6 other accessibility improvements for Logline.

To avoid spamming your notification feed, how would you prefer I submit these?

  • Option A: List them all here in this issue (I can update the comment below).
  • Option B: Open separate issues for each specific problem.

Please let me know your preference, and I will proceed accordingly.

Best regards,

Activity

  1. added
    UI/UX FeedbackFeedback and suggestions related to UI/UX design and aesthetics
    on Feb 4, 2026
  2. Patch4Code commented on Feb 4, 2026

    @Patch4Code
    Owner

    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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    UI/UX FeedbackFeedback and suggestions related to UI/UX design and aesthetics

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions