@emtucky @chiefkikio @karlgroves @CSUNCOD @mattmay It’s complicated and hard to do justice on Twitter. To get a taste of the complexities, here are the communication rules we use for meetings that mix deaf, hard of hearing, DeafBlind and blind participants with sighted/hearing ones: 1/ @emtucky @chiefkikio @karlgroves @CSUNCOD @mattmay 1. Please use the hand-raising tool
Take pauses as needed to keep the pacing of the meeting accessible for everyone. Remember to lower your hand when your turn is over.

2. Please wait until the Chair has recognized you as having the floor. 2/

This take on #a11y completely overlooks the havoc that the loss of the headphone jack has wrought on people with hearing loss. The 3.5 mm audio cable is the one single unifying standard that we have for putting together all the different components of assistive listening tech. 1/

https://twitter.com/steven_aquino/status/1233469598768488454

Wireless connectivity for hearing assistive tech is a complete and utter mess. There's made-for-iPhone that doesn't work with anything except Apple's products and a select line of hearing devices, including one brand of cochlear implants. 2/

Video relay services (VRS) have been a godsend for making phone calls accessible for people who use ASL. However, a recent ordeal has me made think that the industry has lost sight of the fundamental principle underpinning relay services: functional equivalence. 1/ Functional equivalence is a slippery concept, but in its most essential form can be boiled down to being able to make the same types of calls, under the same circumstances, with the same flexibility as a hearing person can. 2/

Wrestling with part of Karen Nakamura's keynote at #ASSETS2019: move from diversity and inclusion to ownership and belonging. Us deaf folks have been preaching this from the rooftops. Great to see this issue recognized. But how good are we at putting it in practice at ASSETS? 1/6 The target communities need to own the accessibility work and data, through and through. That also means putting people from the communities out font there on the stage and have them present on the work that they've sweated for. We're not seeing nearly enough of this here. 2/6

This is a long rant, but if we ever want to get accessibility right, we must address this type of barrier in content creation. I have long maintained that it must be easy to create accessible content, and hard to create inaccessible content. (1/11) This means authoring tools must have robust accessibility support built in from the ground up. Case in point: @Microsoft has prided itself on making great strides in accessible document creation by improving accessibility workflows, accessibility checking & PDF conversion. (2/11)