This bug was fixed in the package gnome-initial-setup -
49~beta.1-0ubuntu1
---------------
gnome-initial-setup (49~beta.1-0ubuntu1) questing; urgency=medium
* New upstream release
* d/control: Depend on gnome-session 49.beta
* d/control: Drop unused dependency on gnome-keyring
* d/p/a11y-Notify-bad-username.patch: Drop patch applied upstream
* d/p: Rebase patches
gnome-initial-setup (49~alpha-0ubuntu2) questing; urgency=medium
* a11y: Notify through the screen reader any error message about
invalid user names in the About you page (LP: #2116935)
-- Alessandro Astone <[email protected]> Thu, 07 Aug
2025 11:15:55 +0200
** Changed in: gnome-initial-setup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-initial-setup in Ubuntu.
https://bugs.launchpad.net/bugs/2116935
Title:
No accessibility in errors during user data intro
Status in gnome-initial-setup package in Ubuntu:
Fix Released
Bug description:
In the `About you` page, where a new user is created, if there is an
error, it is shown in a line below, but nothing is said by the screen
reader.
There is a pending patch that fixes this:
https://gitlab.gnome.org/GNOME/gnome-initial-
setup/-/merge_requests/278
[ Impact ]
An user that relies on the screen reader won't be able to know that
the user name selected is not valid.
[ Test plan ]
* create a virtual machine to avoid spoiling your system and launch it
* open a terminal in the virtual machine
* run `export UNDER_JHBUILD=1` to enable the testing mode
* run `export XDG_CURRENT_DESKTOP=GNOME`
* enable the screen reader
* launch gnome-initial setup with `/usr/libexec/gnome-initial-setup`
* press the `Next` button until you arrive to the `About you` page
* set, as the username, your current user name to force an error. Under
the entry, you must see the error message `Sorry, that username isn't
available. Please try another.`
* if the patch doesn't work, you should hear nothing, but if the patch
works, then the screen reader should read the error message out loud.
[ Where problems could occur ]
Since this patch uses `gtk_accessible_announce()` method, it can happen
that any other screen reader message sent immediately after can "overwrite"
the error message, thus preventing the user to receive the expected info.
Also, since there is logic to avoid repeating the same message over and
over, an error in this logic can either:
- make the same message be read over and over
- make the message be read once when in a different page
- make the message not be read when it should
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2116935/+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
