-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add accessibility entry in user menu #34069
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, a suggestion: we use the A11y icon instead of the theming icon https://fonts.google.com/icons?selected=Material%20Icons%20Outlined%3Aaccessibility_new%3A
@szaimen I thought of this but don't think it's critical. It would also mean that whenever you manually click on that navigation, the entry on the top right would also need to be highlighted. Might need a hacky solution for this. |
look at https://github.com/nextcloud/server/pull/33756/files#diff-0fc396967e1f9523319e6bbfd0d6877a8a6e5db7a7896697404c19ea896f734dR137-R140. Maybe it helps figuring out a solution |
@szaimen as per screenshot, the active item is now fixed, thanks a lot for the useful pointer please re-review! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm now but acceptance-header failure is related!
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
5427aaa
to
da01494
Compare
solved |
S3 failure unrelated |
I understand the wish to make this submenu easier accessible. However, I think it's inconsistent in terms of "now we have three links to the same side menu" – two main entry points (user, admin) and one sidemenu subentry on top of it. If theming and accessibility were a complete separate side menu, then I'd agree. This way, I don't. But that's not my decision. BUT: Even the icons used are inconsistent. THAT should be decided upon which one to use consistently: |
@nursoda yes, understandable – however all of the requirements for having each of the entries quickly accessible are valid. Initially we only had "Settings", then it was cumbersome for admins to get to admin settings quickly, or not clear that this was also there. And "Appearance and accessibility" needs to be reachable quickly to help people in need of assistive technology. Regarding the icon, yes for sure. @szaimen could you change the icon of "Appearance & accessibility" in the settings to the one we use in the menu (the "human")? Admin theming can keep its icon to distinguish. |
WIP: #34170 |
For #33736
Note: if the theming app is disabled the entry will remove itself.