Feature #14522

Make Tails usable for blind users

Added by anonym 2017-08-30 09:49:39 . Updated 2020-05-07 09:19:34 .

Status:
Confirmed
Priority:
Normal
Assignee:
intrigeri
Category:
Accessibility
Target version:
2020
Start date:
2014-07-06
Due date:
% Done:

21%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

anonym will review.

Resources:

Files

pan-down.png (197 B) sajolida, 2019-06-28 14:51:51
open-menu.png (181 B) sajolida, 2019-06-28 14:51:52

Subtasks

Bug #7502: Unsafe Browser is not accessible Confirmed

20
Bug #7503: The Persistent Volume Assistant is not readable by Orca Confirmed

0
Bug #9051: Tor Launcher is not accessible Confirmed

30
Bug #9260: Orca reads neither Tor Browser nor Thunderbird if started after it Resolved

100
Bug #9732: Orca cannot work with Electrum Confirmed s7r

0
Feature #11664: Improve usability of the Greeter with a screenreader Confirmed alant

0
Bug #12014: Tails Installer accessibility: speech does not work Rejected J0001

0
Bug #12384: Forward Greeter accessibility settings to the GNOME session Confirmed alant

0
Bug #16685: The Upgrader GUI is not readable by Orca Confirmed

0
Bug #16795: No audio in Unsafe Browser breaks accessible CAPTCHAs Confirmed

0
Bug #17666: the sound is muted by default in the greeter Confirmed anonym

0
Feature #17667: the keyboard shortcut to start orca doesn't work in a VM Confirmed anonym

0

Related issues

Related to Tails - Feature #12213: Wayland in Tails 5.0 (Bullseye) In Progress 2017-09-02

History

#1 Updated by intrigeri 2017-09-02 08:24:13

#2 Updated by intrigeri 2018-07-10 20:49:34

  • Description updated

#3 Updated by intrigeri 2018-09-01 13:52:34

  • Description updated

#4 Updated by sajolida 2018-09-02 17:53:49

I often test the screen reader to write alt=“” tags on our documentation. I could report my findings for you to work on this ticket but I don’t want to go through the extra work of creating tickets for each issue that I stumble upon. Would commenting on this ticket be an option to point you to possible issues?

#5 Updated by intrigeri 2018-09-02 20:49:14

> I often test the screen reader to write alt=“” tags on our documentation. I could report my findings for you to work on this ticket but I don’t want to go through the extra work of creating tickets for each issue that I stumble upon. Would commenting on this ticket be an option to point you to possible issues?

Yes! Except for website issues that should be collected on a dedicated subtask (I’m not sure I’ll take responsibility for accessibility of our website at this point, we’ll see).

#6 Updated by sajolida 2018-09-10 10:34:57

  • I can’t open the hamburger menu of Firefox with the keyboard only.
  • The hamburger menu of Tor Browser is not read by the screen reader.
  • The circuit view of Tor Browser is not read by the screen reader.

#7 Updated by intrigeri 2018-09-14 11:28:59

  • Target version changed from 2019 to 2020

#8 Updated by sajolida 2019-06-28 14:52:48

In GNOME Files in Tails Buster, both the and are read as “Menu toggle button not pressed” by Orca without clue of what they really are.

#9 Updated by sajolida 2019-07-28 15:56:30

In OnionShare, at least:

  • The Settings button is only read as “push button” by ORCA
  • The description of each option in the Settings dialog is not read by ORCA

#10 Updated by sajolida 2019-11-19 19:49:58

The content of pages in Tor Browser is not read by ORCA. For example, if I open https://debian.org/, the label of links are read if I tab through the page but I can’t get ORCA to read the rest of the content on the page.

#11 Updated by intrigeri 2019-11-22 11:17:15

Hi,

> The content of pages in Tor Browser is not read by ORCA. For example, if I open https://debian.org/, the label of links are read if I tab through the page but I can’t get ORCA to read the rest of the content on the page.

In Firefox 70.0.1 on Debian sid, the only way I’ve found to have ORCA read the content of a web page is to enable the caret cursor (F7). Then I can move the cursor around and ORCA reads the current paragraph. This also works on Tails 4.0. So at this point, IMO the next question is: how do sight-impaired users commonly use ORCA in a web browser? Does this technique work any worse in Tails than in a regular Firefox on Linux?

#12 Updated by goupille 2020-05-01 15:45:19

  • related to Bug #17666: the sound is muted by default in the greeter added

#13 Updated by zersiax 2020-05-01 16:29:37

I am a blind developer and security enthusiast and would love to see Tails be more accessible. I was directed here by after reporting some bugs and I would be happy to answer any “How Would sight-impaired people…” questions, as well as test implemented solutions from the point of view of a user depending on assistive tech. I will leave my two cents on the currently open subtasks to clarify where required, as a start. Let’s see how accessible we can make this distro.

#14 Updated by intrigeri 2020-05-07 09:12:15

  • related to deleted (Bug #17666: the sound is muted by default in the greeter)

#15 Updated by intrigeri 2020-05-07 09:19:34

> I am a blind developer and security enthusiast and would love to see Tails be more accessible. I was directed here by after reporting some bugs and I would be happy to answer any “How Would sight-impaired people…” questions, as well as test implemented solutions from the point of view of a user depending on assistive tech.

That’s awesome, thanks! I expect it’ll be immensely helpful once someone has the capacity to resume work on this.
Note that we may have to do some of that work anyway while porting Tails to Wayland in the next 2-3 years.