Voyager

8169 readers

47 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Rules

Be nice.
lemmy.world instance policy

Sponsor development! 👇

💙

founded 2 years ago

MODERATORS

aeharding@lemmy.world

aeharding@vger.social

Voyager Accessibility Issues (lemmy.zip)

submitted 9 months ago by seavoyager@lemmy.zip to c/voyagerapp@lemmy.world

11 comments fedilink hide all child comments

First let me say, I have tried many Lemmy clients, and Voyager is by far my favorite.

For large text support, Voyager might be the best. But it could still do better.

I have posted some bug reports and issues, here in the lemmy coms and even created PRs on the Voyager github repo. Those PRs were never merged.

As a proof of concept or prototype, I have forked Voyager to fix many of the large text or accessibility related issues.

You can find this fork documented here along with the webapp.

https://seevoyapp.free.nf/

If you scroll down to the "Compare" section, I think it will be very clear as to what the issues are.

Hopefully you will see this as a very comprehensive bug report which includes suggested code fixes.

Also many of these issues, like string truncation of user names and server instances, are general issues which impact all users regardless of visual acuity.

you are viewing a single comment's thread
view the rest of the comments

[–] cloudless@piefed.social -3 points 9 months ago (1 children)

What point am I missing? If I want a replacement of Voayager with the features of your fork, and I use PieFed, that would be the entire point.

[–] seavoyager@lemmy.zip 5 points 9 months ago (3 children)

Will Voyager using a PieFed backend fix this? If so, then we are on the same page. But this doesn't look like a backend protocol issue to me. This looks like a UI issue.

[–] antler@feddit.online 6 points 9 months ago* (last edited 9 months ago) (2 children)

At first, I misread the post you are replying to; maybe you did the same. The poster was asking if your app supports PieFed, not because PieFed fixes the issues that you identified, but because that's the site that poster uses.

In other words, they may want to use your app, but would need it to support PieFed since that's the site they use.

[–] paraphrand@lemmy.world 6 points 9 months ago (1 children)

Classic online discussion moment.

[–] antler@feddit.online 3 points 9 months ago (1 children)

I really considered whether I wanted to comment, but my desire to procrastinate at work won out.

[–] paraphrand@lemmy.world 1 points 9 months ago

I sympathize.

[–] GreenKnight23@lemmy.world 3 points 9 months ago

classic piefed user. always making it about piefed.

[–] seavoyager@lemmy.zip 1 points 9 months ago* (last edited 9 months ago)

In fact, I know it's a UI issue, because I know the data is available. It's just not styled correctly.

Do you think the backend protocol is returning "..." ellipses as part of a username???

[–] cloudless@piefed.social 1 points 9 months ago

It looks like you are missing the point. I asked you about Seevoy's support for PieFed, not Voyager's support for large text support.