Skip to main content

Moving from #Github to #Codeberg (as my main #Git account) is completely flawless :heart_cybre: I wish it'd be possible that many other projects I follow could've moved there...
#codeberg #github #git
This entry was edited (1 year ago)
in reply to ilias

André Polykanine
André Polykanine
• •
If Codeberg (in fact, Gitea) was as accessible for screen reader users as Github is, then that would be a great move.
in reply to André Polykanine

Caesar
Caesar
• •

@menelion I am starting work on improving the accessibility of @forgejo (and thus @Codeberg) over the coming months. I know there is a lot to be done. But if you have any suggestions of things that are _especially_ bad that make Forgejo hard or impossible to use, please let me know. It might be hard to file issues if Codeberg isn't accessible to you, so feel free to message me directly here or on Matrix. Cheers!

@DM_Ronin

@André Polykanine @ilias @Codeberg.org @Forgejo

Peter Vágner reshared this.

in reply to Caesar

André Polykanine
André Polykanine
• •
@caesar @forgejo @Codeberg Especially hard is to review pull requests. You cannot comment lines of code, this process is totally inaccessible and I even don't know how to tackle it best, frontend is very… specific, so to say, or it's because I'm a backender.
@Caesar @Codeberg.org @Forgejo
in reply to André Polykanine

Caesar
Caesar
• •
@menelion Thanks for the useful feedback. I can see that PR reviews in particular could be a challenging area to solve – if GitHub is better in this regard it will be instructive to look at how they solved that. I'll be making some architectural changes to the front-end code first, but later I might contact you for feedback on changes I make if that's ok with you.
(I do also realise you have sent some feedback before to other team members; thank you for that.)
@forgejo @Codeberg @DM_Ronin
@André Polykanine @ilias @Codeberg.org @Forgejo
in reply to Caesar

André Polykanine
André Polykanine
• •
@caesar @forgejo @Codeberg It's totally OK, but please use Mastodon, email, Telegram, but not Matrix as at least for me it's also super painful accessibility-wise. I did one small improvement in Gitea regarding headings navigation for comments in issues. As for Github, they also implemented it on my request. They have a plus button next to each line, which is not a button really. So they added a corresponding ARIA role and provided it with text "Add line comment". They however didn't add accessibility for multi-line commenting which I've been asking for like one and a half years.
@Caesar @Codeberg.org @Forgejo
in reply to André Polykanine

Caesar
Caesar
• •
@menelion Thanks, that's useful to know. I wonder if for multi-line commenting keyboard navigation like in Gmail would be useful? So you could use up/down keys to highlight lines and X or space to select? @forgejo @Codeberg @DM_Ronin
@André Polykanine @ilias @Codeberg.org @Forgejo
in reply to Caesar

André Polykanine
André Polykanine
• •
@caesar Usually we use virtual cursor or its equivalent on Github when reviewing pull requests, so it's really not intuitive. Otherwise, how to read diffs? I'd prefer something like that: line numbers themselves are clickable and have semantic role of toggle buttons. So basically, I'd click number 5, then click number 10, so a field opens wheree I could comment on lines 5 through 10. Your Gmail example probably would be OK, but again, how do we navigate then?
@Caesar
in reply to André Polykanine

Caesar
Caesar
• •
@menelion that makes perfect sense. If you don't mind, I'll paste some of this feedback into a Codeberg issue later to keep track of it when I get round to implementing this.
@André Polykanine
in reply to Caesar

André Polykanine
André Polykanine
• •
@caesar Feel free. Of course you can mention me also. codeberg.org/Menelion

Andre Polykanine

A married and happy geek from Ukraine living in Mannheim, Germany. Working as a software engineer at InterNations. Accessibility, development, reading, languages and music are my passions.
Codeberg.org
@Caesar
in reply to André Polykanine

Caesar
Caesar
• •
@menelion For reference: codeberg.org/forgejo/forgejo/i…

[ACCESSIBILITY] PR review is not accessible to screen reader users

[Reported on Fediverse](https://dragonscave.space/@menelion/110679713699812355) by @Menelion. Copying here for future reference. - Forgejo version (or commit ref): v1.19 ## Description @Menelion: > Especially hard is to review pull requests.
Codeberg.org
@André Polykanine
in reply to Caesar

Mikołaj Hołysz
Mikołaj Hołysz
• •
@caesar @menelion @Codeberg I’d say that figuring out the captcha situation should be your first order of business. The “contact us” approach is a terrible idea.
@Caesar @André Polykanine @Codeberg.org
⇧