debcrafters-packages team mailing list archive
-
debcrafters-packages team
-
Mailing list archive
-
Message #04749
[Bug 2116166] Re: Tecla lacks accessibility when showing available keys
So the way translations work is:
- the package build calls dh_translations which refreshes the
translations template
example
https://launchpadlibrarian.net/722260790/buildlog_ubuntu-noble-amd64.tecla_46.0-1build1_BUILDING.txt.gz
dh_translations
ninja: Entering directory `/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[0/1] Running external command tecla-pot
- dh_translations produces a translations tarball
- launchpad imports the new template and update its list of strings to
translate
- translators work on those strings in the launchpad UI (they are shared
across series so if the patch backports a string existing in a new
version some translations might already exist and be used directly)
- those translations will be included in the next langpack refresh
We just had a langpack export for Noble .3 and seeing the timing it doesn't seem likely we will have translations for this point release even if the SRU is accepted.
New translations put aside having an english description is probably
still better than having no screen reader description, a non trivial
portion of our userbase understand english and that string describes
letters which might even be understandable by some non english
speakers...
--
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to tecla in Ubuntu.
https://bugs.launchpad.net/bugs/2116166
Title:
Tecla lacks accessibility when showing available keys
Status in tecla package in Ubuntu:
Fix Released
Status in tecla source package in Noble:
Incomplete
Status in tecla source package in Plucky:
Incomplete
Status in tecla source package in Questing:
Fix Released
Bug description:
[ Impact ]
An user that relies on a screen reader won't be able to know what
characters are available in each key combination.
This has been fixed upstream with
https://gitlab.gnome.org/GNOME/tecla/-/merge_requests/32
[ Test plan ]
* Enable the screen reader
* Launch `tecla`
* Press any key in the keyboard. A popup with the available characters will be shown, but the screen reader will say nothing. With the patch, it will read the (currently) four alternative characters generated by that key when pressed alone, with Shift, AltGr...
[ Where problems could occur ]
This patch just adds an accessibility label, 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/tecla/+bug/2116166/+subscriptions
References