A button lacks the A11Y role

[Sergio Costas]

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, 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.

[Nick Rosbrook (enr0n)]

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.

[Nick Rosbrook (enr0n)]

Hello Sergio, or anyone else affected,

Accepted malcontent into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/malcontent/0.11.1-1ubuntu1.2 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-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. 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.

[Launchpad Janitor (janitor)]

This bug was fixed in the package malcontent - 0.13.0-1ubuntu2

---------------
malcontent (0.13.0-1ubuntu2) questing; urgency=medium

  * d/p/ui-Fix-wrong-a11y-role-in-button.patch:
    - Fix wrong a11y role in button (lp: #2116954)

 -- Sergio Costas Rodriguez <email address hidden> Wed, 16 Jul 2025 10:50:45 +0200

[Sergio Costas (rastersoft-gmail)]

I'll check it right now. Give me a moment, please.

[Sergio Costas (rastersoft-gmail)]

I tested in Noble. Opened a terminal, installed everything, launched `malcontent-control`, and unlocked it. It showed the main interface. I enabled the screen reader and navigated using the TAB key. When I arrived to the `Restrict applications` button, the reader said "Underline Restrict applications PUSHBUTTON" as expected for the patch working.

[Sergio Costas (rastersoft-gmail)]

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.

[Nick Rosbrook (enr0n)]

This is currently blocked on ppc64el FTBFS on plucky. I have just retried the build, because it failed without logs.

Sergio - please remember to flip the $RELEASE specific verification tag (plucky in this case still said verification needed).

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted malcontent (0.13.0-1ubuntu1.1) for plucky have finished running.
The following regressions have been reported in tests triggered by the package:

flatpak/unknown (ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/plucky/update_excuses.html#malcontent

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Launchpad Janitor (janitor)]

This bug was fixed in the package malcontent - 0.13.0-1ubuntu1.1

---------------
malcontent (0.13.0-1ubuntu1.1) plucky; urgency=medium

  * d/p/ui-Fix-wrong-a11y-role-in-button.patch:
    - Fix wrong a11y role in button (lp: #2116954)

 -- Sergio Costas Rodriguez <email address hidden> Wed, 16 Jul 2025 10:59:27 +0200

[Andreas Hasenack (ahasenack)]

The verification of the Stable Release Update for malcontent has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package malcontent - 0.11.1-1ubuntu1.2

---------------
malcontent (0.11.1-1ubuntu1.2) noble; urgency=medium

  * d/p/ui-Fix-wrong-a11y-role-in-button.patch:
    - Fix wrong a11y role in button (lp: #2116954)

 -- Sergio Costas Rodriguez <email address hidden> Wed, 16 Jul 2025 11:23:10 +0200