fix: make top nav bar right elements within a nav - #63239
Conversation
384a1bd to
4551f67
Compare
susnux
left a comment
There was a problem hiding this comment.
This part looks good, likely needs adjustments in the vue library for NcHeadMenu to set role = menuitem
|
@susnux Regarding updating role of NcHeaderMenu to |
|
@kristian-zendato which other place is using it? It must only be used within that header bar thats its full purpose. |
|
@susnux I checked that again and yes, they are only used in header. |
yes |
@susnux Why?
Semantically, this is not about any set of buttons but a complete actions set. Like this one: I can see how it can be used as an application menu, but even in this case, it is usually about the classic application menus ( Technically, a menubar must have menu keyboard navigation, for example:
So if we keep it a menubar, we must implement it as a menu bar. What about |
You are right! The proper role is likely |
4551f67 to
ff48cf3
Compare
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
| <nav class="header-end" aria-label="<?php p($l->t('Header menu')); ?>"> | ||
| <ul class="header-end__items" role="toolbar"> | ||
| <li class="header-end__item" role="none"> | ||
| <div id="notifications"></div> | ||
| </li> | ||
| <li class="header-end__item" role="none"> | ||
| <div id="contactsmenu"></div> | ||
| </li> | ||
| <li class="header-end__item" role="none"> | ||
| <div id="user-menu"></div> | ||
| </li> |
There was a problem hiding this comment.
So the plan would be now:
- remove role none from li
- remove role toolbar
- = keep this as a simple list
- change label as "header menu" is too unspecific
Signed-off-by: kristian-zendato <kristian.zendato@nextcloud.com>
09c5907 to
4ae9e88
Compare
| <div id="contactsmenu"></div> | ||
| <div id="user-menu"></div> | ||
| </div> | ||
| <nav class="header-end" aria-label="<?php p($l->t('Notifications, contacts and settings')); ?>"> |
There was a problem hiding this comment.
@nimishavijay or @kra-mo do you have a better idea how to label the section of the navigation here? (the part including notifications, assistent, contacts etc)
There was a problem hiding this comment.
They are all rather distinct apps there, and if anyone using a screenreader heard something generic for this category like "More apps" or something like that, they may skip over it entirely.
If there is any way we can take them out of this section and have them be directly accessible that would be the best from a UX persepctive. If that's not possible then I'd suggest "Nextcloud Assistant, notifications and settings" to indicate the most commonly used apps.
In the future we could also think about moving the assistant to the center section as it's closer in function to searching, then the top right group could become "Notifications and settings" which makes more sense in my head.
@kra-mo any thoughts here since you worked on the new layout?
There was a problem hiding this comment.
The original proposal did have Assistant next to search, but I wonder about the balance if we have suggested apps on the left in the future.
As for the label, considering it also includes the people menu for example, I really am not sure what to call it. I do think something generic may be the best, but without using the word "app". For regular users, I would reserve that word for apps in the grid. Maybe "Actions and options"?

Summary
navelement.Checklist
3. to review, feature component)stable32)AI (if applicable)