Accessibility

The items inside of Assignees and Clear Assignees require a user to tab to the submenu items versus use down/up arrows.

Labels option does not follow typical keyboard actions.

In Desktop for Windows and Mac, “Close” button control does not have close option in the keyboard tab order. User has to hit Esc key to cancel changes.

On Desktop for Windows, context menus key off of the mouse versus the parent control.

On Desktop for Windows and Mac, the Co-Author button is not keyboard navigable.

GitHub desktop applications are built using platform-specific standards and best practices where possible.

The Filter control on the web client does not receive keyboard focus.

When changing color value on Labels button, focus unexpectedly moves to top of page.

When activating certain controls such as “delete” button for labels and links from buttons, expanded filters or filtered search results, focus does not move to the new dialog.

When creating a “new issue,” focus does not move automatically to the title field.

Focus order when creating a “new issue” is not logical.

Focus does not go to user name/repo name, when activating “Skip to Main” button.

In GitHub Notifications page, notifications are read out of logical order.

When activating the branch dropdown menu, focus is not visible on “Skip to Content” link.

On the Windows Desktop client, focus does not move to the first actionable item after sign in.

On Desktop for Mac, add co-authors button is not keyboard focusable and focus is not visible on comments section.

For web and GitHub client experiences, when making an edit to the markdown of the GitHub ReadMe file, the field is not announced as editable and “no new line at end of file” icon is not announced by screen reader.

Across a number of areas in the GitHub Marketplace and Desktop for Windows and Mac experiences, selected elements are not announced as selected and decorative elements are not skipped by screen readers.

Throughout GitHub sites and Desktop client experiences, links are only described as links without additional context. For example, in GitHub repositories, new links are described only as new link without additional context. Social media links (e.g., GitHub Twitter link) are only described as “link.”

Assignees button, and type or choose name control do not have the correct accessible control name.

No additional announcements are made after making a pull request although there are visual displays of errors and other information.

On web experiences and Desktop for Windows, when reviewing search results data, checkboxes for labels and select all issues checkboxes do not have accessible names.

On GitHub Help page, search button does not have the control type described.

On GitHub Repo Settings Collaborators, the dismiss message button is announced before message is read and “Delete this repository” dialog sets focus to input field and ignores accompanying text.

When not signed in, button names are not read (such as Watch or Fork) and instead, you must be signed in is read when landing on the control.

On Desktop for Windows, default branch, recent branch and other branch headings are not announced by screen readers.

On Desktop for Mac, when using delete branch button, the button state change to “restore branch” is not announced.

On Desktop for Windows, Continue dialog and Finish button do not trigger focus change to new dialogs when activated.

On Desktop for Windows, Co-Author edit box does not have an accessible name.

On Desktop for Windows and Mac, when when using “Fetch Origin” button and “Publish” button additional information when button state changes (e.g., fetch origin never fetched) is not announced by screen reader.

On Desktop for Windows and Mac, new lines of code are announced as buttons.

On Desktop for Windows, file viewer control does not have an accessible name.

On Desktop for Windows and Mac the blue dot indicating status message on history is not announced.

All iconography are rendered via the Octicons library.

System wide contrast, font-size and other accessibility preferences are respected throughout the application except the Desktop for Mac client does not respond to high contrast settings.

Visual line diffs are annotated with standard “+” and “-“ notation to indicated additions and removals, but may not be available to screen readers on Desktop for Windows and Mac clients.

Applications have no flashing or blinking elements.

When making an edit to the markdown of the GitHub ReadMe file, the field is not announced as editable.

No additional announcements are made after making a pull request although there are visual displays of errors and other information.

Assignees button and “Type or choose a name edit field” have accessible names that do not match the visual control names.

Input errors on GitHub.com sign up and sign-in pages on Desktop for Windows and Mac are not announced.

All non-text navigation and functional elements are accompanied by text descriptions. Some non-navigation, non-functional visual elements, such as a user’s contributions graph may not be accessible to assistive technology.

Additionally, when a users submits non-text content (e.g., an image in a issue comment), Markdown’s syntax requires alternative text be provided.

No multimedia presentations (other than the occasional animated GIF) are used.

Visual line diffs are annotated with standard “+” and “-“ notation to indicated additions and removals.

GitHub uses modern, text-based, semantic web development practices, and does not rely on non-HTML plugins or applets such as Java, ActiveX, or Flash except where otherwise noted for non-essential functionality.

No server-side image maps are used.

No client-side image maps are used.

GitHub Enterprise dashboard has a table that is not identified as a data table.

No frames are used for navigation. An iframe is used to render visual representations of some user content such as maps.

Where an interaction is not possible through the web interface, it may be accomplished through text-only means through the Git command-line desktop software.

The only plugin used is a flash-based tool for simplifying the task of copying text visible on the page (such as a commit’s unique id) to the user’s clipboard. The task may be accomplished through the operating system’s standard copy and paste functionality.

On GitHub Enterprise and the GitHub Desktop client, the user must tab through repetitive links as there is no skip to main content.

Timed responses are not required.

Training materials available at youtube.com/github and youtube.com/githubguides. All GitHub videos are fully closed captioned.

For more information on YouTube’s accessibility see support.google.com/youtube/answer/189278

Training videos posted via YouTube video player do not include audio description.

Viewers may toggle closed captioning using YouTube’s native closed-captioning functionality.

Account management and social interaction scenarios for each of the GitHub offerings covered by this VPAT have focus order, name, role, value, accessible name, and info and relationship issues that may prevent some scenarios from being completed.

Zooming to certain levels will cause info on the screen to be pushed off and require horizontal scrolling. This is particularly impactful when accessing GitHub web offerings or experiences on mobile devices.

For each of the GitHub offerings covered by this VPAT, there is insufficient color contrast on a number of links, dialogs and controls.

Products do not require auditory feedback.

Products do not use auditory feedback.

Products do not require speech input.

Submenus and other control areas may require using irregular keyboard actions such as tabbling versus up/down arrows and focus order for creating and managing issues in GitHub is illogical.

Please contact support@github.com with any such requests.

Documentation available at government.github.com/accessibility

Support provided via web and email