RISE - accessibility features

Agreeing with Mark and Ashely here, too.
I would love some solid information as well.
Currently, we do use and recommend Storyline because you can *make* the content accessible but it is not simple, or seamless, and this is a turn off to some of the folx we train to use authoring tools to create learning experiences. Some of those folx then read the... highlights... that articulate shares about Rise and think it's a solution that we somehow overlooked. Of course that is untrue, we keep up with it, but still cannot recommend it. So once we explain that what is written about accessibility is – and I am trying to be kind here – not a full picture of all that is necessary for accessibility, it really diminished the reputation of the entire suite of tools. So, we now actively steer folx away from Rise at the outset because it's not accessible and can't be made accessible to our standards, and ultimately makes our job harder with regard to trying to standardize on one suite of tools for our design and development cycles.