Login
You're viewing the front-end.social public feed.
  • Guillem Leonguilevi@dragonscave.space
    Oct 16, 2026, 9:15 AM

    I don't know why I keep writing to Orchestral Tools to ask about the accessibility of SinePlayer. Their latest response makes it fairly clear that blind musicians are simply not an audience they are interested in. Their latest response:

    Hi Guillem,

    I am afraid the situation remains the same.

    We are aware SINE is not very accesible and there are blind people using it with varying levels of success.

    Unfortunately, while we do not hinder accessibility tools on purpose, I am afraid our current priority is SINE development on bugfixing and the most recent OS.

    While we want to improve SINE as much as possible, I am afraid we do not have the manpower to be able to implement all possible requested features.

    Apologies for the bad news. Anything else, just let me know.

    💬 1🔄 1⭐ 1

Replies

  • Guillem Leonguilevi@dragonscave.space
    Oct 16, 2026, 9:20 AM

    "Blind people using it to varying levels of success" is exactly what they said last time. Except last time, they said they had been able to help some blind people to that end. In the email that this message was a response to, I asked what assistance they had been able to provide and whether they could give me more information about how blind people were making use of it. Conveniently, that part of the email wasn't ever answered.

    The exodus from Kontakt is amazing and empowering and I'm sure NI deserves it. Unless, of course, you're blind. These companies will try to do everything that NI did but better. Except, of course, accessibility.

    💬 1🔄 0⭐ 0
  • Guillem Leonguilevi@dragonscave.space
    Oct 16, 2026, 9:27 AM

    But hey, this is 2026. I have one resource left. let's see what Claude can do with a half-accessible (15% accessible?) plug-in. Yes, I think this is fair use. Feel free to disagree with me. I'm sick of these responses. The truth is that I have no issue showing the same level of sympathy with these companies that they show with me.

    💬 1🔄 1⭐ 0
  • ScottScott@tweesecake.social
    Oct 16, 2026, 9:38 AM

    @guilevi Which OS and DAW are you trying to use it with? Might have a repo you and your friend Claude could add to.

    💬 1🔄 0⭐ 0
  • Guillem Leonguilevi@dragonscave.space
    Oct 16, 2026, 9:40 AM

    @Scott Mac/Reaper. Ideally I'd love for anybody to be able to use it eventually, but I'll settle for anything. I eventaully want to look at Musio too, because their response has been pretty similar.

    💬 1🔄 0⭐ 0
  • ScottScott@tweesecake.social
    Oct 16, 2026, 9:45 AM

    @guilevi Just downloaded and had a poke around. It's JUCE, plenty of places where they're using the standard control set, badly labeled and scant keyboard support but it really wouldn't be hard for them to fix the stuff I've found so far. Guessing the person emailing back doesn't know how. Of course, I don't yet know what's on screen that I'm not able to poke at though. It would defo be possible to tighten this up with the repo I had in mind. It's private for now, have you got a GitHub account?

    💬 2🔄 0⭐ 0
  • Guillem Leonguilevi@dragonscave.space
    Oct 16, 2026, 9:48 AM

    @Scott You're right, although it looks like the library part of it is either making an effort to hide itself from the accessibility tree or is some strange custom control. I was halfway ready to have Claude write a wrapper, which isn't super elegant but would've worked, but will absolutely take a look at this repo. Yes, my Github username is guilevi

    💬 0🔄 0⭐ 0
  • Guillem Leonguilevi@dragonscave.space
    Oct 16, 2026, 9:50 AM

    @Scott This is the thing that really bothers me about these responses. Diagnosing the issue and realizing that you don't have the manpower is one thing. Seeing the word accessibility and shitting your proverbial pants without having a clue what it would take to fix is just low-effort, which I will match with a low-effort LLM fix because I'm apparently kind of a vindictive person hahahaha

    💬 0🔄 0⭐ 0
  • Florianzersiax@cupoftea.social
    Oct 16, 2026, 10:59 AM

    @guilevi Not familiar with this one, do you know what UI it's using? Claude/Codex should potentially be able to work something out if there's enough UIA to work with, if not it gets a bit trickier

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Guillem Leonguilevi@dragonscave.space
    Oct 16, 2026, 9:28 AM

    @NicksWorld But the thing is that it's not about the program. It's about a sample library that I like and want to use. It's about the fact that a collection of glorified WAV files is inaccessible to me because this company simply does not care and isn't afraid to say so.

    💬 1🔄 0⭐ 0
  • Nicks WorldNicksWorld@mastodon.stickbear.me
    Oct 16, 2026, 9:30 AM

    @guilevi Yeah, but you can't force them to make it accessible if they don't want to, unless you pirate their stuff which can work, if you know how.

    💬 1🔄 0⭐ 0
  • Guillem Leonguilevi@dragonscave.space
    Oct 16, 2026, 9:31 AM

    @NicksWorld Of course not. Nobody can force anybody to do anything. But I sure as hell can throw my Claude at it. And that's exactly what I'm doing! :)

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Sean Randallcachondo@defcon.social
    Oct 16, 2026, 10:50 AM

    @guilevi I had a financial services thing this morning where before you could click agree you had to scroll to the bottom of the text. But the text was in a nonfocusable div they'd styled to look like a dialog. Nothing keyboardy worked. I literally had to hack the dom before the button was clickable. Couldn't even use OCR, the accept/decline were icons. Flippin' mess.

    💬 0🔄 0⭐ 0