RocketChat / RocketChat/Rocket.Chat

Feature Proposal: Improve Navbar Accessibility on Mobile and Tablet Screens

Open
#38,676 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: feature
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

📝 Summary

On medium and mobile screen sizes, the top navigation bar progressively hides several important navigation buttons (e.g., Marketplace, Directory, Display).

While this is part of the current responsive behavior, it may reduce discoverability and accessibility of key features.

This proposal suggests introducing a consolidated "More" (overflow) menu to maintain access to all primary navigation actions when screen width is limited.


📌 Current Behavior
  • On large screens, all primary navigation buttons are visible:

    • Home
    • Directory
    • Marketplace
    • Pages
    • Sidebar
    • Create New
  • On medium screens, several buttons are hidden.

  • On mobile screens, some features become difficult to access or are nested inconsistently.

This may reduce usability and discoverability for users on smaller devices.


📷 Screenshots


💡 Proposed Improvement

When screen width falls below the large breakpoint:

Keep 3 primary buttons visible:
  • Home
  • Pages
  • Overflow menu (⋮ or ☰ icon)
Move remaining navigation actions into a structured dropdown menu:
  • Directory
  • Marketplace
  • Display
  • Create New
  • Open Sidebar

✅ Benefits
  • Improved usability on smaller screens
  • Clearer navigation hierarchy
  • Reduced cognitive load
  • Better discoverability of features
  • Consistent responsive navigation pattern

🧪 Environment
  • Rocket.Chat branch: develop
  • Browser: Chrome (latest)
  • Operating System: Ubuntu 25.10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the responsive top navigation entry point and the breakpoint logic that hides actions on medium and mobile screens. Review how existing navigation menus expose Directory, Marketplace, Display, Create New, and the sidebar. Done means the proposed primary actions remain visible, the remaining actions are available through an accessible overflow menu, and the behavior is consistent across the described screen sizes.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
accessibility, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.