tails issueshttps://gitlab.tails.boum.org/tails/tails/-/issues2024-02-27T14:50:37Zhttps://gitlab.tails.boum.org/tails/tails/-/issues/20231Changing locale in the Welcome Screen doesn't change it for Accessibility menu2024-02-27T14:50:37ZboyskaChanging locale in the Welcome Screen doesn't change it for Accessibility menu... nor for the date widget or anything else, actually
<img src="/uploads/a181fd8a8fac4534956b479677a7474c/Screenshot_tails-amd64-6.0_2024-02-27_12_49_58.png" width="300px" />... nor for the date widget or anything else, actually
<img src="/uploads/a181fd8a8fac4534956b479677a7474c/Screenshot_tails-amd64-6.0_2024-02-27_12_49_58.png" width="300px" />https://gitlab.tails.boum.org/tails/tails/-/issues/19907Orca doesn't change language while in the Welcome Screen2024-02-27T12:35:37Zsajolidasajolida@pimienta.orgOrca doesn't change language while in the Welcome ScreenIf I activate the screen reader in the Welcome Screen and change the language to "Spanish", for example, Orca reads Spanish text with an English voice, which is not really understandable. Orca reads Spanish fine with a Spanish voice once...If I activate the screen reader in the Welcome Screen and change the language to "Spanish", for example, Orca reads Spanish text with an English voice, which is not really understandable. Orca reads Spanish fine with a Spanish voice once on the GNOME desktop.https://gitlab.tails.boum.org/tails/tails/-/issues/19906Sound indication when getting to the Welcome Screen2024-02-26T10:56:38Zsajolidasajolida@pimienta.orgSound indication when getting to the Welcome ScreenFrom #18989:
We recommend to offer a sound indication (music or beat sound) to let users know that the operative system is fully loaded and ready to use.
If this works correctly, this may be a solution for blind users to being able to i...From #18989:
We recommend to offer a sound indication (music or beat sound) to let users know that the operative system is fully loaded and ready to use.
If this works correctly, this may be a solution for blind users to being able to install independently if they know the shortcut to start the screen reader.
We probably don't want to "sound like Tails" not to raise too much attention, but a simple and neutral *beep* could help. For example, /usr/share/sounds/gnome/default/alerts/drip.ogg.
I guess that the same reasoning should apply to the Boot Menu: could we play a system beep when GRUB loads to reassure blind users that Tails is loading?https://gitlab.tails.boum.org/tails/tails/-/issues/19904Document basic keyboard shortcuts for accessibility in more places2024-01-03T18:19:14Zsajolidasajolida@pimienta.orgDocument basic keyboard shortcuts for accessibility in more placesFrom #18989:
While we were doing our keyboard and screen reader testing, we had to try different combination of shortcuts and try to study and understand the current shortcuts defined on the System Tools.
For instance, Alt+Space shortc...From #18989:
While we were doing our keyboard and screen reader testing, we had to try different combination of shortcuts and try to study and understand the current shortcuts defined on the System Tools.
For instance, Alt+Space shortcut opens RESIZE MENU (close, maximize, minimize, etc.) in all windows (options that are not receiving focus with Tab key) but users that do not have previous knowledge of that shortcut may think it is not accessible. The same logic applies with other shortcuts like Alt+Super+S to turn screen reader on or off. Or Ctrl+Alt+Tab for universal access menu.
There is a webpage with Tails accessibility information but it may be a good idea to add some basic shortcuts.
Additional to that, it may be a good idea also to add this information or instructions message on some screen reader accessibility section inside Tails, not only on the documentation webpage. This way the user can have the info on site at the right time.https://gitlab.tails.boum.org/tails/tails/-/issues/19903WhisperBack text input fields are not read by Orca2023-07-20T20:15:28Zsajolidasajolida@pimienta.orgWhisperBack text input fields are not read by OrcaFrom #18989:
The screen reader announces “TEXT” to indicate that is an input field, but it does not mention the label, so blind users don’t know.From #18989:
The screen reader announces “TEXT” to indicate that is an input field, but it does not mention the label, so blind users don’t know.https://gitlab.tails.boum.org/tails/tails/-/issues/19596Unsafe Browser - Sandbox escape by sniffing audio of the host system - deanon...2023-08-01T15:33:04ZboyskaUnsafe Browser - Sandbox escape by sniffing audio of the host system - deanonymization of Tor usersFrom https://git.radicallyopensecurity.com/ros/pen-tails/-/issues/15
> I found a trivial way to sniff the audio inside the unsafe-browser sandbox. The threat scenario is that someone gets RCE inside the unsafe-browser sandbox. As you sa...From https://git.radicallyopensecurity.com/ros/pen-tails/-/issues/15
> I found a trivial way to sniff the audio inside the unsafe-browser sandbox. The threat scenario is that someone gets RCE inside the unsafe-browser sandbox. As you said, it is not a big deal unless someone can correlate the "clear" Ip with the TOR activities. Taking screenshots doesn't work, and all other gnome-* raise errors. But the audio sniffing works fine, as shown in the following picture. Please note that I use the GUI because this tool has no CLI interface. However, I could build my GTK application or load custom modules inside the gnome-sound-recorder app!https://gitlab.tails.boum.org/tails/tails/-/issues/19572Tor Browser ignores cursor size (accessibility issue)2023-06-12T08:57:18Zsajolidasajolida@pimienta.orgTor Browser ignores cursor size (accessibility issue)In GNOME, users can configure a bigger cursor size for accessibility with, for example:
gsettings set org.gnome.desktop.interface cursor-size 64
This settings works fine in Thunderbird but doesn't work in Tor Browser.
This setting...In GNOME, users can configure a bigger cursor size for accessibility with, for example:
gsettings set org.gnome.desktop.interface cursor-size 64
This settings works fine in Thunderbird but doesn't work in Tor Browser.
This settings used to work fine in Tails 5.7, so I guess that's it's a regression related to Wayland.https://gitlab.tails.boum.org/tails/tails/-/issues/19266"Large text" accessibility feature does not apply to Tor Browser since 5.8~beta12023-06-12T08:54:37Zintrigeri"Large text" accessibility feature does not apply to Tor Browser since 5.8~beta1https://gitlab.tails.boum.org/tails/tails/-/issues/19199Have a background image that feels less old-fashioned and nerdy2024-02-06T18:49:41Zsajolidasajolida@pimienta.orgHave a background image that feels less old-fashioned and nerdyI've heard similar feedback about a first impression of Tails several times in the past month already:
Tails looks minimal and nerdy:
- [Lucas](https://tails.boum.org/contribute/how/user_experience/interviews/lucas) told me that he lik...I've heard similar feedback about a first impression of Tails several times in the past month already:
Tails looks minimal and nerdy:
- [Lucas](https://tails.boum.org/contribute/how/user_experience/interviews/lucas) told me that he liked:
> The minimalist interface. I'm fed up with the thousands of notifications of Windows, the popups, news, ads, weather apps, etc.
>
> I like that everything was a bit square. It felt like the 90's, without so many animations and things. Tails has this aesthetic clarity, like in video games where aesthetics support clarity, playability, and understanding of what you are doing.
>
> For example, the cursor goes above the different elements without animations or that you can only see one thing at a time and not multiple layers of windows.
- During #18784, commented on the interface, while waiting for a dead slow progress bar (#19173), saying:
> The interface is very minimalist. The plain blue screen. It feels like I'm opening a different computer after I restarted. I'm in another kind of Mac. It feels like I'm entering a different universe. This minimalist thing reminds me a lot of the aesthetics of a programming interface and a safe place. If I restarted and it looked like Mac, I might mistake one for the other. Now the distinction is very clear.
- During the workshop at Netzwerk Recherche, the only PC user also commented on the minimalist and nerdy look, though I don't have an exact quote.
I'm taking these comments with a grain of salt, because people might have toned down to sound more socially acceptable when talking to me as a Tails developer. But it seems to me that, going back to our [values and style](https://tails.boum.org/contribute/mission/), and in terms of emotions:
- Minimalist, clear, distinct, and safe are things that we want to keep
- Old-fashioned and nerdy are things that we should get rid of
Changing the look and feel of GNOME would be quite a lot of work, but changing our background image could be quite easy and might affect these perception a lot already.
- Tails/Tor icons are mostly purple and are clashing more and more with blue background and blue theme of GNOME.
I think that we should only work on this after we have #7148 to make it easier to do this change. Then:
1. Brainstorm a couple of possible new background images, building up on this feedback.
2. Test these few ideas, either
* Qualitatively during usability tests
* Quantitatively through a survey using the Microsoft Desirability Toolkit: https://www.nngroup.com/articles/microsoft-desirability-toolkit/
3. Consider using a custom theme with a color scheme that works better with purple than the default blue theme. This might also be better combined with #7148.https://gitlab.tails.boum.org/tails/tails/-/issues/18781Difficulty using Tor Connection assistant with screen of 800 px high or lower2024-03-01T09:23:38ZcbrownsteinDifficulty using Tor Connection assistant with screen of 800 px high or lowerHelp Desk received a report from a user (WB: c2c3fd1d77a963809059fd328258861d) complaining that it's difficult (I'm sure for many, impossible) to use the Tor Connection assistant with lower screen resolutions:
> I'm using VirtualBox 6.1...Help Desk received a report from a user (WB: c2c3fd1d77a963809059fd328258861d) complaining that it's difficult (I'm sure for many, impossible) to use the Tor Connection assistant with lower screen resolutions:
> I'm using VirtualBox 6.1.30 to run Tails 4.25 in a VM on a smaller 14"
> Win10 laptop with 1366x768 resolution. In more recent iterations of
> Tails, the new "Tor Connection" window that appears upon startup has
> elements of the window hidden by default. As it stands, the button(s)
> to proceed are hidden below the bottom of the screen and the window
> itself prevents movement or resizing by default. So, the buttons to
> proceed are inaccessible through mouse-click.
I also encounter this problem when testing new Tails releases in VirtualBox.
We don't specify a minimum screen resolution on our [system requirements](https://tails.boum.org/doc/about/requirements/) page.
The same problem happens when enabling the *Large text* option in the Accessibility menu.https://gitlab.tails.boum.org/tails/tails/-/issues/18181Have an accessibility statement on our website2021-02-18T18:15:17Zsajolidasajolida@pimienta.orgHave an accessibility statement on our websitehttps://www.w3.org/WAI/planning/statements/
Probably better done after #18083.https://www.w3.org/WAI/planning/statements/
Probably better done after #18083.https://gitlab.tails.boum.org/tails/tails/-/issues/18156Allow saving accessibility options from the Welcome Screen2024-02-27T12:35:36Zsajolidasajolida@pimienta.orgAllow saving accessibility options from the Welcome ScreenSplitting this out of #5501.Splitting this out of #5501.https://gitlab.tails.boum.org/tails/tails/-/issues/7511Add tests to check that accessibility features work fine2022-06-03T15:42:22ZmeganetAdd tests to check that accessibility features work fine_Originally created by @meganet on [#7511 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/7511)_
At least Orca should be tested.
### Related issues
- **Related to** tails/tails#12389_Originally created by @meganet on [#7511 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/7511)_
At least Orca should be tested.
### Related issues
- **Related to** tails/tails#12389https://gitlab.tails.boum.org/tails/tails/-/issues/7506Add header to the beginning of pages content2020-05-15T18:48:29ZpzajdaAdd header to the beginning of pages content_Originally created by @pzajda on [#7506 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/7506)_
Actually, there are headers in the content itself.
It could make the navigation easier if there was a level 1 header ..._Originally created by @pzajda on [#7506 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/7506)_
Actually, there are headers in the content itself.
It could make the navigation easier if there was a level 1 header (h1 in
HTML) at the beginning of the content of each pages, and why not, at the
top of the menu and before the footer.
### Related issues
- **Related to** tails/tails#7508pzajdapzajdahttps://gitlab.tails.boum.org/tails/tails/-/issues/7507Add WCAG quick navigation links2022-01-12T16:36:03ZpzajdaAdd WCAG quick navigation linksAdding quick navigation links (Jump to menu, content and footer) would
make navigation easier to find the exact part of a page.
Web Content Accessibility
Guidelines:
<http://www.w3.org/WAI/WCAG20/quickref/#navigation-mechanisms>
“Provid...Adding quick navigation links (Jump to menu, content and footer) would
make navigation easier to find the exact part of a page.
Web Content Accessibility
Guidelines:
<http://www.w3.org/WAI/WCAG20/quickref/#navigation-mechanisms>
“Providing mechanisms to navigate to different sections of the content
of a Web page”.
On the top of each HTML page you insert links to
jump to menu, content, footer (using an anchor). These links should be
hidden to normal users (using a CSS class, ie “screen-reader”) but will
be visible to screen readers, Braille readers etc.https://gitlab.tails.boum.org/tails/tails/-/issues/9732Orca cannot work with Electrum2021-03-22T16:19:31ZemmapeelOrca cannot work with Electrum_Originally created by @emmapeel on [#9732 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/9732)_
Reported by user:
steps to reproduce:
\- Turn Orca on
\- Open electrum
Orca cannot read it.
Parent Task..._Originally created by @emmapeel on [#9732 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/9732)_
Reported by user:
steps to reproduce:
\- Turn Orca on
\- Open electrum
Orca cannot read it.
Parent Task: tails/tails#14522
### Related issues
- **Related to** tails/tails#16969
- [x] **Blocked by** tails/tails#16421s7rs7rhttps://gitlab.tails.boum.org/tails/tails/-/issues/12384Forward Greeter accessibility settings to the GNOME session2024-02-27T11:22:16ZalantForward Greeter accessibility settings to the GNOME session_Originally created by @alant on [#12384 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12384)_
Accessibility support is getting better in the new Greeter, but the
settings chosen in the Greeter are not automatical..._Originally created by @alant on [#12384 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12384)_
Accessibility support is getting better in the new Greeter, but the
settings chosen in the Greeter are not automatically forwarded to the
GNOME session, so if one needs some accessibility tool, then they need
to enable it twice. And if they need help from someone else to do so,
then they need to request such help twice.
Relevant dconf settings, i.e. those one can modify from the Universal
Access menu (there’s more one can fine-tune in the Universal Access
settings panel but that’s irrelevant here as the user cannot do that in
the
Greeter):
- <https://sources.debian.net/src/gsettings-desktop-schemas/3.22.0-1/schemas/org.gnome.desktop.a11y.applications.gschema.xml.in/>
- <https://sources.debian.net/src/gsettings-desktop-schemas/3.22.0-1/schemas/org.gnome.desktop.a11y.keyboard.gschema.xml.in/>
Implementation resources:
- the [dconf for administrators (reference
doc)](https://wiki.gnome.org/Projects/dconf/SystemAdministrators)
- an [answer with more practical
approach](https://askubuntu.com/questions/416556/shouldnt-dconf-editor-and-gsettings-access-the-same-database#417330)
Parent Task: tails/tails#14522
### Related issues
- **Related to** tails/tails#7500https://gitlab.tails.boum.org/tails/tails/-/issues/14522Make Tails usable for blind users2021-08-03T11:40:47ZanonymMake Tails usable for blind users_Originally created by @anonym on [#14522 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14522)_
# Resources
- I’m told <https://accessibility.digital.gov/> is a great guide.
- [Practical hands-on accessibilit..._Originally created by @anonym on [#14522 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14522)_
# Resources
- I’m told <https://accessibility.digital.gov/> is a great guide.
- [Practical hands-on accessibility
testing](https://archive.org/details/lca2018-Practical_handson_accessibility_testing)
talk, by Nicolas Steenhout (LCA 2018)
- [gla11y](https://github.com/hypra/gla11y/) automatically checks accessibility of Glade `.ui` files
# Attachments
* [pan-down.png](https://redmine.tails.boum.org/code/attachments/download/2379/pan-down.png)
* [open-menu.png](https://redmine.tails.boum.org/code/attachments/download/2380/open-menu.png)
# Subtasks
- [ ] tails/tails#7502
- [ ] tails/tails#7503
- [x] tails/tails#9051
- [x] tails/tails#9260
- [ ] tails/tails#9732
- [ ] tails/tails#11664
- [x] tails/tails#12014
- [ ] tails/tails#12384
- [ ] tails/tails#16685
- [ ] tails/tails#16795
- [ ] tails/tails#17666
- [ ] tails/tails#17667https://gitlab.tails.boum.org/tails/tails/-/issues/16685The Upgrader GUI is not readable by Orca2020-05-15T13:06:57ZintrigeriThe Upgrader GUI is not readable by Orca_Originally created by @intrigeri on [#16685 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16685)_
Reported on tails-dev\\@
(\<6F6E8706-3D81-4281-96CD-F2026E53279C\\@gmail.com\>).
Parent Task: tails/tails..._Originally created by @intrigeri on [#16685 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16685)_
Reported on tails-dev\\@
(\<6F6E8706-3D81-4281-96CD-F2026E53279C\\@gmail.com\>).
Parent Task: tails/tails#14522