Accessibility, quality of life, and bug fixes

Some general housekeeping I've been meaning to do! Nothing new for the story… yet….

• Threadbare is now fully image described! I chose to do this in a kind of narrative / longdesc style, basically rewriting Threadbare as if it wasn’t a visual novel, which is why it took so long. It’s ehhh not a perfect experience on my NVDA screenreader, for reasons I will elaborate on shortly, but it should be functional.
   ‎
• Added temp QOL fixes for screenreaders. They’re not great, but it could be worse. I coded myself into a corner by making my navigation menu and typewriter animation macros baked into each passage. Originally, <<typed>> text would read out each individual letter one by one until the animation finished, and every time a passage changed, NVDA would re-read the menu buttons. Right now my hackjob fix adds “aria-hidden” and “aria-live” labels retroactively in JS every time a new passage loads or a typewriter animation goes off, so you don’t have to listen to that racket.
   ‎
  Unfortunately, this means you’re stuck waiting for the animation to finish for the text to populate. As always, you can skip the <<type>> animation with spacebar or CONT_. Just don’t buttonmash or it gets confused ):
   ‎
  In the future I want a proper toggle for the <<type>> animation, and… I don’t even know what I’m doing with the menu... but it’s beyond my JS abilities for right now.
   ‎
• Added a “tension” setting for the timed segment. You can optionally work through it at your own pace.
   ‎
•  Added a mute button. 
   ‎
  
• Fixed missing dialogue on the route where Frey withholds her name. No huge changes, ES and Rhodes just call you stuff like “Canary” “Seer-killer” and “Dude” instead of “Frey.” 
   ‎
• Heckled Kairos.