√¯¯¯¯¯¯¯¯
That is about the best I could come up with. I could use a screenshot, but I worry about accessibility issues with that, and I'd need a screenshot for each question and answer choice and there are a ton of them:
Here's one example in the attached image.
The accessibility of complex math equations is an issue. From what I've seen screen readers struggle with superscripts and statistical formulas. In a business statistics course for an MBA program the best I could come up with was an image file of each equation and alt-text from the professor on how he would say the equation if he was in class.
Some people with visual disabilities will have active braille display keyboards that work well with math equations with LaTeX. LaTeX isn't supported yet in Storyline.
Here is what I came up with (1-question functionality sample only)
https://360.articulate.com/review/content/1aac6464-3a42-4c79-b9be-52a11e46e24c/review
I typed my number and then used the square root symbol (all in Signika font) and then used a symbol that was an elevated horizontal line. When I changed this horizontal line font to Arial, it lined up perfectly with the Signika font (ironically, using the same font makes it not line up), and I could "stretch" it for as long as I needed by just copying and pasting more horizontal lines.
The second part was just adding a second text layer that was the number existing inside of the root symbol. I made this the same font size as the root symbol, and just lined everything up.
Once I started copying this setup over, it becomes very easy to update a series of questions like this. Like a lot of design, you'll spend more time just setting things up that first time.
For the root/number in the question itself, that's just a screengrab image from a Word doc using the same colored background. I think I'll end up just changing that to my font trick above, however, I'll have to always slide that number text box around based on the length of the question. Still easier than a screenshot, I guess.
As for accessibility, it's not perfect, but I used the focus order to override what's being read by the screen reader in both the question and each answer button.
