tutorial on 508 compliance?

Hey Jon! Re: your question about imported Engage content, yeah, since those are treated as web objects when you import them into Storyline, there isn't really a way for screen readers or tab navigation to pick up that content. Probably best to rebuild the content in Storyline if you need the interaction to be accessible. Or, if the interaction is simple, you might consider this approach instead: add a shape or button on top of your web object, and add Alt Text to describe the interaction content. The object won't be visible to sighted learners, since web objects cover up slide content - but it should still get picked up by the screen reader. 

Regarding your question about the sidebar menu - yeah, having that visible for every slide could get cumbersome to someone using a screen reader, since it will be read for every slide. If you need to show a menu, you might instead consider building it manually on a separate slide, and then create a trigger that enables learners to use a hot key to jump to the menu if they need it. (Of course you'd need to tell them up front about the hot key so they know it's available.)