Scroll to Top Implementation

[bloo-berries]

Select Topic Area

Question

GitHub Feature Area

UI/UX

Body

For blind/low vision nav, can we implement a native platform "scroll to top" button for repos/other relevant pages?
I don't see it currently, but it would wildly help the nav for long repos/discussion pages, etc.

Rationale for it being an accessibility feature is that I'm blind/low vision, and have found it difficult to navigate some long form content and losing my place/code spatial awareness 😂

I know there are browser extensions or custom scripts, but a native button would be great for accessible navigation.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[queenofcorgis]

Hi there @bloo-berries 👋🏼 ,

Thanks for sharing this feedback I have gone ahead and reported this as this is already something available in the Discussions feature.

In the meantime, you don't need a browser extension or custom script to quickly scroll back to the top of a page, another option is a keyboard shortcut. For Chrome: Command/Control + the Up arrow, I recommend searching your browser + device type to get the proper shortcuts.

[bloo-berries]

Hey, @queenofcorgis - please see @jecisc comment below as well. Other users have also shared that this feature could be really helpful for repo nav, whether or not its strictly an "accessibility" feature.

Maybe implementing a Github native feature similar to reddit's up/down scroll button to nav forums more easily would be beneficial.

Because, to your point - devs often have different key bindings for shortcuts which may change how they nav on a page, and even if/when using the command you suggested - this doesn't always "scroll" the page, it often only moves within the selected window.
For example, this text box/alt buttons surrounding the text box.

[jecisc]

Hi,

I would love to have this feature in the Github Action pages!
The logs are often pretty long and it takes a while to scroll up. I miss a scroll to top option one those pages. Is it the right place to indicate a "+1" on this feature request? :)

[bloo-berries]

hey @jecisc - ty!
I was thinking a nav/scroll button similar to what's implemented on Reddit would be SO helpful for long form content, long repos/etc.

A visible scroll-to-top button offers immediate access to the top of very long pages, like project READMEs, discussion threads, or complicated Action logs, without relying on browser shortcuts or manual scrolling.

[bloo-berries]

My other suggestions/rationale for this implementation are:

• Not all users are aware of or able to use browser- or operating system-specific shortcuts (such as Ctrl+Up Arrow), especially on mobile devices, tablets, or when using custom keyboard bindings. A universal on-screen button ensures consistency
• On smartphones and tablets, scrolling through long pages can be tedious without a physical keyboard or native "jump to top" gesture.
• Quickly returning to the top improves productivity, especially when reviewing documentation, large issues/discussions, CI/CD logs, or repo settings. Developers often need to reference navigation bars, tabs, or page-level tools found only at the top.

Benefit to Copilot:

• users instantly return to the beginning of coding sessions, especially when reviewing multi-line completions or custom Copilot instructions within .github/copilot-instructions.md files
• Improve integrated web-based Copilot agent interfaces (e.g., in pull requests or repos) by providing faster access to menus and project metadata after working through large outputs or generated sections.
• Improve task-switching speed during iterative refinement loops, where developers frequently return to the initial query or command origin.

GitHub Actions:

• Allow users to easily jump back to workflow summaries, run controls, or “Re-run job” actions located at the top without manually scrolling.
• Improve accessibility across browsers and devices, where log truncation and responsiveness already pose performance and usability challenges.

Accessibility Rationale:

• For users with motor impairments, repetitive scrolling or precise gesture navigation may be difficult.
• Help screen reader users locate contextual navigation areas or skip repetitive markup, improving the experience documented in GitHub’s accessibility guide for PRs.

And even as it stands on this forum page, with your original suggestion, I had to change my key bindings, click out of this text box, then use the shortcut just to the top to get back to my own native navbar.

[bloo-berries]

@queenofcorgis

[meharshjaincom]

I have one additional idea: a “scroll to top” button could also support keyboard and screen reader focus management. For example, when activated, it could automatically move focus to the main navigation bar or page heading, helping users who rely on assistive technologies know exactly where they are on the page.

This would make it more than just a convenience feature and it would directly improve accessibility for blind/low-vision users.

[sjprograms]

This would be a great addition to the PR page. When requesting a copilot review, the page becomes very long with all the suggestions and comments. After submitting the merge, it is a long way to scroll back to the top to access the navbar.

Basically, anytime the navbar leaves the visible page, a scroll-to-top button should appear.

[bloo-berries]

Wish we could get a response on this, because it seems to be an ongoing issue for a lot of code reviewers/accessibility features.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[bloo-berries]

Not dormant, awaiting a response/resolution to the feature implementation for disabled programmers.

[jecisc]

+1

[shivrajcodez]

This is actually a really solid accessibility suggestion.

On long repository pages (README files, large issue threads, or long discussion pages), navigation can become difficult, especially for users relying on screen readers, magnification tools, or reduced-vision workflows. A native “Scroll to Top” control would make it significantly easier to quickly return to the repository header, navigation tabs, or search controls without needing to manually scroll through large sections of content.

While browser extensions or custom scripts can provide similar behavior, relying on them shifts the responsibility to the user. A built-in control would provide a consistent and predictable navigation mechanism across GitHub, which is generally preferable from an accessibility perspective.

A few implementation ideas that could work well:

A floating “scroll to top” button that appears after the user scrolls past a certain threshold.

Ensuring the control is keyboard accessible and reachable through standard tab navigation.

Adding an ARIA label (e.g., aria-label="Scroll to top") so screen readers clearly announce its purpose.

Smooth scrolling back to the repository header or main navigation area.

GitHub already does a lot of good work around accessibility, so this would be a relatively small UI addition that could meaningfully improve navigation for users dealing with long pages.

Overall, this feels like a practical accessibility enhancement rather than just a convenience feature, especially for users navigating large discussions or documentation-heavy repositories.

[Josvanegmond]

I think this is a good idea. There is a Return to top button on this page. Why not on other pages that grow very long?

Additional note: I don't think the button on this page is very useful for keyboard users, if you try to reach it with the focus the page will automatically scroll up and it disappears.