1401392 - Windows content processes require fully-fledged application accessibles

Status: RESOLVED FIXED

(Core :: Disability Access APIs, enhancement)

Description

[(No longer employed by Mozilla) Aaron Klotz]

In bug 1023509 this was changed so that a content application accessible is just an ApplicationAccessible. On Windows we actually need this to be an ApplicationAccessibleWrap since ATs can directly interact with it.

Reported by Brett while working on JAWS stuff.

Comment 1

[(No longer employed by Mozilla) Aaron Klotz]

Attachment: Use ApplicationAccessibleWrap in content

Comment 2

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

Comment on attachment 8910028 [details] [diff] [review]
Use ApplicationAccessibleWrap in content

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

Oh. Yeah I guess we need this so we can give them a IID_IAccessibleApplication interface?

Comment 3

[(No longer employed by Mozilla) Aaron Klotz]

(In reply to David Bolter [:davidb] (NeedInfo me for attention) from comment #2)
> Oh. Yeah I guess we need this so we can give them a
> IID_IAccessibleApplication interface?

When trying to resolve it from a content accessible, yes. Brett tells me that JAWS resolves application accessibles off of the accessible provided with events.

I suppose that we could modify this in the future so that content always returns the browser's application accessible but this is the best short-term fix.

Comment 4

[(No longer employed by Mozilla) Aaron Klotz]

https://hg.mozilla.org/integration/mozilla-inbound/rev/a86e0e1c7c6318e9664af75c05bcb3ea79687cf4
Bug 1401392: Use ApplicationAccessibleWrap for content application accessible on Windows; r=davidb

Comment 5

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/mozilla-central/rev/a86e0e1c7c63