Tails

#1 Updated by intrigeri 2017-04-29 11:41:53

• Affected tool set to Greeter

#2 Updated by intrigeri 2017-04-29 11:45:12

• Assignee set to mercedes508
• QA Check set to Info Needed

> Would it be possible to make it enabled by default when installing Tails for example?

It seems to me that this is essentially the same problem (be it in terms of UX or in terms of implementation details) as the one about needing to persist language and keyboard settings in clear-text (so that they’re applied before one unlocks their persistent volume), which is well tracked on Feature #12470. Would you be fine if I broadened the scope of Feature #12470 to include this, and marked this very ticket as a duplicate?

#4 Updated by mercedes508 2017-05-01 17:31:03

• Assignee changed from mercedes508 to intrigeri

#6 Updated by intrigeri 2017-05-11 09:20:56

• Assignee changed from intrigeri to sajolida

> I think that making it easy to enable the screen reader from start is different that storing this setting between boots, because: […]

OK, fair enough.

> For example, could we have a keyboard shortcut to enable the screen reader from Tails Greeter? Is there anything standard for this in GNOME?

Yes. https://wiki.gnome.org/Design/OS/KeyboardShortcuts says that Alt+Super+S should be enough (and FTR each of Windows and macOS have others, different shortcuts). I’ve just verified it works fine in 3.0~beta4 (even though the change takes ~12 seconds to be effective here — MacBook Pro started from USB — as Orca startup needs to read quite some stuff from the USB stick). I’ll let you decide if you want to turn this ticket into a Documentation one, or ask me to do the ticket mangling what I proposed earlier here, or simply close it as resolved.

#7 Updated by sajolida 2017-05-16 10:53:47

• related to Feature #5501: Persistence preset: locale and accessibility options (language, keyboard, and formats) in Greeter added

#8 Updated by sajolida 2017-05-16 10:56:29

• Target version set to Tails_3.0
• QA Check deleted (Info Needed)
• Type of work changed from Discuss to End-user documentation

I bet you were referring to Feature #5500 in Feature #12470#notes-2. I added “accessibility” to its title. And for now, I’ll document some keyboard shortcuts relevant to accessibility in the documentation for 3.0 as a solution for this ticket.

And I ack the “~12 seconds” to start the screen reader, whether or not it’s started with a keyboard shortcut.

#9 Updated by sajolida 2017-05-16 10:57:02

• blocks Feature #12432: Technical writing core work 2017Q2 added

#10 Updated by sajolida 2017-05-18 17:53:40

• Assignee changed from sajolida to spriver
• QA Check set to Ready for QA
• Feature Branch set to doc/12470-accessibility-shortcuts

spriver: do you want to have a look? Otherwise try to assign it to cbrownstein.

#11 Updated by spriver 2017-05-19 19:05:17

• Assignee changed from spriver to sajolida
• Feature Branch changed from doc/12470-accessibility-shortcuts to spriver:doc/12470-accessibility-shortcuts

I’m fine with everything, I tested all documented keybindings etc.
I just added the method to select multiple items from the menu without closing it after each selection (by pressing space), if that’s okay. If it’s too much detail, ignore my commit and merge it as-is.

#12 Updated by intrigeri 2017-05-20 06:42:12

• Subject changed from Having screen reader enable at startup to Document how to start the screen reader with keyboard shortcuts

#13 Updated by sajolida 2017-05-22 21:43:59

• Status changed from Confirmed to Resolved
• Assignee deleted (sajolida)
• QA Check deleted (Ready for QA)
• Feature Branch changed from spriver:doc/12470-accessibility-shortcuts to doc/12470-accessibility-shortcuts

I prefer Space much more than Enter! I originally copied this from some GNOME documentation without testing it enough it seems.

So actually I removed Enter in cc4a84ab32 and merged that.

#14 Updated by intrigeri 2020-04-15 06:02:09

• Affected tool changed from Greeter to Welcome Screen