Accessibility Conformance Report for github.com

Report Date

This report was last updated on July 17, 2023.

Product Description

github.com is the world’s largest developer platform. It empowers developers to collaborate and build scalable, secure software.

Contact Information

Please share questions or comments on the accessibility community discussion page.

Scope

The scope of this report is limited to the following user scenarios:

Create a new account
Sign in
Review and modify accessibility settings
Read notifications
Join a repository
Review, update, and assign issues
Read and edit a file within a repo
Create a branch and commit a change
Create, review, and merge a pull request
Sign out

Evaluation Methods Used

Scenarios were tested using:

Keyboard-only interactions
JAWS and NVDA with Google Chrome
axe
Colour Contrast Analyzer
Platform features such as high contrast and zoom

Applicable Standards/Guidelines

This report reflects outstanding issues found by an audit based on the level A and AA criteria of the Web Content Accessibility Guidelines version 2.1 (WCAG 2.1 AA).

Terms

Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partially Supports: Some functionality of the product does not meet the criterion.
Does Not Support: The majority of product functionality does not meet the criterion.
Not Applicable: The criterion is not relevant to the product.
Not Evaluated: The product has not been evaluated against the criterion.

WCAG 2.1

Level A Success Criteria

Success Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content	Supports
1.2.1 Audio-only and Video-only (Prerecorded)	Supports
1.2.2 Captions (Prerecorded)	Supports
1.2.3 Audio Description or Media Alternative	Supports
1.3.1 Info and Relationships	Partially Supports	Exceptions include: [GitHub home page]: Upon activating the 'Skip to main content' link , the screen reader does not announce the content present on the main landmark. [Manage Access-Search by username, full name, or email] Screen reader is not announcing the search suggestion results that appear when a valid input is provided in the 'Search by username, full name, or email' edit field. [GitHub home page-Product] Links that appear under the 'Explore' section are not defined under a group. [Manage Access-Role] Items that appear under 'Filter by role' section under 'Role' dropdown are not defined under a group. [GitHub home page] The screen reader announces incorrect number of list items in the dropdown under ‘Product’ control. [Issue Tab-Right section controls]: The Screen reader is announcing incorrect position of the items present under 'Assignees' on the right pane of the page. [Manage Access-Add People] On the add people dialog box, radio buttons are controls are not defined under a group. [Sort]: Items that appear under 'Most reactions' section under 'Sort' dropdown are not defined under a group. [Assignee]: Screen reader does not announce the search suggestion results that appear when a valid input is provided in the 'Filter users' edit field. [Manage Access-Find a collaborator] Screen reader is not announcing the search suggestion results that appear when a valid/invalid input is provided in the 'Find a collaborator' edit field. [Manage Access-Type] On the 'Manage access' page, menu item radio controls are not defined under a group. [Audio challenge] Screen reader is not announcing the frame text information.
1.3.2 Meaningful Sequence	Supports
1.3.3 Sensory Characteristics	Supports
1.4.1 Use of Color	Partially Supports	Exceptions include: [Code Tab-Code button] Links must be distinguishable without relying on color.
1.4.2 Audio Control	Supports
2.1.1 Keyboard	Partially Supports	Exceptions include: [Issue]: The alternative text which appears on mouse hover on ‘Update readme’ control is not accessible through keyboard. [GitHub home page] The search suggestion results are not accessible through keyboard upon providing a valid input in the edit field. [Open a pull request] On the 'Open a pull request' page, 'Diff using three-dot notation' control is not accessible through keyboard. [Open a pull request] Tooltip (awaiting requested review from username) information which appears on mouse hover is not accessible through keyboard. [GitHub home page] The ‘Mona looking at the galaxy’ control is not accessible through keyboard. [Assignee]: ‘Copy’ control present alongside 'Hello word' file under 'Code' tab is neither accessible nor visible through keyboard navigation. [GitHub home page]: Code contents having a horizontal bar are not accessible through keyboard.
2.1.2 No Keyboard Trap	Supports
2.1.4 Character Key Shortcuts	Supports
2.2.1 Timing Adjustable	Supports
2.2.2 Pause Stop Hide	Supports
2.3.1 Three Flashes or Below Threshold	Supports
2.4.1 Bypass Blocks	Supports
2.4.2 Page Titled	Supports
2.4.3 Focus Order	Partially Supports	Exceptions include: [Issue-Add or remove reaction] On the comment section controls, the focus order is not logical. [Display the source diff/rich diff/more button]: The focus order is not logical for the ‘1 changed file’ control. [Display the source diff/rich diff/more button]: The keyboard focus disappears upon activating the ‘Display the Rich diff’ button. [Display the source diff/rich diff/more button]: The Keyboard focus moves to the next control- ‘Copy the full SHA’ button without the ‘Verified’ dropdown automatically collapsing. [Display the source diff/rich diff/more button]: ‘Copy the full SHA’ control requires two-tab strokes to navigate. [Authors-filter by authors] The menu that appears upon activation the ‘Authors’ control is not closing automatically when keyboard focus moves to the next control. [File changed] On checking the viewed checkbox, the keyboard focus does not remain on it. [Review required] On the review required section, the keyboard focus moves inside the collapse elements of 'show all checks' control. [Review changes] The keyboard focus moves out of the expanded 'Finish your review' control to the background page elements. [Add or remove reaction] By selecting any emoji control, the visual focus indicator does not remain on the 'Add or remove reaction' control. [GitHub home page] The focus order is not logical for the 'Terms & Privacy' links at the footer section. [Issue Tab]: Keyboard focus moves out of the expanded items of '...' (Show options) dropdown to the background controls of the page without the dropdown automatically collapsing. [GitHub home page]: Keyboard focus moves out of the expanded items of 'Product' dropdown to the background controls of the page without the dropdown automatically collapsing.
2.4.4 Link Purpose (In Context)	Partially Supports	Exceptions include: [Review required/Merging is blocked sections] On the 'Adding welcome message to readme' page, link 'learn more' is not descriptive enough. [Code tab]: 'Yesterday' link present under 'Code' tab is not descriptive enough, as read by screen reader.
2.5.1 Pointer Gestures	Supports
2.5.2 Pointer Cancellation	Supports
2.5.3 Label in Name	Supports
2.5.4 Motion Actuation	Supports
3.1.1 Language of Page	Supports
3.2.1 On Focus	Supports
3.2.2 On Input	Supports
3.3.1 Error Identification	Partially Supports	Exceptions include: [Issue Tab-Right section controls]: Screen reader does not automatically announce the error message information after providing an invalid input in the 'Find a user' edit field.
3.3.2 Labels or Instructions	Supports
4.1.1 Parsing	Supports
4.1.2 Name Role Value	Partially Supports	Exceptions include: [Display the source diff/rich diff/more button]: The screen reader does not announce ‘Role’ for the view file control which is present under ellipses 'show options' button. [Open a pull request] Role is not defined for 'awaiting requested review from username' control. [Issue Tab-Right section controls]: Screen reader is not announcing the role of 'Clear assignees' control present under 'Assignees'. [Issue Tab]: Screen reader is not announcing the role of the items present under '...' (Show options) button under 'Issues' tab. [Code] On the code section, `aria-label` is not defined for the three-dot ellipsis button. [Audio challenge] Title attribute is not defined for the frame.

Level AA Success Criteria

Success Criteria	Conformance Level	Remarks and Explanations
1.2.4 Captions (Live)	Supports
1.2.5 Audio Description (Prerecorded)	Supports
1.3.4 Orientation	Supports
1.3.5 Identify Input Purpose	Supports
1.4.3 Contrast (Minimum)	Partially Supports	Exceptions include: [GitHub home page] The luminosity contrast ratio of the text 'the total economic impact' is less than 4.5:1. [GitHub home page-script.js] The luminosity contrast ratio of the text 'script.js' is less than 4.5:1. [Audio challenge] The luminosity contrast ratio for text "Incorrect. Only enter the number of your chosen answer, e.g. 1" is less than 4.5:1.
1.4.4 Resize text	Partially Supports	Exceptions include: [GitHub home page] On zooming the 'GitHub home' page up to 200%, the code elements under ‘index.html’ tab get truncated. [Display the source diff/rich diff/more button]: Upon resizing the page to 200%, 'Verified' control disappears. [Assignee]: Upon resizing the page to 200%, 'Projects' and 'Milestones' dropdown disappears.
1.4.5 Images of Text	Supports
1.4.10 Reflow	Partially Supports	Exceptions include: [Issue]: Upon setting the viewport to 320254 pixels, the ‘Menu items’ under the ‘Label’ dropdown button are truncating. [Start puzzle-navigation] The images get truncated when the viewport changes to 320256 pixels. [Assignee]: The dropdown indicator for 'Assignee' disappears after setting the viewport to 320*256 pixels.
1.4.11 Non-text Contrast	Partially Supports	Exceptions include: [new user]: The luminosity ratio of focus boundary for ‘Open issue and pull requests’ control that is under ‘Filter dropdown is less than the required contrast ratio i.e., 3:1. [Assignee] The luminosity ratio of focus boundary for ‘Assigned to nobody’ control that is under ‘Assignee’ dropdown is less than the required contrast ratio i.e., 3:1. [Display the source diff/rich diff/more button] The luminosity contrast ratio for borderline over ‘Copy the full SHH’ button is less than 3:1. [Issue-accessibility testing of the product #1] The luminosity contrast ratio of borderline over the Subscribe button is less than 3:1. [Issue-accessibility testing of the product #1] The luminosity contrast ratio for borderline over the 'Edit' button is less than 3:1. [Projects/milestone] The luminosity contrast ratio for borderline over the ‘filter milestones’ control is less than 3:1. [labels-filter by labels] The luminosity contrast ratio for the borderline over ‘Filter labels’ edit field is less than 3:1 [Authors-Filter by Authors] The luminosity contrast ratio for borderline over ‘Filter users’ control is less than 3:1. [Manage access] The banner has insufficient contrast (less than 3:1) against the page background
1.4.12 Text-spacing	Partially Supports	Exceptions include: [Issue]: Upon applying text spacing, the information below the menu items under ‘Label’ dropdown button is truncating.
1.4.13 Content on Hover or Focus	Supports
2.4.5 Multiple Ways	Supports
2.4.6 Headings and Labels	Partially Supports	Exceptions include: [GitHub home page]: Order of headings is semantically incorrect for 'GitHub' home page.
2.4.7 Focus Visible	Partially Supports	Exceptions include: [Review changes] The keyboard focus is not visible on the 'Attach file' control. [GitHub home page]: Focus indicator is not visible on the social media controls when navigated upon through keyboard.
3.1.2 Language of Parts	Supports
3.2.3 Consistent Navigation	Supports
3.2.4 Consistent Identification	Supports
3.3.3 Error Suggestion	Supports
3.3.4 Error Prevention (LFD)	Supports
4.1.3 Status Messages	Partially Supports	Exceptions include: [Issue]: The screen reader does not announce the status message when any valid input is provided in the ‘search field’ [Propose changes]: The screen reader does not announce the status message information after activating ‘Propose changes’ button.

Back to conformance reports