Recent searches
Search options
If anyone has time to help the lovely @codeberg@mastodon.technology folks with improving accessibility, please take a look at this issue:
Codeberg.orgCodeberg AccessibilityIn #389 it was reported that text editors were not accessible yet.
Given that such a central piece of the software it not accessible by screen readers (and spell checkers for the matter) yet, it's very likely that there are other UI roadblocks, too.
I'd love to improve this and take the power of Codeberg to move on here. I'm opening this issue to collect open issues that are already identified, discuss new eventual issues and / or talk about asking for an audit of the software.
Also we should talk about QA to make sure that UI changes / framework migrations etc do not introduce new accessibility issues.
Of course this needs a close collaboration to the upstream developers, but first opening here to collect the material necessary and talk about how Codeberg can support this mission.
---
## Edit: Current status
Accessibility for Gitea is an ongoing issues, the most important problems currently
- comment editor not accessible, WIP upstream https://github.com/go-gitea/gitea/pull/15394
- our captcha is only possible with good eye vision and hard, we need alternatives like audio captcha or honeypots (https://github.com/go-gitea/gitea/issues/11426)
- we don't know what else needs improvement and we're looking for someone to audit Gitea
- interactive elements don't always carry a description / don't read in screen readers, see https://codeberg.org/Codeberg/Community/issues/479#issuecomment-633066
ᶤѕ€𝔤𝐫Į𝓂𝓶 
_1st. 