This was actually more of a bug, though I needed to look into our code in question before confirming what was expected.
Therefore, this is now fixed. Significantly, this broke accessibility of overlays that weren't triggered by our XF.OverlayClick system specifically.