<html><head></head><body style="zoom: 0%;"><div dir="auto">Github has had to be pushed quite a bit in the past to make accessibility fixes as one of our folks at my project and LumoSQL found in 2020.<br><br></div>
<div dir="auto">The linked accessibility post was over a year ago, but gitea are now working with folks like Devin Prater to improve on their accessibility. <br><br></div>
<div dir="auto">I can confirm that codeberg has some accessibility issues. <br><br></div>
<div dir="auto"><a href="https://blog.brettsheffield.com/a11y">https://blog.brettsheffield.com/a11y</a><br><br></div>
<div dir="auto">There's also been some discussion recently on the Fediverse about <a href="http://codeberg.org">codeberg.org</a> sign up process and accessibility workflow.<br><br></div>
<div dir="auto"><a href="https://codeberg.org/Codeberg/Community/issues/479">https://codeberg.org/Codeberg/Community/issues/479</a><br><br></div>
<div dir="auto">Codeberg would like to use a different captcha for signup. Now there are more issues with accessibility than sign up, so there needs to be a process for documentation of the accessibility issues on sites and to do that we need to work closely with folks who have these issues. <br><br></div>
<div dir="auto"><a href="https://mastodon.social/@humanetech/108683748152153409">https://mastodon.social/@humanetech/108683748152153409</a><br><br></div>
<div dir="auto">These processes to report the issues need to be fairly simple. Otherwise folks get frustrated and end up excluded from projects. <br><br></div>
<div dir="auto"><a href="https://github.com/go-gitea/gitea/pull/20458">https://github.com/go-gitea/gitea/pull/20458</a><br><br><br></div>
<div dir="auto"><a href="https://mastodon.social/@humanetech/108673514211178268">https://mastodon.social/@humanetech/108673514211178268</a><br><br></div>
<div dir="auto">These things do take time, but it should not be something that's dropped until enough people yell about the issue.<br><br></div>
<div dir="auto">Of course projects are often small and there's a lack of resources to fix. But that's why we are on this list. To work on the issues. <br><br></div>
<div dir="auto">Best regards <br><br></div>
<div dir="auto">Esther <br><br></div>
<div dir="auto"><!-- tmjah_g_1299s -->Sent from <!-- tmjah_g_1299e --><a href="https://bluemail.me"><!-- tmjah_g_1299s -->BlueMail<!-- tmjah_g_1299e --></a><!-- tmjah_g_1299s --> <!-- tmjah_g_1299e --></div>
<div style="font-size:10.0pt;font-family:"Tahoma","sans-serif";padding:3.0pt 0in 0in 0in">
<hr style="border:none;border-top:solid #E1E1E1 1.0pt">
<b>From:</b> HF <hf@pixelplanet.fun><br>
<b>Sent:</b> Wed Jul 27 23:03:00 GMT+02:00 2022<br>
<b>To:</b> give-up-github@lists.sfconservancy.org<br>
<b>Subject:</b> Re: Add note about inaccessibility<br>
</hf@pixelplanet.fun></div>
<br>
<pre class="blue">On Thursday, 30 June 2022 at 19:20:58 CEST, Jookia wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> All have significant flaws in accessibility compared to GitHub.<br> <br> It would be nice to add a note that the trade-off for using these tools<br> is excluding disabled people from your projects.<br></blockquote><br>Might be good, but that should be a bit more specifc than just<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">you will excluse disabled people<br></blockquote>Like what exactly the issues are. Gitea did actually put work into <br>accessibility recently.<br><a href="https://github.com/go-gitea/gitea/issues/16660">https://github.com/go-gitea/gitea/issues/16660</a><br><br><br><hr><br>Give-Up-GitHub mailing list<br>Give-Up-GitHub@lists.sfconservancy.org<br><a href="https://lists.sfconservancy.org/mailman/listinfo/give-up-github">https://lists.sfconservancy.org/mailman/listinfo/give-up-github</a><br></pre></body></html>