Some animation transitions may make content inaccessible to ChromeVox users

[aitchiss]

Describe the bug

We recently became aware that ChromeVox (the in-built screen reading software for Chromebook) does not announce content that is set to have opacity: 0 (even if the opacity is then later transitioned to opacity > 0 via e.g. an animation) (See https://twitter.com/sarasoueidan/status/1365696682529333253)

We have a few instances in the app where we use opacity: 0 as the starting point for a transition - e.g. the sidebar-wrapper in articles.scss.

To Reproduce

I haven't actually been able to reproduce this as it seems ChromeVox is only available as the native screen reader on Chromebooks.

Expected behavior

Elements that fade or animate in should still be accessible to ChromeVox users. We can address this by adding a very small opacity to the elements that are currently 0, e.g. opacity: 0.00001

[github-actions]

Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you.

Feature requests that require more discussion may be closed. Read more about our feature request process on forem.dev.

To our amazing contributors: issues labeled type: bug are always up for grabs, but for feature requests, please wait until we add a ready for dev before starting to work on it.

To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem/oss. The OSS Community Manager or the engineers on OSS rotation will follow up.

For full info on how to contribute, please check out our contributors guide.

[cmgorton]

I believe #12939 closes this issue.