Using Git, GitHub CLI, and Copilot CLI with a Screen Reader
Using Git, GitHub CLI, and Copilot CLI with a Screen Reader Guide Topics Skip to content A guide for screen reader users who want to work with Git and GitHub entirely from the command line. This guide covers installing and configuring Git, using Windows Terminal, working with the GitHub CLI, and using Copilot CLI as a terminal assistant. Who this guide is for This guide is for developers and technical contributors who use a screen reader and want to interact with Git and GitHub from the terminal rather than through a web browser or desktop application.
It assumes basic familiarity with navigating a computer with a screen reader, but no prior experience with Git or GitHub. The guide uses NVDA on Windows as the reference screen reader, but the commands and workflows apply to any screen reader and any terminal that supports standard keyboard input. What you will need Before starting, make sure you have: A Windows computer with administrator access (needed for installing software) A screen reader (this guide references NVDA, but JAWS, Narrator, or other screen readers work as well) A GitHub account (sign up at github.com if you do not have one) An internet connection for downloading installers and authenticating with GitHub How this guide is organized The guide follows a local-to-remote progression: Part 1: Git CLI covers installing Git and learning the commands you need to work with files and commits on your own computer.
Part 2: GitHub CLI covers installing the GitHub CLI ( gh ) and using it to create pull requests, manage issues, and interact with GitHub without opening a browser. Part 3: Copilot CLI covers installing GitHub Copilot CLI and using it as a conversational terminal assistant that translates plain language into commands. Common Workflows brings it all together with end-to-end examples that chain Git and GitHub CLI commands.
Part 1: Git CLI Git is the version control system that tracks changes to your files. The commands in this section all happen locally on your computer. You do not need an internet connection or a GitHub account to use them. Installing Git for Windows Download the installer from the Git for Windows download page . The page has tabs for different operating systems. Make sure the Windows tab is selected, then follow the download link.
Launching the installer Open File Explorer and navigate to the Downloads folder. Find the installer file. Your screen reader announces the file name, which includes “Git” followed by the version number and system architecture – for example, “Git-2.54.0-64-bit.” Press Enter to launch the installer. Windows displays a User Account Control (UAC) prompt. Your screen reader may announce “Secure Desktop” and go briefly silent before the dialog appears.
Press Alt+Y to allow the installation, or Tab to the Yes button and press Enter. Step-by-step installer walkthrough The Git for Windows installer presents a series of screens, each with a question or set of options. Every screen has keyboard shortcuts for its buttons: Alt+N for Next, Alt+B for Back, Alt+I for Install, and Alt+F for Finish. Accessibility note : Several installer screens use radio button groups where the group heading (the question being asked) is not announced by the screen reader.
Your screen reader reads the radio button text but not the surrounding context. If you are unsure what a screen is asking, use your screen reader’s object navigation (for example, NVDA+Numpad keys) to read the full screen content. This guide describes what each screen is about so you know the context before navigating the controls. License screen The first screen shows the GNU General Public License, which governs how Git’s source code can be used and distributed.
Focus lands on the Next button. No action is needed here beyond continuing. Press Enter to proceed. Destination folder An edit field shows the default installation path ( C:\Program Files\Git ). Leave the default path unless your organization requires software to be installed in a different directory. This is where Git’s executable and supporting files will be stored. The default location keeps Git accessible from the system PATH.
Tab to the Next button and press Enter to continue. Select components A tree view with checkboxes lists the components to install. Use arrow keys to navigate the tree. Use Space to toggle each checkbox. Your screen reader announces each item with its checked or unchecked state. Take a moment to review the following settings. Windows Explorer integration : Leave this enabled for most workflows. This adds Git options to the right-click context menu in File Explorer, which can be a convenient way to open a terminal in any folder.
Checked by default. Add a Git Bash Profile to Windows Terminal : Enable this option if you plan to use Windows Terminal (recommended), to save yourself from having to configure the profile manually later. This adds Git Bash as a profile you can open directly from Windows Terminal. Not checked by default. Check daily for Git for Windows updates : Enable this in development environments where you want the latest features and security fixes.
Leave it unchecked in environments where updates need to be managed on a controlled schedule. This keeps Git up to date by checking for new versions automatically. Not checked by default. The remaining components – Git LFS, file associations, and Scalar – are configured with sensible defaults for most development workflows. Leave them as they are unless you have a specific reason to change them. Select Next to continue.
Start Menu folder An edit field shows the default value “Git” for the Start Menu folder name. Leave the default name. It is clear and recognizable. This determines where Git appears in the Windows Start menu. The Start Menu entry provides a way to launch Git Bash or Git GUI from the Start menu, but it does not affect how Git works from the terminal. Select Next to continue. Default editor A combo box (dropdown) for selecting the text editor Git uses when it needs you to write or edit text, such as commit messages.
Select Visual Studio Code if you already use it. It has strong screen reader support and numerous accessibility features. Otherwise, the default (Vim) is a widely used terminal-based editor. The editor can be changed later with git config --global core.editor , so this is not a permanent decision. Use arrow keys to browse the options, then select Next to continue. Default branch name The default branch is the starting branch Git creates when you initialize a new repository.
Branches are how Git lets you work on different changes independently – the concept is explained fully in the Creating and switching branches section later in this guide. Two radio buttons are available. Leave the default selected, since most teams configure the branch name as part of their project setup: Let Git decide (default recommended): The branch name is typically configured as part of project setup, not during installation.
Override the default branch name for new repositories : Select this only if you want to specify a custom name during installation rather than configuring it later. Use arrow keys to navigate between options, then select Next to continue. PATH environment This screen asks how Git should be made available from the command line. Three radio buttons are available. Leave the default selected for broad terminal compatibility without risking conflicts: Use Git from Git Bash only : Select this only if you want Git commands to work exclusively inside the Git Bash terminal.
Git from the command line and also from 3rd-party software (default recommended): It makes Git available from any terminal without risking conflicts with existing Windows commands. Use Git and optional Unix tools from the Command Prompt : Avoid this option unless you specifically need Unix commands in the Windows PATH. It adds Unix commands (like find and sort ) to the system PATH, which can conflict
The rest of this page is on the live site.