Thanks for the response!
Unfortunately, from what I, and a few other friends who rely on screenreaders can tell, is that there has not been a single change screen reader wise for the mobile, web, or desktop clients in the last year or so. On mobile, no buttons are labeled or marked clickable so you can’t tell if something is a button or what it does, and the main messages view doesn’t allow you to read the actual content of the messages, just the names. On desktop we have not yet found a screenreader that can distinguish any elements so you can not read, navigate, or effectively send any messages. On the web version the DOM is made in such a way that screen readers cannot navigate effectively, and it too has no aria attributes or labels, which again makes it impossible to tell if something is a button. It’s just as unusable as mobile or Desktop. I’ve talked to Discord staff about this as well (quite a while ago in fact) and they said that screen reader support will be worked on in the future, yet there haven’t been any changed still.
Regarding bridges like mattermost which do work, but not well. It’s best to use a bitlbee bridge to Discord, but sadly the only one that exists does not support bot accounts, which breaks the tos and gives you a high risk of getting banned. Discord has also been stepping up the bans for anyone who uses selfbots or custom clients, and there’s been a noticeable increase in those.
I also wonder how well Slack would work, as custom clients are allowed there, and there’s some very nice weechat-slack plugins, especially how Slack is more programming related. Personally I would prefer to stick with Slack or IRC.
It’s also important to make sure we don’t fracture the rust community with something like this where half of peeps move to Discord, and the other half stays on IRC.