Project

General

Profile

Feature #14522

Make Tails usable for blind users

Added by anonym almost 2 years ago. Updated 25 days ago.

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

25%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

anonym will review.

Resources:

pan-down.png View (197 Bytes) sajolida, 06/28/2019 02:51 PM

open-menu.png View (181 Bytes) sajolida, 06/28/2019 02:51 PM


Subtasks

Bug #7502: Unsafe Browser is not accessibleConfirmed

Bug #7503: The Persistent Volume Assistant is not readable by OrcaConfirmed

Bug #9051: Tor Launcher is not accessibleIn Progress

Bug #9260: Orca reads neither Tor Browser nor Thunderbird if started after itResolved

Bug #9732: Orca cannot work with ElectrumConfirmeds7r

Feature #11664: Improve usability of the Greeter with a screenreaderConfirmedalant

Bug #12014: Tails Installer accessibility: speech does not workRejectedJ0001

Bug #12384: Forward Greeter accessibility settings to the GNOME sessionConfirmedalant

Bug #16685: The Upgrader GUI is not readable by OrcaConfirmed

Bug #16795: No audio in Unsafe Browser breaks accessible CAPTCHAsConfirmed


Related issues

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

History

#1 Updated by intrigeri almost 2 years ago

#2 Updated by intrigeri about 1 year ago

  • Description updated (diff)

#3 Updated by intrigeri 12 months ago

  • Description updated (diff)

#4 Updated by sajolida 12 months ago

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 12 months ago

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 12 months ago

  • 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 11 months ago

  • Target version changed from 2019 to 2020

#8 Updated by sajolida about 2 months ago

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 25 days ago

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

Also available in: Atom PDF