1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-14 09:42:09 +00:00
seirdy.one/content/notes/sourcehut-accessibility.md
2022-06-30 12:44:02 -07:00

14 lines
1 KiB
Markdown

---
title: "Sourcehut accessibility"
date: 2022-06-30T12:38:21-07:00
replyURI: "https://social.tchncs.de/@jookia/108567653359611884"
replyTitle: "Sourcehut is pretty poor accessibility-wise too"
replyType: "SocialMediaPosting"
replyAuthor: "Jookia"
replyAuthorURI: "https://www.jookia.org/"
---
I won't pretend that the Sourcehut accessibility situation ideal, but it's usable for the most part with assistive technologies IME. From what I can tell, it doesn't have critical issues like hidden/un-focusable items, interactive widgets that don't change states, keyboard traps, etc. The only other forge that generally passes that is GitHub.
Core functionality all works, but ancillary functionality and quality-of-life could use some significant improvements. I'll file some tickets later today; they're generally easy to fix. Some that come to mind are using additional `<nav>` elements with different labels, and naming in-page heading anchors.
Edit: just saw [your thread on Sourcehut accessiblity](https://social.tchncs.de/@jookia/108567672375976987), I'll take a look.