Can tab outside of a callout

[betrue-final-final]

Environment: IE11 and JAWS 18
Are you willing to submit a PR to fix? No. I need help
Requested priority: High

1. When invoked, callout does not announce itself.
   Expected: Callout says ", alert, "

2. Can tab out of callout. Focus should be trapped.

[mdahamiwal]

When invoked, callout does not announce itself.
Expected: Callout says ", alert, "

Don't see a reason why a callout need to be an alert as far as we move the focus to it. Moreover, we use callout in lot other components like dropdown, tooltip, contextmeu. Adding alert to callout will be a bad experience for ATs.

2. Can tab out of callout. Focus should be trapped.

Somewhat related to 1. but is there any guideline that specifies this behavior? We generally follow one of the aria design pattern. Given that callout is a multipurpose container, its content should decide which pattern to follow. Thoughts ?

[betrue-final-final]

We need to tell the user that they are in a new object on the page if we bring focus to it. I've been listening to Windows toasts, and they don't grab focus, so we could announce them without moving focus.

As for the second issue, one of the big problems is that if you tab, you end up at the top of the tab order, in the browser chrome. This is totally disorienting. You are in a new surface that has no relationship to the main page. It's like a dialog, so escape should be the way to get out of it, and bring you back to where you were before the interruption.

[AbhinavSinghT]

In relation to issue #2, tab order feels broken when tabbing out of the callout. Should trap the tab or provide a way to navigate to next control and not to the top tab stop. Narration is painful when callout loses control due to tab.

[betrue-final-final]

Yes, I agree @AbhinavSinghT. We need to trap focus.

[betrue-final-final]

This is still an issue, for both focustrap and calling itself out.

[betrue-final-final]

All previous issues are fixed except for the focuszone issue.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions to Fabric React!

[stale]

This issue has been automatically closed because it has not had recent activity after being marked as stale. If you belive this issue is still a problem or should be reopened, please reopen it! Thank you for your contributions to Fabric React!
Why am I receiving this notification?

[yumikohey]

@betrue-final-final The workaround that I tried is added a FocusTrapZone within CallOut.

[maheshp9]

Can we reopen this issue and get it fixed the right way?