Joanmarie Diggs Reporter
	Description • 9 years ago

Steps to reproduce:
1. Launch Firefox
2. Launch an accessibility explorer (e.g. Accerciser in Linux)
3. Examine the children of the accessible object backing the Firefox app

Expected results: Because there is only one window open, Firefox would have only one child frame/window.

Actual results: Firefox has two children, the expected child frame/window and a second child frame/window. Drilling down within that frame ultimately brings you to an accessible document frame with the accessible name of https://self-repair.mozilla.org/<your_locale_here>/repair.

While this is not a big deal, it is nonetheless noise in the accessibility tree which ATs find and need to ignore. Therefore, it would be great if this self-repair frame were not exposed to ATs in the first place.

Please and thank you. :)

	alexander :surkov (:asurkov)
	Comment 1 • 9 years ago

CC'ing Gijs for triage help.

	:Gijs (he/him)
	Comment 2 • 9 years ago

Gregg, can you look at this, please?

	Gregg Lind (Fx Strategy and Insights - Shield - Heartbeat )
	Comment 3 • 9 years ago

I don't know what to do about this.  Self-repair is in a hidden window.  Is there an engineering solution for this that allows the accessibility stuff to still work?

	alexander :surkov (:asurkov)
	Comment 4 • 9 years ago

ok, then this might be a dupe for 879741

	:Gijs (he/him)
	Comment 5 • 9 years ago

I defer to surkov - are there workaround for bug 879741 ?

	alexander :surkov (:asurkov)
	Comment 6 • 9 years ago

(In reply to :Gijs Kruitbosch from comment #5)
> I defer to surkov - are there workaround for bug 879741 ?

there's no really workaround for it, you either expose or not, and if you do then AT ignores it because it is hidden, tools don't, it doesn't hurt, but exposing those windows doesn't make any sense imo.