debcrafters-packages team mailing list archive

[Sergio Costas <2119005@xxxxxxxxxxxxxxxxxx>]

Installed `libgtk-4-1/noble-proposed` in my clean 24.04 VM and enabled
the screen reader. Then I opened Gnome Settings and, using the keyboard,
navigated to System->Users, and there to the `Unlock` button. As it
should, the screen reader said "Some options are locked Panel; Unlock
Pushbutton". To fully confirm that everything worked as expected, also
deleted the `~/.config/gnome-initial-setup-done` file, logged out, and
logged in again. I was greeted with `gnome-initial-setup`, and this time
the screen reader correctly read the titles and subtitles in each page,
as it should.

So I consider that the patch works as expected.

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

-- 
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 Committed

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