Zum Inhalt der Seite gehen


#Blind users, users that rely heavily on #keyboardNavigation or anyone else with a preference on that matter (please indicate what applies in the comments):

Do you have a preference for or comments on the format of URLs? During user research, we have learned that URLs that are easy to handle are a good thing.

We are currently considering to introduce URLs that do not need more reserved usernames in #Forgejo, such as codeberg.org/-/something/ or codeberg.org/_something/.

#a11y #accessibility

Als Antwort auf Codeberg.org

More on the background:

User research: In codeberg.org/forgejo/user-rese…, we talked about URLs that are easy to navigate using the browser (e.g. being easier than navigating within the page), and we have noticed other people that navigate by manually entering or editing the URL from time to time.

In Forgejo, there are currently discussions for new implementation that would benefit from your feedback, see codeberg.org/forgejo/discussio… and codeberg.org/forgejo/forgejo/p…

Als Antwort auf Codeberg.org

Hey, André here. I used to test accessibility functionality with Otto once. First of all, thank you again for caring about accessibility, it's not very frequent in the open-source community, unfortunately. Yes, URLs are extremely important at least for some of us (like me), and here GitHub keeps doing great job. However, I didn't really understand your concern, what was before and what are you planning to introduce? Thank you. Also, you always know where to find me, please write here or to ap (at) oire.me. I'm willing to help.
Als Antwort auf André Polykanine

@menelion The features we are currently about to implement is moderation tooling where submitting and viewing these things is considering to introduce codeberg.org/-/abuse_reports/n… (current proposal) or something similar like codeberg.org/_abuse_reports/ne….

While it is probably a feature that is not visited frequently, it might be good to set a direction for future endpoints that are more prominent.

IIRC, Gitea has recently even moved some routes to the /-/something pattern.

~f

Als Antwort auf Codeberg.org

Sorry, but are /-/ necessary? That's something that adds extra burden, as far as I'm concerned. Why not like codeberg.org/abuse-reports/new?
Als Antwort auf André Polykanine

@menelion I'd guess that'd be because they'd only have to block - or anything starting with _ so people can't create accounts with those names
Als Antwort auf Ember ​

@Ember @menelion

Yeah, the idea is to avoid adding more and more reserved usernames for every route and simply using patterns that are easy to differentiate from user accounts. For example, user accounts could be prevented to start with an underscore and you could do URLs that start with an underscore for "special use".

We wondered if there was a recommendation or best practice that is still acceptable accessibility-wise.

Als Antwort auf Codeberg.org

Als Antwort auf Codeberg.org

@Ember @menelion Thanks so much for caring about screen reader accessibility for Codeberg! Thie issue for screen reader users is whether the dash and underscore characters get read. THe different screen readers handle characters like this in different ways and each has a setting for the user to choose how much they want to hear about punctuation and these characters. I think the underscore is less likely to be skipped by VoiceOver, which is the screen reader I use.
Als Antwort auf Codeberg.org

While I'm not a visually impaired person (outside of just bad eye sight) do I think that URLs using "-" as a sort of separator could be beneficial to have here. It's something platforms like GitLab have and that I believe are better than reserved usernames.
Als Antwort auf Codeberg.org

I don’t really see the problem with reserved usernames. Those endpoints are typically not names you would choose as a username except to cause confusion.

I dislike dashes and underscores in URLs that are directly visible to the user.

That being said, an endpoint such as to report abuse can be under the object it’s meant to represent?

Dieser Beitrag wurde bearbeitet. (3 Wochen her)

Diese Webseite verwendet Cookies. Durch die weitere Benutzung der Webseite stimmst du dieser Verwendung zu. https://inne.city/tos