There already exist web standards for #accessibility which details media, such as captions. This extends to livestreams, recorded video. BUT not many authoring/conference platforms support this, or hide support. Standards are WCAG, latest ver 2.1: https://www.w3.org/TR/WCAG21/  2/?

Zoom and Microsoft Teams have voluntary accessibility reports on file. Zoom's accessibility docs: https://zoom.us/accessibility  3/?

Microsoft Teams has had reported accessibility issues but here's what MS lists as what they support. https://support.office.com/en-us/article/accessibility-overview-of-microsoft-teams-2d4009e7-1300-4766-87e8-7a217496c3d5 4/?

Microsoft also has a guide for using the JAWS screen reader with Teams. Your mileage may vary if using NVDA. https://support.microsoft.com/en-us/office/use-a-screen-reader-to-explore-and-navigate-microsoft-teams-47614fb0-a583-49f6-84da-6872223e74a0#picktab=windows 5/?

So HERE'S THE THING THOUGH. Despite these docs from the companies themselves, each person experiences their body and conditions differently. But using WCAG 2.1 is a good starting point: captions/transcripts, have a chat (not only video or audio) option too, etc 6/?

Not only does this mean people with tech issues (say, audio driver issues, w/e) can still participate in at least one method in meetings, those of us with a wide range of issues can also: from my autistic fam to folk with joint pain to so on. 7/?

Granted this is just a BASIC BASIC AF overview. I'm sure more folk would chime in. But please, do not end your #accessibility efforts here either. Also, if this thread has helped you at all, buy me a coffee / beer: http://paypal.me/kitchan