spending some time on my local model LLM agent since my approach is way more screen reader friendly than pi.dev 🤓
@mauve hit up the clownbot accessibility-mode elf for my take on an elf that’s controller friendly ish
@tychi What's the tldr of your approach? I'm targeting terminal screen readers in particular so I avoid needless rerenders or notifications.
Black and white minimal courier new screenplay for scrollback of chat
Lb/rb to tab chats
Voice optional input
Basically exactly the accessibility mode label, anything that decreases HCI friction— so for me that’s being able to toggle out of game into chat with one button and then to use the same gamepad and headset for input instead of needing to reach for a keyboard with a stock harness on a name brand os
The silly thing is that it should be the one way to “summon” anything from silly
“Accessibility”
@tychi Lately I'm only using this console based reader called TDSR so I've focused on reducing unnecessary output from commands. For graphical stuff I use Orca but I've considered making my own.
@mauve I have done eleven labs stt so I have accidentally started making a prototype in house one I guess
Will test orca
@mauve not this one specifically but which screen reader are you using to test?
I’ve done explicit aria-live with like polite and rude iirc in the past— so no my screen reader code would fail right now most likely, but I can align on how you test and get good on my end
Would be like one session once I can repro my failures