Should FullWindowOverlay always have accessibilityviewismodal as true?

[wahidshafique]

This was prompted by a bug that I encountered once I updated to the latest version of rns. Previously I had a fullscreenoverlay that was persistent, used for toast notifications. However after this change was merged in, I could not interact with any elements underneath the overlay using the ios accessibility inspector.

I'm wondering whether accessibilityviewismodal should be an configurable prop, as the overlay doesn't necessarily mean I want the screen reader to be captured.

What does everyone else think?

[tboba]

Hey @wahidshafique, thanks for making this discussion!
Yeah, I think it's a good idea to make the content underneath FullWindowOverlay interactive. I'll leave this topic to the ideas category.

[bitensam]

Hi, I have encountered the same problem. Any chance to make those a11y props configurable ?

[mzablockifm]

This might become a bigger problem because European Accessibility Act comes into effect in June 2025.

[kkafar]

@bitensam @mzablockifm

Hey, I haven't answered here, but you can customise this behaviour by unstable_accessibilityContainerViewIsModal. See this PR:

• feat(iOS): add unstable_accessibilityContainerViewIsModal prop for FullWindowOverlay #2854

for details.