Accessibility: use labels
Greetings,
you may not be aware of it, but Mumla is hugely useful
for visually-impaired users (did you know, for example,
that it’s the only Mumble client that allows to move
users between channels without using a pointing device?).
Mumla is entirely usable through TalkBack, without any
visual input -- which is awesome. However, that level
of accessibility is greatly hindered by the lack of labels
on nearly all interface items (menus, buttons, etc.).
You can reproduce that issue by turning on TalkBack (without
disabling the screen), and opening Mumla in that mode: by
single-finger swiping to navigate through the interface,
all you’re likely to hear is: “Unlabeled button”, “Unlabeled
button”, and so on.
Another way of auditing that issue (as recommended by Google)
is to use their Accessibility Scanner; after scanning Mumla it then
highlights all interface items for which no labels are available.
A workaround is, with recent TalkBack versions, to go to its
“Verbosity” settings and enable “Speak element IDs for unlabeled
buttons” (disabled by default). It makes Mumbla much easier
to use without visual information.
A very basic (if somewhat inelegant) way to fix that problem
would be to use the strings you already have for android:title
as android:contentDescription
and/or android:hint
where
appropriate. That way you can build upon the existing translations.