On Fri, Jun 29, 2012 at 12:05 PM, Kurt Zeilenga <[email protected]>wrote:
> So I'm wondering, what do those who understand well accessibility issues > think here, if software supports RTT, does it also need to support A/V? > No, I don't want to scare vendors :-) It's perfectly okay to offer A/V independently of RTT. Otherwise, we scare vendors away from adopting XEP-0301 It's just that if RTT is implemented as part of the same software as A/V is, then accessibility considerations need to be considered. -- If vendors allow clients to 'advertise' a signal of audio/video support, then it should also signal that RTT is also supported. -- Initiation mechanisms can still be separate and independent, or combined... If vendors decide to implement video/audio *and* RTT in the same software -- then a main accessibility concern is vendors that enable audio/video support by default, but block the ability to initiate an RTT conversation (i.e. non-compliance with Section 5 of XEP-0301). ...That is, a situation of preventing senders from having any opportunity to initiate RTT, and preventing recipients from being able to be informed that an incoming RTT attempt is occuring. That is the one that becomes the discriminatory issue. Mark Rejhon
