dragonscave.space is one of the many independent Mastodon servers you can use to participate in the fediverse.
A fun, happy little Mastodon/Glitch instance.

Server stats:

237
active users

Public

Looked at the pull request interface of . With a and keyboard, there's no way to jump between PRs in the list without reading the info for each one, and the diffs are even less than on .

Quiet public

@jscholes Hey, accessibility is really important for us and we try to improve it constantly. (Alt texts, Semantic HTML, less JavaScript, supporting keyboard navigation, ...)

It would be great if you could create an issue regarding the accessibility issue that it can be fixed!

@Beowulf I understand, and I do appreciate the response.

Full disclosure that my full time job is in accessibility consulting, and I take care over how much of my personal time I devote to it too. I'm disabled myself and unfortunately can't avoid the multiple accessibility barriers I'm faced with every day, so I have to choose which hills I want to climb. Accessible diffs is a mountain in its own right, and not just one issue to be fixed.

With that in mind, I'd love to read any documentation or statements you have about your approach and commitment to accessibility. How do you triage and prioritise accessibility problems when they're reported? What are your testing strategies? How much of the project's budget is dedicated to expert accessibility consulting?

Essentially, how would my report be handled if I spent time on one?

Quiet public

@jscholes There is ongoing work at different places in the forgejo space.
PRs regarding the UI are also blocked if Accessibilty issues are detected.

The main issue isn't financial, instead human power.

> Essentially, how would my report be handled if I spent time on one?

Thats hard to say, but it provides a reference and a starting point for people who want to work on it.

If you have time left, I think it is also beneficial to inform for degraded accessibility in PRs with UI changes.

Quiet public

@Beowulf When you say that PRs are blocked if UI accessibility issues are "detected", detected by whom or what?

Quiet public

@jscholes There is an accessibility team, but in the end everyone can do a review and if it is valid it needs to be addressed.

codeberg.org/forgejo/governanc

Summary card of repository forgejo/governance
Codeberg.orggovernance/PullRequestsAgreement.md at maingovernance - The Governance of Forgejo