[Accessibility] Improve discover-ability of the screen reader at the FTU stage.

RESOLVED FIXED

Status

Firefox OS
Gaia::First Time Experience
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: yzen, Assigned: yzen)

Tracking

unspecified
ARM
Gonk (Firefox OS)
Dependency tree / graph

Firefox Tracking Flags

(feature-b2g:2.2r+, b2g-v2.2r fixed)

Details

Attachments

(2 attachments)

(Assignee)

Description

3 years ago
If the user stays in the welcome page for more than 15 seconds, there is an announcement "press volume up then volume down 3 times to start the screen reader". This allows users who are visually impaired to discover the screen reader on their own without sighted assistance.
(Assignee)

Updated

3 years ago
Assignee: nobody → yzenevich
Status: NEW → ASSIGNED
Created attachment 8667429 [details] [review]
[gaia] yzen:bug-1209049 > mozilla-b2g:master
(Assignee)

Comment 2

3 years ago
Comment on attachment 8667429 [details] [review]
[gaia] yzen:bug-1209049 > mozilla-b2g:master

Sam, could you take a look at the FTU part? Thanks
Attachment #8667429 - Flags: review?(timdream)
Attachment #8667429 - Flags: review?(sfoster)

Updated

3 years ago
Blocks: 1199493
Attachment #8667429 - Flags: review?(timdream) → review+
Comment on attachment 8667429 [details] [review]
[gaia] yzen:bug-1209049 > mozilla-b2g:master

Looks good, works for me.
Attachment #8667429 - Flags: review?(sfoster) → review+
(Assignee)

Comment 4

3 years ago
https://github.com/mozilla-b2g/gaia/commit/3f30bca1654f8b03ea92e968ce3a8f80f182e3b1
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
feature-b2g: --- → 2.2r+
I believe we need it for RedTai/RedSquare
Flags: needinfo?(yzenevich)
(Assignee)

Comment 6

3 years ago
(In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #5)
> I believe we need it for RedTai/RedSquare

Yep, that's what this feature is added for
Flags: needinfo?(yzenevich)
(In reply to Yura Zenevich [:yzen] from comment #6)
> (In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #5)
> > I believe we need it for RedTai/RedSquare
> 
> Yep, that's what this feature is added for

Hi Yura,

could you add a PR request for v2.2r thanks!
Flags: needinfo?(yzenevich)
(Assignee)

Comment 8

3 years ago
Comment on attachment 8667429 [details] [review]
[gaia] yzen:bug-1209049 > mozilla-b2g:master

Required for accessibility.
Flags: needinfo?(yzenevich)
Attachment #8667429 - Flags: approval-gaia-v2.2r?(whuang)
Comment on attachment 8667429 [details] [review]
[gaia] yzen:bug-1209049 > mozilla-b2g:master

2.2R is not FL yet so I'm + it for all feature-b2g:2.2r+
Attachment #8667429 - Flags: approval-gaia-v2.2r?(whuang) → approval-gaia-v2.2r+
Created attachment 8673282 [details] [review]
[gaia] yzen:bug-1209049-v2.2r > mozilla-b2g:v2.2r
(Assignee)

Comment 11

3 years ago
Comment on attachment 8673282 [details] [review]
[gaia] yzen:bug-1209049-v2.2r > mozilla-b2g:v2.2r

This is a PR for 2.2r
(Assignee)

Updated

3 years ago
Keywords: checkin-needed
This patch lack a way to disable this warning message definitely.
So far 15 seconds is too small that it triggers quite frequently in my automation devices (which is on my desk).

As a work-around, I will locally set the setting  "accessibility.screenreader-ftu-timeout-seconds" to 2147483 (24.8 days), which is the maximal value without overflow in setTimeout.
Flags: needinfo?(yzenevich)
This issue is being addressed in Bug 1215216.
Flags: needinfo?(yzenevich)
(In reply to Nicolas B. Pierron [:nbp] from comment #14)
> This issue is being addressed in Bug 1215216.

1215216 will fix the bug where this screenreader announcement plays every time the device starts - it should only do this on the first time of use after flashing. But if your automation starts with a fresh profile and doesn't skip FTU, it is expected that the screenreader starts talking at you after 15 seconds. Maxing out the timeout is probably your best option at that point.
You need to log in before you can comment on or make changes to this bug.