Michael Kauzmann [12:09]
This may warrant an issue, but I wanted to ask you first. Is there a reason that aria-live attributes need to
be created in the static html files? Could we wire them up to be created in display? That may simplify
testing html files. I also feel like it is baggage if you are trying to use UtteranceQueue-like-tech with
scenery outside of our phet scaffolding (I know that isn't directly supported right now).
Does this discussion warrant an issue, or have we already talked about it before, and decided it's best to
have these in the top level static html runnables?
Jesse Greenberg [14:12]
When we first started a11y we discovered that a couple of AT (at least VO and one more I can't
remember) had a limitation that aria-live did not work when added to the document dynamically. So we
ended up putting those elements in the main html file so they are there whenever the AT added
observers to the aria-live elements, which apparently was only once on start up. *However*, I am not
sure if that is still a limitation and I agree that it would be much more general if a display or something
could manage creation of these elements. We could test on our supported AT.
It may be nice to test and see if scenery can add these as they are needed. There are quite a few runnables that need these elements, so it would be simpler if it was in one spot.
zepumph
commented
6 years ago
From slack:
It may be nice to test and see if scenery can add these as they are needed. There are quite a few runnables that need these elements, so it would be simpler if it was in one spot.