Closed Bug 911714 Opened 8 years ago Closed 8 years ago

Backgrounded apps remain visible to screen reader

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: eeejay, Assigned: eeejay)

References

Details

(Keywords: access)

Attachments

(1 file, 2 obsolete files)

Currently, background apps are simply obscured by z-order. Our screen reader still picks it up. We need to explicitly hide background apps.
Blocks: gaiaa11y
Keywords: access
Summary: Window management is not screen-reader friendly → Backgrounded apps remain visible to screen reader
Attachment #801751 - Flags: review?(alive)
The aria-hidden attribute needs to be applied to the iframe because of the way the accessible tree is constructed.
Attachment #801751 - Attachment is obsolete: true
Attachment #801751 - Flags: review?(alive)
Attachment #801758 - Flags: review?(alive)
Comment on attachment 801758 [details] [diff] [review]
Hide backgrounded windows, and show foreground window.

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

Could we put aria-hidden on the frame (div.appWindow) instead of iframe element?
There would be other elements in the appWindow container other than iframe.
I don't know the detail of screen reader though.

Please send a pull request as well.
Attachment #801758 - Flags: review?(alive) → feedback+
(In reply to Alive Kuo [:alive] from comment #3)
> Comment on attachment 801758 [details] [diff] [review]
> Hide backgrounded windows, and show foreground window.
> 
> Review of attachment 801758 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> Could we put aria-hidden on the frame (div.appWindow) instead of iframe
> element?
> There would be other elements in the appWindow container other than iframe.

What other elements? In any case, I will update this with a version that gives the frame an explicit region role so that it is not pruned in the accessible tree and is available to the screen reader.

> I don't know the detail of screen reader though.
> 
> Please send a pull request as well.
Attachment #801831 - Flags: review?(alive)
Comment on attachment 801831 [details] [diff] [review]
Hide backgrounded windows, and show foreground window.

I trust the un-hiding of the home screen is done in one of the other code paths, right? Because I only see here where the home screen is explicitly hidden, but not un-hidden.
(In reply to Marco Zehe (:MarcoZ) from comment #6)
> Comment on attachment 801831 [details] [diff] [review]
> Hide backgrounded windows, and show foreground window.
> 
> I trust the un-hiding of the home screen is done in one of the other code
> paths, right? Because I only see here where the home screen is explicitly
> hidden, but not un-hidden.

https://github.com/eeejay/gaia/blob/54e842a1a841fde841bd450e9af80e478ec84985/apps/system/js/window_manager.js#L474

open homescreen path would go through here.
(In reply to Eitan Isaacson [:eeejay] from comment #4)
> (In reply to Alive Kuo [:alive] from comment #3)
> 
> What other elements? In any case, I will update this with a version that
> gives the frame an explicit region role so that it is not pruned in the
> accessible tree and is available to the screen reader.

I'm going to put alert prompt confirm - modal dialog in the frame as well.
Comment on attachment 801831 [details] [diff] [review]
Hide backgrounded windows, and show foreground window.

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

r=me. Do you need me to merge for you?
Attachment #801831 - Flags: review?(alive) → review+
Thanks!
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.