Grant Butler

@grantjbutler
8 Followers
111 Following
115 Posts
iOS @ Twitch. Broadcast Production @ Zeldathon/KinstoneIO. Admin @ MiniKitMarathon. I organized a fandom concert at one point.
Websitehttps://grantjbutler.com/
PronounsHe/him
Hmmmm, do I write my own IRC library in Swift that supports Twitch, or do I create a WebSocket implementation/bridge from Swift to JavaScript and pull in a JavaScript Twitch IRC implementation, giving it my WebSocket implementation when I set up everything in JavaScriptCore...?
Which browser do you use?
Thanks for any boosts! I wanna know!
Chrome šŸ‘ļø
29.4%
Firefox šŸ”„
37.5%
Brave šŸ¦øā€ā™€ļø
6.5%
Opera ā™¦ļø
2.3%
Edge 🟦
5%
Other (comment) ⭐
5.6%
See results only šŸ˜‘
2%
Safari šŸŒ€
11.7%
Poll ended at .
OK #Mastodon. I've seen several toots on #accessibility for #screenreader users, however, I've not seen one from a screenreader user (as far as I know). I've used ZoomText, Outspoken, JAWS (AKA JFW), Supernova, NVDA (Windows), and VoiceOver (both on Macs and iPhone). I don't have experience with Windows Narrator or TalkBack. I would like to rectify and clarify a few small things.
First off, any awareness of accessibility issues, and endeavours to make things more accessible is great. Keep going!
But…
Blind/low-vision people have been using the internet as long as everyone else. We had to become used to the way people share things, and find workarounds or tell developers what we needed; this latter one has been the main drive to get us here and now. Over the past decade, screen readers have improved dramatically, including more tools, languages, and customisability. However, the basics were already firmly in place around 2000. Sadly, screen readers cost a lot of money at that time. Now, many are free; truly the biggest triumph for accessibility IMHO.
So, what you can do to help screen readers help their users is three simple things.
1. Write well: use punctuation, and avoid things like random capitalisation or * halfway through words.
2. Image description: screen readers with image recognition built-in will only provide a very short description, like: a plant, a painting, a person wearing a hat, etc. It can also deal with text included in the image, as long as the text isn't too creatively presented. So, by all means, go absolutely nuts with detail.
3. Hashtags: this is the most commonly boosted topic I've seen here, so #ThisIsWhatAnAccessibleHashtagLooksLike. The capitalisation ensures it's read correctly, and for some long hashtags without caps, I've known screen readers to give up and just start spelling the whole damn thing out, which is slow and painful.
That's really all. Thanks for reading! 😘
Huh, it’s working now. Not 100% sure what the issue was, but after re-installing the software again, it’s working. Which means I’m fully on OBS 28 now. 
Hmmm, I thought all my OBS plug-ins had updated for OBS 28 and Apple Silicon, but it looks like the NDI plugin is using a version of the NDI runtime that doesn’t support ARM. No matter, I was using it for one thing and I should be able to replace it with something else. Now I just have to figure out why the Stream Deck software doesn’t like OBS 28…
Why do I do this to myself? I guess I’ll add ā€œMastodon clientā€ to that growing list of project ideas that strangely never seems to get any smaller…
One thing that was super common on Mastodon / Fediverse prior to this mass migration was adding image descriptions to help be accessible to our many blind and partially sighted users here. Many people won't boost posts without them.
Please consider adding alt text to your images when you can. 

Haven't done an #introduction yet since coming back to this account, so hi! I'm Grant! I do a whole bunch of software development. Currently #iOS on the Mobile Core team at #Twitch, and #swift, #php, and #laravel things on the side.

I also do #charity events! I do #broadcast and #av things for Zeldathon, and run my own #lego-themed event, Minikit Marathon, both of which #stream on Twitch.

Every Mastodon explanation is like "It's very simple, your account is part of a kerflunk, and each kerflunk can talk to each other as part of a bumblurt. At the moment everyone you flurgle can see your bloops but only people IN your kerflunk can quark your nerps. Kinda like email."
Is there a good desktop Mastodon client that people are using for macOS, or is our best bet right now to just use the web interface?