Looked at the pull request interface of #Forgejo. With a #screenReader 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 #accessible than on #GitHub. #accessibility
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!
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?
Beowulf
Als Antwort auf James Scholes • • •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!
James Scholes
Als Antwort auf 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?