Update: This morning there was an update to PalChat. It resolves several of the labeling problems but more importantly, it resolves an issue with swipe order, which must have been a bit more of an involved fix than adding some labels. This is one of those times when I was wrong and I'm glad of it. Last night this was what sounded like a dismissive developer response. This morning it was one of the fastest accessibility fixes I've seen in a long time.
ORIGINAL POST:
I've been using an app called PalChat, which interfaces with a lot of common large language models in a single app. It's very powerful, but has some VoiceOver issues. Namely, the swipe order is wrong in some places, and a few buttons are unlabeled. So I wrote a very detailed message explaining all of these issues in what I thought was a pretty clear way. The developer replied to that message—which contained three separate issues—with a couple of sentences, essentially saying "I didn't change anything, and I don't know enough to fix it, sorry."
And honestly, I'm unreasonably annoyed about this. I took the time to report #accessibility problems that clearly do affect me, one of which is just a labeling problem, and all I got back was "I don't know how to fix that."
Well then *LEARN* how to fix it! Do I have to Google docs for you so you can figure out how to label a button?
I'm not sure the dev could have said "I don't care about accessibility" any more loudly. And maybe I'm just expecting too much of a single developer, but it doesn't seem like these fixes would be rocket science. This basically tells me I'll be able to use the app until something breaks.
There's a subscription, which I would have been happy to pay for if I'd gotten anything above 0% interest in actually working with me, but now I won't.
I'm tired.
Simon Jaeger
npub1ez…qwagq
2025-01-11 10:41:01 UTC
Author Public Key
npub1ezwmkgpt0tlgn2kgz385gph3qfrqcc7z02qgg5xkkcg0dtg2cmfstqwagqPublished at
2025-01-11 10:41:01 UTCEvent JSON
{
"id": "7dfc958c77a22038b3416e39300e1849973843adce918070f56c182f6fc50818",
"pubkey": "c89dbb202b7afe89aac8144f4406f102460c63c27a808450d6b610f6ad0ac6d3",
"created_at": 1736592061,
"kind": 1,
"tags": [
[
"t",
"accessibility"
],
[
"proxy",
"https://procrastodon.net/users/simon/statuses/113809297371801035",
"activitypub"
]
],
"content": "Update: This morning there was an update to PalChat. It resolves several of the labeling problems but more importantly, it resolves an issue with swipe order, which must have been a bit more of an involved fix than adding some labels. This is one of those times when I was wrong and I'm glad of it. Last night this was what sounded like a dismissive developer response. This morning it was one of the fastest accessibility fixes I've seen in a long time.\n\nORIGINAL POST:\nI've been using an app called PalChat, which interfaces with a lot of common large language models in a single app. It's very powerful, but has some VoiceOver issues. Namely, the swipe order is wrong in some places, and a few buttons are unlabeled. So I wrote a very detailed message explaining all of these issues in what I thought was a pretty clear way. The developer replied to that message—which contained three separate issues—with a couple of sentences, essentially saying \"I didn't change anything, and I don't know enough to fix it, sorry.\"\nAnd honestly, I'm unreasonably annoyed about this. I took the time to report #accessibility problems that clearly do affect me, one of which is just a labeling problem, and all I got back was \"I don't know how to fix that.\"\nWell then *LEARN* how to fix it! Do I have to Google docs for you so you can figure out how to label a button?\nI'm not sure the dev could have said \"I don't care about accessibility\" any more loudly. And maybe I'm just expecting too much of a single developer, but it doesn't seem like these fixes would be rocket science. This basically tells me I'll be able to use the app until something breaks.\nThere's a subscription, which I would have been happy to pay for if I'd gotten anything above 0% interest in actually working with me, but now I won't.\nI'm tired.",
"sig": "d200c3963cb8415c0ecc9d1ecd1fcff332ebc3da769841787ea2e163e9efca20f9d4a67aa32876803a7daf4c7fd5a5093f8b6f500651ebc89603ac7587eb0469"
}