Hi Chad,
I think there’s a larger issue of load order fragility here that would be nice to address, but the main problem in this case is that the SlateScreenReader plugin has it’s load phase set to PostEngineInit. Modules can forcibly load other modules earlier than their specified phase, and in this case the engine subsystem is causing an early load. The easiest way to avoid this would be to just bump the SlateScreenReader plugin to load earlier and be sure it already exists prior to the subsystem accessing it. I tried setting the load phase to PostDefault and it seemed to resolve the issue without causing any problems with the screen reader, so that might be the quickest path forward here.
Best,
Cody