** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Committed
** Changed in: gnome-shell (Ubuntu)
Milestone: None => ubuntu-25.10
** Tags added: fixed-in-gnome-shell-49.alpha.1 fixed-upstream questing
** Also affects: gnome-shell (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Questing)
Importance: Undecided
Assignee: Sergio Costas (rastersoft-gmail)
Status: Fix Committed
** Also affects: gnome-shell (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu Oracular)
Status: New => Won't Fix
** Changed in: gnome-shell (Ubuntu Plucky)
Status: New => In Progress
** Changed in: gnome-shell (Ubuntu Noble)
Status: New => In Progress
** Changed in: gnome-shell (Ubuntu Plucky)
Milestone: None => plucky-updates
** Changed in: gnome-shell (Ubuntu Noble)
Milestone: None => noble-updates
** Changed in: gnome-shell (Ubuntu Questing)
Importance: Undecided => Medium
** Changed in: gnome-shell (Ubuntu Plucky)
Importance: Undecided => Medium
** Changed in: gnome-shell (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: gnome-shell (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: gnome-shell (Ubuntu Noble)
Assignee: (unassigned) => Sergio Costas (rastersoft-gmail)
** Changed in: gnome-shell (Ubuntu Plucky)
Assignee: (unassigned) => Sergio Costas (rastersoft-gmail)
** Tags added: a11y
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2115948
Title:
Accessibility issues in Gnome Shell/GDM/Unlock
Status in gnome-shell package in Ubuntu:
Fix Committed
Status in gnome-shell source package in Noble:
In Progress
Status in gnome-shell source package in Oracular:
Won't Fix
Status in gnome-shell source package in Plucky:
In Progress
Status in gnome-shell source package in Questing:
Fix Committed
Bug description:
Gnome Shell and GDM have several accessibility issues. Specifically:
* The Events element in the clock/date drop down window, with today events,
and the Weather element, with the weather in our location, lack accessibility
names.
* When there is an error during GDM login or unlock (for example, typing a
wrong password), a text message is shown, but nothing is said by the screen
reader.
* After clicking on “Not listed” in the GDM main page, an input is shown.
“Username” field has visible “Username” label (likely a placeholder), but is
not read by screen reader (only reads “text”, its role).
All these elements belong to Gnome Shell package.
[ Impact ]
An user that relies on a screen reader will lack a lot of context when
navigating the system, making it much harder to use the computer.
There are three patches that fix all this. Since all of them apply to
the same package, and all are related to accessibility, they have been
grouped in a single bug.
* https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3769 adds the
missing a11y labels to the Events and Weather elements.
* https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3765 emits a
spoken notification through the screen reader whenever an error is set in the
error widget in the GDM/Unlock screen.
* https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3179 sets the
widget a11y label pointing to the same label used in a St.Entry. This fixes not
only the "Username" lack of a11y, but any other similar case inside Gnome Shell.
[ Test plan ]
To reproduce the bug, first ensure that you have installed gnome-
clocks, gnome-weather and gnome-calendar.
* Logout of the current Gnome Shell session
* Enable the screen reader (just by pressing the key combination Super+Alt+S)
* Using TAB to navigate through the elements in GDM, go to "Not listed" and
press Return.
* A text entry with "Username" should appear, but the screen reader only says
"Entry". When the bug is fixed, it should say "Username entry".
* Type your user name, and when asked for the password, put a wrong one. An
error will be displayed, but the screen reader will say nothing. With the bug
fixed, it should read the error out loud.
* Enter your session and ensure that the screen reader is still enabled
* Expand the Notifications/Calendar drop down in the upper clock
* Using TAB and/or the cursor keys, navigate to the "Today" element with
today's appointments. The screen reader will say "Button". When the bug is
fixed, it should say "Today Button".
* Using TAB and/or the cursor keys, navigate to the "Weather" element. The
screen reader will say "Button". When the bug is fixed, it should say "Weather
Button".
[ Where problems could occur ]
All the cases just add accessibility labels, so, in general, any
possible problem should be just wrong accessibility data spoken
through the screen reader, but no impact is expected for the average
user.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2115948/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
