Accessibility

Voluntary Product Accessibility Template (VPAT) outlining §508 accessibility information for GitHub.com, GitHub Enterprise, and GitHub Desktop.

Please note, when using GitHub.com or GitHub Enterprise, there are four alternate ways to interact with stored content:

  1. Via the GitHub.com or GitHub Enterprise web interface through a modern browser
  2. Via the GitHub Desktop application
  3. Via the GitHub's open application programming interface (API) which provides information in a machine-readable format for integration with other applications
  4. Via the open source Git command line (interactive, entirely text-based) interface

Where support below is indicated below as "Supports with exceptions", such a qualification applies to the particular product being evaluated, however, interactions may be accomplished through alternate means such as via the Git command-line interface.

For more information, please contact [email protected].

Summary

Criteria Level of Support Remarks and explanations
Section 1194.21 Software Applications and Operating Systems Supports with exceptions
Section 1194.22 Web-based Intranet and Internet Information and Applications Supports with exceptions
Section 1194.23 Telecommunications Products Not applicable
Section 1194.24 Video and Multi-media Products Supports with exceptions
Section 1194.25 Self-Contained, Closed Products Not applicable
Section 1194.26 Desktop and Portable Computers Not applicable
Section 1194.31 Functional Performance criterion Supports with exceptions
Section 1194.41 Information, Documentation and Support Supports

Section 1194.21 Software Applications and Operating Systems

Criteria Level of Support Remarks and explanations
(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. Supports with exceptions

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.

(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer. Supports

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

(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes. Supports with exceptions

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.

(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to Assistive Technology. When an image represents a program element, the information conveyed by the image must also be available in text. Supports with exceptions

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.

(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. Supports

All iconography are rendered via the Octicons library.

(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes. Supports
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Supports with exceptions

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.

(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. Supports
(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Supports with exceptions

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.

(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided. Supports
(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. Supports

Applications have no flashing or blinking elements.

(l) When electronic forms are used, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Supports with exceptions

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.

Section 1194.22 Web-based Intranet and Internet Information and Applications

Criteria Level of Support Remarks and explanations
(a) A text equivalent for every non-text element shall be provided (e.g., via 'alt', 'longdesc', or in element content). Supports with exceptions

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.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Not applicable

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

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Supports

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

(d) Documents shall be organized so they are readable without requiring an associated style sheet. Supports

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.

(e) Redundant text links shall be provided for each active region of a server-side image map. Not applicable

No server-side image maps are used.

(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. Not applicable

No client-side image maps are used.

(g) Row and column headers shall be identified for data tables. Supports with exceptions

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

(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. Not applicable
(i) Frames shall be titled with text that facilitates frame identification and navigation Not applicable

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

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Supports
(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. Not applicable

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.

(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology. Supports
(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with 1194.21(a) through (l). Not applicable

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.

(n) When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Supports
(o) A method shall be provided that permits users to skip repetitive navigation links. Supports with exceptions

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

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not applicable

Timed responses are not required.

Section 1194.23 Telecommunications Products

Criteria Level of Support Remarks and explanations
(a) Telecommunications products or systems which provide a function allowing voice communication and which do not themselves provide a TTY functionality shall provide a standard non-acoustic connection point for TTYs. Microphones shall be capable of being turned on and off to allow the user to intermix speech with TTY use. Not applicable
(b) Telecommunications products which include voice communication functionality shall support all commonly used cross-manufacturer non-proprietary standard TTY signal protocols. Not applicable
(c) Voice mail, auto-attendant, and interactive voice response telecommunications systems shall be usable by TTY users with their TTYs. Not applicable
(d) Voice mail, messaging, auto-attendant, and interactive voice response telecommunications systems that require a response from a user within a time interval, shall give an alert when the time interval is about to run out, and shall provide sufficient time for the user to indicate more time is required. Not applicable
(e) Where provided, caller identification and similar telecommunications functions shall also be available for users of TTYs, and for users who cannot see displays. Not applicable
(f) For transmitted voice signals, telecommunications products shall provide a gain adjustable up to a minimum of 20 dB. For incremental volume control, at least one intermediate step of 12 dB of gain shall be provided. Not applicable
(g) If the telecommunications product allows a user to adjust the receive volume, a function shall be provided to automatically reset the volume to the default level after every use. Not applicable
(h) Where a telecommunications product delivers output by an audio transducer which is normally held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided. Not applicable
(i) Interference to hearing technologies (including hearing aids, cochlear implants, and assistive listening devices) shall be reduced to the lowest possible level that allows a user of hearing technologies to utilize the telecommunications product. Not applicable
(j) Products that transmit or conduct information or communication, shall pass through cross-manufacturer, non-proprietary, industry-standard codes, translation protocols, formats or other information necessary to provide the information or communication in a usable format. Technologies which use encoding, signal compression, format transformation, or similar techniques shall not remove information needed for access or shall restore it upon delivery. Not applicable
(k)(1) Products which have mechanically operated controls or keys shall comply with the following: Controls and Keys shall be tactilely discernible without activating the controls or keys. Not applicable
(k)(2) Products which have mechanically operated controls or keys shall comply with the following: Controls and Keys shall be operable with one hand and shall not require tight grasping, pinching, twisting of the wrist. The force required to activate controls and keys shall be 5 lbs. (22.2N) maximum. Not applicable
(k)(3) Products which have mechanically operated controls or keys shall comply with the following: If key repeat is supported, the delay before repeat shall be adjustable to at least 2 seconds. Key repeat rate shall be adjustable to 2 seconds per character. Not applicable
(k)(4) Products which have mechanically operated controls or keys shall comply with the following: The status of all locking or toggle controls or keys shall be visually discernible, and discernible either through touch or sound. Not applicable

Section 1194.24 Video and Multi-media Products

Criteria Level of Support Remarks and explanations
(a) All analog television displays 13 inches and larger, and computer equipment that includes analog television receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals. As soon as practicable, but not later than July 1, 2002, widescreen digital television (DTV) displays measuring at least 7.8 inches vertically, DTV sets with conventional displays measuring at least 13 inches vertically, and stand-alone DTV tuners, whether or not they are marketed with display screens, and computer equipment that includes DTV receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals. Not applicable
(b) Television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry. Not applicable
(c) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain speech or other audio information necessary for the comprehension of the content, shall be open or closed captioned. Supports

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

(d) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain visual information necessary for the comprehension of the content, shall be audio described. Supports with exceptions

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

(e) Display or presentation of alternate text presentation or audio descriptions shall be user-selectable unless permanent. Supports

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

Section 1194.25 Self-Contained, Closed Products

Criteria Level of Support Remarks and explanations
(a) Self contained products shall be usable by people with disabilities without requiring an end-user to attach Assistive Technology to the product. Personal headsets for private listening are not Assistive Technology. Not applicable
(b) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not applicable
(c) Where a product utilizes touch screens or contact-sensitive controls, an input method shall be provided that complies with 1194.23 (k) (1) through (4). Not applicable
(d) When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided. Not applicable
(e) When products provide auditory output, the audio signal shall be provided at a standard signal level through an industry standard connector that will allow for private listening. The product must provide the ability to interrupt, pause, and restart the audio at anytime. Not applicable
(f) When products deliver voice output in a public area, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. Where the ambient noise level of the environment is above 45 dB, a volume gain of at least 20 dB above the ambient level shall be user selectable. A function shall be provided to automatically reset the volume to the default level after every use. Not applicable
(g) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Not applicable
(h) When a product permits a user to adjust color and contrast settings, a range of color selections capable of producing a variety of contrast levels shall be provided. Not applicable
(i) Products shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Not applicable
(j)(1) Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following: The position of any operable control shall be determined with respect to a vertical plane, which is 48 inches in length, centered on the operable control, and at the maximum protrusion of the product within the 48 inch length on products which are freestanding, non-portable, and intended to be used in one location and which have operable controls. Not applicable
(j)(2) Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following: Where any operable control is 10 inches or less behind the reference plane, the height shall be 54 inches maximum and 15 inches minimum above the floor. Not applicable
(j)(3) Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following: Where any operable control is more than 10 inches and not more than 24 inches behind the reference plane, the height shall be 46 inches maximum and 15 inches minimum above the floor. Not applicable
(j)(4) Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following: Operable controls shall not be more than 24 inches behind the reference plane. Not applicable

Section 1194.26 Desktop and Portable Computers

Criteria Level of Support Remarks and explanations
(a) All mechanically operated controls and keys shall comply with 1194.23 (k) (1) through (4). Not applicable
(b) If a product utilizes touchscreens or touch-operated controls, an input method shall be provided that complies with 1194.23 (k) (1) through (4). Not applicable
(c) When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided. Not applicable
(d) Where provided, at least one of each type of expansion slots, ports and connectors shall comply with publicly available industry standards Not applicable

Section 1194.31 Functional Performance criterion

Criteria Level of Support Remarks and explanations
(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided. Supports with exceptions

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.

(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided. Supports with exceptions

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.

(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided Supports

Products do not require auditory feedback.

(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. Not Applicable

Products do not use auditory feedback.

(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided. Supports

Products do not require speech input.

(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. Supports with exceptions

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.

Section 1194.41 Information, Documentation and Support

Criteria Level of Support Remarks and explanations
(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge Supports

Please contact [email protected] with any such requests.

(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge. Supports

Documentation available at government.github.com/accessibility

(c) Support services for products shall accommodate the communication needs of end-users with disabilities. Supports

Support provided via web and email