Accessibility: Missing labels on workout input fields and action buttons

[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 (like TalkBack) more effectively.

I’ve been exploring wger and noticed some accessibility barriers on the Log/Workout Entry screen, so I wanted to propose a fix.

1. The Issue

On the Workout Entry and Configuration screens, several input fields (where users enter weights, repetitions, or search for exercises) present the following behavior:

• Current behavior: The fields lack persistent visual labels or clear instructions that remain available once the user starts typing (violating WCAG 3.3.2 Labels or Instructions).
• Impact: Users with cognitive impairments or those using screen readers may lose track of what each numerical field represents (e.g., distinguishing between "weight" and "reps") after interacting with them.

2. Proposed Solution

To fix this, I suggest using TextInputLayout to provide floating labels, or ensuring each EditText is explicitly linked to a TextView label using android:labelFor.

Code snippet / XML suggestion:

<TextView
    android:id="@+id/weight_label"
    android:text="@string/weight_kg"
    android:labelFor="@+id/weight_input" />
<EditText
    android:id="@+id/weight_input"
    ... />

3. Additional fixes (Need your input)

I have identified 1 other accessibility improvement on this screen.

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

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

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

Best regards,

[rolandgeider]

Hi Ana!

You are right, accessibility has not really been a priority (like in most places I fear). Since this is a flutter app, we won't be able to use those xml snippets, but there's probably a solution in flutter. I would say we collect all the places were you find something here, then we can see how to proceeed