Public bug reported: 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. [ 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. ** Affects: gtk4 (Ubuntu) Importance: Undecided Assignee: Sergio Costas (rastersoft-gmail) Status: New ** Affects: gtk4 (Ubuntu Noble) Importance: Undecided Status: New ** Tags: noble verification-needed-noble ** 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. [ 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. ** Also affects: gtk4 (Ubuntu Noble) Importance: Undecided Status: New ** Tags added: noble verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2119005 Title: Accessibility groups aren't honored in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2119005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
