In our case we have TTS options that may be enabled separately from the full Slate Screen Reader experience. We still push the TTS tasks through the Screen Reader subsystem since it handles queuing and everything for us.
That’s why we were always registering the user, and then only enabling the Slate handler if the option for full screen reading was enabled. Effectively we want the screen reader system enabled and working, but slate only be reading under certain conditions. Luckily, since our game only supports a single local player I can use a “system” user index for our TTS implementation and the “real” user index for the slate screen reader.
But it would be nice if this feature evolves to be able to support pushing TTS requests through separately from the full Slate Screen Reader being enabled.