Closed zepumph closed 6 years ago
For example, the scrolling feature doesn't work on IE, is this acceptable moving forward? Or should I spend more dev time to support that feature, in phetsims/chipper#617
@zepumph FYI, we did publish a link to it in the CSUN paper we wrote, but the published link was incorrect. I made a correction on the PhET Accessibility page.
One big improvement visually would be if the iframe on the left was fixed as the content on the right scrolled. Also, the fixed heights on the alerts are too small. I don't think a fixed height is the best approach to stop the bounciness.
A few thoughts from a meeting regarding this issue:
What is the a11y view for? @emily-phet: The accessibility content that we add to our simulations. Content/structure focused. @terracoda: I see it as a way for visual users to experience what a screen reader user does.
We together decided that this is a document that deserves some love, and will be used in multiple places, and shown to others outside the project.
We came up with https://github.com/phetsims/a11y-research/issues/66 as a list of features that will push the a11y view to the next level, and help to convey our a11y content more effectively to all audiences that use the document.
Thanks for a great meeting today @terracoda @emily-phet @jessegreenberg. Closing.
In https://github.com/phetsims/chipper/issues/622 we found a big bug in the A11y View. It brought up a point about who is using this document, because that changes how strict we are in handling problems with it. I see it as a spectrum:
---less use---
The more use, the more time that should be taken in a few areas
@emily-phet I know that we have brought this up before, but It would be good to hammer out a more specific game plan to help address the issues that keep coming up. @terracoda @jessegreenberg as well @mbarlow12 feel free to add in. I'll probably bring this up at a meeting soon.