1312100 - Enable a11y+e10s by default for OSX/Linux in Fx52

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Jim Mathies [:jimm]]

Firefox on OSX does not enable e10s if a11y activity has been detected. Currently we do not have open crash or other types of blockers preventing us from turning this on.. so lets do it!

The plan:

1) enable in Nightly (target: Fx 53) 
2) let the feature roll out to beta and monitor for stability issues
3) If all looks good on beta, roll out to release.

Comment 1

[Jim Mathies [:jimm]]

davidb tells me the a11y team would like to target 52 for this, so updating.

Comment 3

[Jim Mathies [:jimm]]

Attachment: patch

Comment 4

[Jim Mathies [:jimm]]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=f3100320ccc08609ea7a6b2b424723b86b94336a

Comment 5

[:Felipe Gomes (needinfo for replies!)]

Comment on attachment 8804245 [details] [diff] [review]
patch

Review of attachment 8804245 [details] [diff] [review]:
-----------------------------------------------------------------

IIRC a11y on OSX barely "worked" before e10s, and it was made worse with e10s.. Did anyone check that basic VoiceOver support will not be regressed by enabling e10s?

Comment 6

[Jim Mathies [:jimm]]

(In reply to :Felipe Gomes (needinfo me!) from comment #5)
> Comment on attachment 8804245 [details] [diff] [review]
> patch
> 
> Review of attachment 8804245 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> IIRC a11y on OSX barely "worked" before e10s, and it was made worse with
> e10s.. Did anyone check that basic VoiceOver support will not be regressed
> by enabling e10s?

Tracy, please test VoiceOver with e10s on and off in nightly to see where we are at.

Comment 7

[Tracy Walker [:tracy]]

I wouldn't call VoiceOver a usable accessibility tool with Firefox.  Simple things like reading through search results don't work.  Certain sub-menu items (like those in our awesome bar) are also not read by VoiceOver.  This sort of broken behavior is present on Release as well as Nightly in non-e10s and e10s.  

That said, to determine if/what has regressed from non-e10s to e10s, a full QA test plan of VoiceOver and its function across our browser should be created and implemented.  Is that something you want me to do here, Jim?

Comment 8

[Jim Mathies [:jimm]]

(In reply to Tracy Walker [:tracy] from comment #7)
> I wouldn't call VoiceOver a usable accessibility tool with Firefox.  Simple
> things like reading through search results don't work.  Certain sub-menu
> items (like those in our awesome bar) are also not read by VoiceOver.  This
> sort of broken behavior is present on Release as well as Nightly in non-e10s
> and e10s.  
> 
> That said, to determine if/what has regressed from non-e10s to e10s, a full
> QA test plan of VoiceOver and its function across our browser should be
> created and implemented.  Is that something you want me to do here, Jim?

That sounds like a very good idea. I'd love to know what slipped through the e10s crash when we rolled out. From Davidb, we officially don't support a11y on OSX, but we generally want to avoid regressing working features. So lets figure out where things are at.

Comment 9

[Jim Mathies [:jimm]]

(In reply to Jim Mathies [:jimm] from comment #8)
> (In reply to Tracy Walker [:tracy] from comment #7)
> > I wouldn't call VoiceOver a usable accessibility tool with Firefox.  Simple
> > things like reading through search results don't work.  Certain sub-menu
> > items (like those in our awesome bar) are also not read by VoiceOver.  This
> > sort of broken behavior is present on Release as well as Nightly in non-e10s
> > and e10s.  
> > 
> > That said, to determine if/what has regressed from non-e10s to e10s, a full
> > QA test plan of VoiceOver and its function across our browser should be
> > created and implemented.  Is that something you want me to do here, Jim?
> 
> That sounds like a very good idea. I'd love to know what slipped through the
> e10s crash when we rolled out. From Davidb, we officially don't support a11y
> on OSX, but we generally want to avoid regressing working features. So lets
> figure out where things are at.

s/crash/cracks :)

Comment 10

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e71702af187b
Enable a11y with e10s for Linux/OSX on all channels. r=felipe

Comment 11

[Carsten Book [:Tomcat]]

backed out for bustage like https://treeherder.mozilla.org/logviewer.html#?job_id=38542590&repo=mozilla-inbound

Comment 12

[Pulsebot]

Backout by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/cdd2fcf94281
Backed out changeset e71702af187b for bustage

Comment 13

[Jim Mathies [:jimm]]

Attachment: patch v.2

Comment 14

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/6dca348b9b1d
Enable a11y with e10s for Linux/OSX on all channels. r=felipe

Comment 15

[Phil Ringnalda (:philor)]

https://hg.mozilla.org/mozilla-central/rev/6dca348b9b1d

Comment 16

[Tracy Walker [:tracy]]

Jim and I discussed the VoiceOver case in 1:1. We determined full blown testing of this isn't worthwhile since the feature is 1) not supported and 2) VoiceOver wasn't really usable in non-e10s. (ie.  VoiceOver would not read page content). If plans are made to support and get full compatibility of Firefox with VoiceOver, then a full testing effort can be set into motion.

Comment 17

[David Bolter [:davidb] (NeedInfo me for attention)]

Yeah, we'd really like to support OSX but can't prioritize that anytime soon. Until things improve there, we can expect roughly 0.05% of FF mac users to instantiate a11y.