-
Notifications
You must be signed in to change notification settings - Fork 162
Description
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 Binary Eye (specifically the Scan, History, and Compose screens) and found a specific issue, so I wanted to propose a fix.
1. The Issue
On the Scan Code screen (or History screen), the 'Save scan history' toggle presents the following behavior:
- Current behavior: The element lacks a descriptive text label. TalkBack announces it simply as "Unlabelled" or "Button", violating WCAG 4.1.2 (Name, Role, Value).
- Impact: Users relying on screen readers cannot distinguish this control from others or understand its function without trial and error.
2. Proposed Solution
To fix this, I suggest adding an android:contentDescription to the element in the XML layout.
Code snippet / XML suggestion:
<ImageButton
...
android:contentDescription="@string/action_description" />3. Additional fixes (Need your input)
I have identified 3 other categories of accessibility improvements across the History, Scan, and Compose screens.
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.
I can provide detailed fixes for these upon request.
Please let me know your preference, and I will proceed accordingly.
Best regards,