ubuntustudio-bugs team mailing list archive

[Launchpad Bug Tracker <1807221@xxxxxxxxxxxxxxxxxx>]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: pavucontrol (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to pavucontrol in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1807221

Title:
  suggestion: improving accessability of buttons pavucontrol

Status in pavucontrol package in Ubuntu:
  Confirmed

Bug description:
  Thanks for the application. This post is not about a  bug but a
  suggestion for improving the accessability of the buttons. As I do not
  know where to post suggestions, I post here (sorry if this isn't the
  right place).

  It took me a long time to figure out the meaning of the buttons of
  input devices. The set as fallback phrase was cryptic to me, I think I
  eventually understood that when it's dark grey, this means it's the
  default (terminology used by Skype for instance). But in light grey it
  still remains green ticked. In thunar for instance, the light grey is
  the active window, somewhat the inverse convention? Maybe it's green
  ticked because it's active? A separate green ticked button labelled
  default_input when this channel is set as default would be much
  clearer.

  Same applies to the mute button, when I click a red border appears in
  the browser and I initially got confused with the meaning of the
  button ; is it the action of muting/unmuting or the resulting state of
  the channel. Seems to me that a red cross for the muted state would be
  clearer and a green icon when unmuted. The label of the toggling
  button would be mute/unmute, not mute only.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/1807221/+subscriptions