I tested it in Plucky now. Opened a terminal, installed the packages
from `proposed`, launched `malcontent-control`, and unlocked it. It
showed the main interface. I enabled the screen reader and navigated to
the `Restrict applications` button using the TAB key. The reader said
"Underline Restrict applications BUTTON", which confirmed that the patch
fixes the bug. Notice the difference in role names between Noble and
Plucky.

** Description changed:

  The "Restrict Applications" button lacks the corresponding role,
  so an user using a screen reader won't be able to know that they
  can push it to expand the list of applications.
  
  [ Impact ]
  
  An user that depends on the screen reader won't know the associated role
  of the button, which can be misleading and make use more difficult.
  
  [ Test plan ]
  
  * In a virtual machine, open a terminal
- * Install `malcontent` and `malcontent-gui` packages.
+ * Install `malcontent` and `malcontent-gui` packages, along with 
`libmalcontent-0-0` and `libmalcontent-ui-1-1`.
  * type `export XDG_CURRENT_DESKTOP=GNOME` and `export UNDER_JHBUILD=1` to set 
debug mode and pure-gnome mode in gnome-initial-setup.
  * enable the screen reader (Super+Alt+S)
  * launch `malcontent-control`.
  * unlock it with your SUDO password.
  * move the cursor, using the TAB key, to the `Restrict applications` button
  * without the patch, it will be read as `Restrict applications. Prevents 
specified...`, without a role.
    Instead, with the patch, it should be read as `Restrict applications 
Button. Prevents specified...`
  
  [ Where problems could occur ]
  
  Since this patch only adds A11Y info, the only possible problem is that
  incorrect accessibility information would be sent to the screen reader.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2116954

Title:
  A button lacks the A11Y role

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to