Closed Bug 1209062 Opened 9 years ago Closed 9 years ago

[Accessibility] Ensure system events are well labelled and announced.

Categories

(Firefox OS Graveyard :: Gaia, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

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

RESOLVED FIXED
feature-b2g 2.2r+
Tracking Status
b2g-v2.2r --- fixed
b2g-master --- fixed

People

(Reporter: yzen, Assigned: yzen)

References

Details

(Keywords: access)

Attachments

(11 files)

46 bytes, text/x-github-pull-request
timdream
: review+
Details | Review
46 bytes, text/x-github-pull-request
timdream
: review+
thills
: review+
Details | Review
46 bytes, text/x-github-pull-request
timdream
: review+
Details | Review
46 bytes, text/x-github-pull-request
Details | Review
46 bytes, text/x-github-pull-request
Details | Review
46 bytes, text/x-github-pull-request
Details | Review
46 bytes, text/x-github-pull-request
Details | Review
46 bytes, text/x-github-pull-request
Details | Review
46 bytes, text/x-github-pull-request
Details | Review
46 bytes, text/x-github-pull-request
timdream
: review+
Details | Review
46 bytes, text/x-github-pull-request
Details | Review
This includes: * Ensuring app opening is clear * Caller id number is announced on call * Hardware events are announced (USB, SDCard etc)
Assignee: nobody → yzenevich
Status: NEW → ASSIGNED
Comment on attachment 8668415 [details] [review] [gaia] yzen:bug-1209062-statusbar > mozilla-b2g:master Statusbar icons PR.
Attachment #8668415 - Flags: review?(timdream)
Attachment #8668415 - Flags: review?(timdream) → review+
Comment on attachment 8669022 [details] [review] [gaia] yzen:bug-1209062-callscreen > mozilla-b2g:master Tim, could you review the System app part. The title that is hidden for attention window is still accessible via the screen reader, which is a bug. Tamara, could you review the callscreen bits. Thanks.
Attachment #8669022 - Flags: review?(timdream)
Attachment #8669022 - Flags: review?(thills)
Attachment #8669022 - Flags: review?(timdream) → review+
Attachment #8669778 - Flags: review?(timdream)
Attachment #8669778 - Flags: review?(timdream) → review+
Comment on attachment 8669022 [details] [review] [gaia] yzen:bug-1209062-callscreen > mozilla-b2g:master Hi Yura, It looks good. One doubt I had was around the .css change in /system. I left a comment there. Can double check with system peer what else this might impact aside from callscreen? Thanks, -tamara
Attachment #8669022 - Flags: review?(thills) → review+
I believe we need it for RedTai/RedSquare
feature-b2g: --- → 2.2r+
Depends on: 1212528
No longer depends on: 1212007
Comment on attachment 8673299 [details] [review] [gaia] yzen:bug-1209062-statusbar-v2.2r > mozilla-b2g:v2.2r v2.2r PR
Comment on attachment 8673306 [details] [review] [gaia] yzen:bug-1209062-callscreen-v2.2r > mozilla-b2g:v2.2r v2.2r PR
Comment on attachment 8673313 [details] [review] [gaia] yzen:bug-1209062-appchrome-v2.2r > mozilla-b2g:v2.2r v2.2r PR
Will close this when the dependency is resolved.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment on attachment 8674010 [details] [review] [gaia] yzen:bug-1209062-unit-tests > mozilla-b2g:v2.2r This should fix the bugs I believe.
Flags: needinfo?(yzenevich)
(In reply to Yura Zenevich [:yzen] from comment #21) > Comment on attachment 8674010 [details] [review] > [gaia] yzen:bug-1209062-unit-tests > mozilla-b2g:v2.2r > > This should fix the bugs I believe. Sorry the tests.
Ok added a follow up PR for 2.2r, id wait until treeherder runs, but it looks like it's jammed atm.
Flags: needinfo?(yzenevich)
Keywords: checkin-needed
Looks green to me (Treeherder has trouble rendering individual revisions with the full revision SHA until some patches land and get pushed to production): https://treeherder.mozilla.org/#/jobs?repo=gaia&fromchange=71eda00bbf794579fd6cb05c75b481127afc1ba2&tochange=71eda00bbf794579fd6cb05c75b481127afc1ba2
Comment on attachment 8682271 [details] [review] [gaia] yzen:bug-1209062-announce-app > mozilla-b2g:master This should be the last patch for this bug. App name will be announced when it is opened, including homescreen.
Attachment #8682271 - Flags: review?(timdream)
Comment on attachment 8682271 [details] [review] [gaia] yzen:bug-1209062-announce-app > mozilla-b2g:master I think this is fine if you have enough tests to cover the sequences you would like to support, but without a master promise queue I wonder if we could have speeches overlap with one another, or a then() callback unset a properly at the wrong time for other speeches? It looks like you have just convert it into promises so if you think the current code is in risk of the problem describe above, adding an promise queue to protect that should be quite simple. Please also noted a promise without a |.catch((e) => console.error(e))| at the very end implies JS error will be consumed without ever being printed out. It also means .then() followed will be skipped too. Feel free to ask me to review again if you make additional changes and need extra pair of eyes to look at.
Attachment #8682271 - Flags: review?(timdream) → review+
https://github.com/mozilla-b2g/gaia/commit/cf0703f147e17bea1b18b58ada82625151238220 Thanks Tim, I added catch clauses and double checked that there's no speech interrupt.
In case threeherder is green this should be the last one for this bug for v2.2r
Keywords: checkin-needed
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
This patch has broken the Music app on master, at least. Music will no longer play in the background. See bug 1222143. Please back this out of master if you can't fix it quickly. I don't know about 2.2r. I didn't test there. Is the screen reader using the "content" channel? If so, it means that it will pause other apps that are using that channel. I'm not sure why music doesn't automatically resume. Maybe that is a music app bug. Is there a higher-priority channel that would allow the screen reader to just talk over the music rather than pause it?
Flags: needinfo?(yzenevich)
I don't understand why the screen reader is on by default. I haven't turned it on, and I don't see any setting for it anywhere in the settings app. Why it is touching the audio hardware in any way if it is off?
Just to be clear, it is the last commit, the announce app names part, that broke the Music app.
(In reply to David Flanagan [:djf] from comment #40) > This patch has broken the Music app on master, at least. Music will no > longer play in the background. See bug 1222143. > > Please back this out of master if you can't fix it quickly. I don't know > about 2.2r. I didn't test there. > > Is the screen reader using the "content" channel? If so, it means that it > will pause other apps that are using that channel. I'm not sure why music > doesn't automatically resume. Maybe that is a music app bug. > > Is there a higher-priority channel that would allow the screen reader to > just talk over the music rather than pause it? Ideally yes there should be but there isn't at the moment. (In reply to David Flanagan [:djf] from comment #41) > I don't understand why the screen reader is on by default. I haven't turned > it on, and I don't see any setting for it anywhere in the settings app. Why > it is touching the audio hardware in any way if it is off? The underlying bug is audio bug, this bug only exposes it even more. However you are right and screen reader should not do anything if it is off, which is what bug 1222249 is fixing. Once bug 1222249 is landed, bug 1222143 will be fixed. You can try the PR as it seems to work for me.
Flags: needinfo?(yzenevich)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: