@sir has released new results on forgeperf.org/.

A great shout-out to user mappu04 who identified the roadblock that made us look bad in previous run!

The worst-case results for huge repos still a known open issue, potentially resolved by caching in coming gitea release.

NOW OUR CALL FOR CONTRIBUTION: If you agree with us that accessibility is important, and would like to help resolving the accessibility issues tagged in the report: please have a look and consider a pull request!

@laufi @codeberg @sir Fortunately, Lighthouse results aren't anywhere near descriptive as to what is wrong with the site (and it is still possible to get a 100% a11y score and have a completely inaccessible site) - I'd appreciate personal 1to1 guidance for a contribution as I'm not at all familiar with Codeberg's project structure, building process, etc.


@nwng @laufi @sir please don't hesitate to contact us with all questions you encounter!

@codeberg @laufi @sir Oh, I didn't realize you're actually using Gitea. Gitea doesn't have many open issues on accessibility at the moment and those open seem to be abandoned by the maintainers - they're also marked as proposals and not as bugs/breaking issues - what they actually are. The issues too have persisted over a very long time in the software and I reckon that a rewrite of the entire UI with a11y focus would be much easier than to implement this now.

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!