debcrafters-packages team mailing list archive

[Sergio Costas <2119005@xxxxxxxxxxxxxxxxxx>]

** Description changed:

  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 seems to be due to the change of the ATSPI_ROLE value for
  GTK_ACCESSIBLE_ROLE_GROUP, from PANEL to GROUPING. Reverting it seems to
  fix the bug.
+ 
+ This bug only affects Noble. Neither Plucky nor Questing are affected.
  
  [ Impact ]
  This bug affects to 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 ]
  
  Both ATSPI_ROLE_PANEL and ATSPI_ROLE_GROUPING are designed to specify a
  group of related elements. But for some reason, it seems that GROUPING,
  in Noble, doesn't respond as expected when there are nested elements,
  while PANEL does (https://docs.gtk.org/atspi2/enum.Role.html) so the
  only possible problems could be A11Y related, specifically with nested
  elements. Anyway, it should affect only users that rely on screen
  readers, and, at most, when notifying higher-scale labels or
  descriptions.

** Changed in: gtk4 (Ubuntu)
       Status: New => Invalid

-- 
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:
  Invalid
Status in gtk4 source package in Noble:
  In Progress

Bug description:
  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 seems to be due to the change of the ATSPI_ROLE value for
  GTK_ACCESSIBLE_ROLE_GROUP, from PANEL to GROUPING. Reverting it seems
  to fix the bug.

  This bug only affects Noble. Neither Plucky nor Questing are affected.

  [ Impact ]
  This bug affects to 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 ]

  Both ATSPI_ROLE_PANEL and ATSPI_ROLE_GROUPING are designed to specify
  a group of related elements. But for some reason, it seems that
  GROUPING, in Noble, doesn't respond as expected when there are nested
  elements, while PANEL does
  (https://docs.gtk.org/atspi2/enum.Role.html) so the only possible
  problems could be A11Y related, specifically with nested elements.
  Anyway, it should affect only users that rely on screen readers, and,
  at most, when notifying higher-scale labels or descriptions.

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