debcrafters-packages team mailing list archive

[Launchpad Bug Tracker <2119005@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package gtk4 - 4.14.5+ds-0ubuntu0.4

---------------
gtk4 (4.14.5+ds-0ubuntu0.4) noble; urgency=medium

  * d/p/skip-s390-tests-lp2119291.patch: skip some gtk4 tests that are failing
    only on s390x (LP: #2119291)
  * Revert: "d/rules: skip some more s390x tests."

gtk4 (4.14.5+ds-0ubuntu0.3) noble; urgency=medium

  * d/rules: skip some more s390x tests. (LP: #2119291)

gtk4 (4.14.5+ds-0ubuntu0.2) noble; urgency=medium

  * Fix accessibility groups (LP: #2119005)

 -- Andreas Hasenack <andreas@xxxxxxxxxxxxx>  Sat, 02 Aug 2025 14:10:23
-0300

** Changed in: gtk4 (Ubuntu Noble)
       Status: Fix Committed => Fix Released

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

Title:
  Accessibility groups aren't honored in Noble

Status in gtk4 package in Ubuntu:
  Fix Released
Status in gtk4 source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  In Noble, after the last Gtk4 update, some accessibility details have
  stopped working. Specifically, when a container is marked as a group
  and an inner element gets the focus, now the screen reader only reads
  the label of the focused element. Before, if the focus went from
  outside the group to inside, the label of the group element was read
  before, thus helping to get context.

  The bug is due to the change of the ATSPI_ROLE value for
  GTK_ACCESSIBLE_ROLE_GROUP, from PANEL to GROUPING. The version of the
  `orca` screen reader in Noble does not support ATSPI_ROLE_GROUPING, so
  revert back to ATSPI_ROLE_PANEL.

  This bug affects all those users that rely on a screen reader. The
  screen reader will not give enough context to know where the focus is,
  which can make more complex for them to navigate and use the computer.

  [ Test plan ]

  * Enable the screen reader
  * Open Gnome Control Center
  * Go to System -> Users
  * Using the keyboard TAB and cursors, go to the "Unlock" button
  * If the bug has been fixed, the screen reader should say first "Some options are locked" and only then "Unlock pushbutton". If the bug is still there, only "Unlock pushbutton" will be read.

  [ Where problems could occur ]

  The change only affects users that rely on screen readers.
  Regressions would be observed in the screen reader announcements of nested UI elements.

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