debcrafters-packages team mailing list archive

[Nick Rosbrook <2116954@xxxxxxxxxxxxxxxxxx>]

Hello Sergio, or anyone else affected,

Accepted malcontent into plucky-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/malcontent/0.13.0-1ubuntu1.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
plucky to verification-done-plucky. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-plucky. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-plucky

** Tags added: verification-needed-noble

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

Title:
  A button lacks the A11Y role

Status in malcontent package in Ubuntu:
  Fix Committed
Status in malcontent source package in Noble:
  Fix Committed
Status in malcontent source package in Plucky:
  Fix Committed

Bug description:
  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
  * 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 `/usr/libexec/gnome-initial-setup`
  * advance until the `About you` page
  * add an user, different of the current one
  * enable the `Parental control` checkbutton
  * go to the next page
  * insert a password
  * go to the next page (parental controls)
  * 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.

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