Unsure about new profile nav ? #3

New issue

Open

opened 2024-03-04 21:08:57 -05:00 by freeplay · 2 comments

freeplay commented

2024-03-04 21:08:57 -05:00

I feel it's more confusing as you can't immediately tell what it's supposed to be for, as there's no indicator and seems to blend in too much with the general site nav I think

Another issue would be that screen readers would be reading the profile nav first and not know what it's actually for until after the nav

The profile name could be placed above also but that seems redundant, so am not really sure about that

I feel it's more confusing as you can't immediately tell what it's supposed to be for, as there's no indicator and seems to blend in too much with the general site nav I think Another issue would be that screen readers would be reading the profile nav first and not know what it's actually for until after the nav The profile name could be placed above also but that seems redundant, so am not really sure about that

❤️ 1

h commented

2024-03-04 21:18:03 -05:00

Owner

Appreciated yeah. I really don’t like the navigation forgejo currently has, what I’m doing now (In my opinion, visually at least, definitely have concerns about the screen reader point of view and thanks for mentioning that) is better, but I’ve got more ideas for later (I recognise I shouldn’t be doing this on the live site when it’s incomplete) which will address this.
I do talk about these changes with friends before I make them but of course git.gay is at a point where that’s not communicating with enough of the users for that to be good enough. I don’t quite know what to do about that. I’d use the @besties@social.besties.house fedi account but it’s so much smaller than git.gay.
Anyways, yeah, I’m very open to suggestions on this and how I should go about getting feedback on these ideas before doing them in the future! Thank you so much :)

Appreciated yeah. I really don’t like the navigation forgejo currently has, what I’m doing now (In my opinion, visually at least, definitely have concerns about the screen reader point of view and thanks for mentioning that) is better, but I’ve got more ideas for later (I recognise I shouldn’t be doing this on the live site when it’s incomplete) which will address this. I do talk about these changes with friends before I make them but of course git.gay is at a point where that’s not communicating with enough of the users for that to be good enough. I don’t quite know what to do about that. I’d use the @besties@social.besties.house fedi account but it’s so much smaller than git.gay. Anyways, yeah, I’m very open to suggestions on this and how I should go about getting feedback on these ideas before doing them in the future! Thank you so much :)

❤️ 1

h pinned this 2024-03-04 21:18:11 -05:00

h referenced this issue from a commit

2024-03-07 19:38:13 -05:00

Merge pull request 'Add a new test for "Unspecified" pronouns' (#3) from algernon/feat/pronoun-field/unspecified-test into feat/pronoun-field

h commented

2024-04-23 14:46:17 -04:00

Owner

Another issue would be that screen readers would be reading the profile nav first and not know what it's actually for until after the nav

Regarding this point, it's actually inside a container with an aria-label, so it's clear it's for the user. Still up for this to be thought through a bit more though

> Another issue would be that screen readers would be reading the profile nav first and not know what it's actually for until after the nav Regarding this point, it's actually inside a container with an aria-label, so it's clear it's for the user. Still up for this to be thought through a bit more though

No labels

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: gitgay/forgejo#3

No description provided.