Accessibility Conformance Report for GitHub.com

(Based on VPAT® Version 2.4)

Report Date

This report was last updated on July 16, 2024.

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 on the GitHub.com website:

  • Sign up
  • 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
  • Account Management
  • Organizations
  • Discussions
  • Email Preferences Center
  • GitHub Sponsors
  • Captcha
  • 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:

  • [GlobalNav5.5] [Global Navigation-User Drawer] Screen reader does not announce the count and position for all list items
  • [GlobalNav5.5] [Global Navigation-User Drawer] List items in profile pane are not correctly structured
  • [GlobalNav5.6] [Global Navigation-User Drawer] < li > elements are not used semantically for 'Create new' controls
  • [Cntribtr&CodeFrqnc1.3] [Repo insights views-Commit Over time - Chart UI] Landmarks are not unique on 'Contributors' page
  • [AcctLogin1.4] [GitHub Account Login -Sign out] Screen reader does not announce complete information of page
  • [AcctLogin1.26] [GitHub Account Login -Sign out] 'Sign out' control is not descriptive enough
  • [AcctLogin1.23] [GitHub Account login- Sign in using recovery code] Heading structure inside the dialog is not in hierarchy level
  • [AcctLogin1.12] [GitHub Account Login -Enable two-factor authentication (2FA)] Visually appearing heading text is not programmatically defined as heading
  • [AcctLogin1.14] [GitHub Account Login -Security key] Screen reader is announcing as table, when focus lands on edit field
  • [AcctLogin1.12] [GitHub Account Login -Enable two-factor authentication (2FA)] Screen Reader does not announce the associated information for edit field
  • [AcctLogin1.17] [GitHub Account Login -Recovery code] Level one heading is not defined in the page
  • [AcctLogin1.5] [GitHub Account Login -Two-factor authentication] Order of headings is not in logical sequence
  • [GithubDisc1.28] [GitHub Discussion-Pin discussion] The heading structure inside the 'Configure pinned discussion' dialog box is not in hierarchy level.
  • [GHRecommendedPlan1.1] [GitHub Recommended Plan-Landing page] Upon activating the 'Skip to main content' link , the screen reader does not announce the content present on the main landmark.
  • [GHSponsers1.31] [GHSponsers - GitHub Sponsors Profile] Screen reader does not announce complete information on the edit field of Introduction.
  • [GHSponsers1.30] [GitHub Sponsors-Sponsors dashboard] Screen reader does not announce the headings in hierarchical order while navigating on them.
  • [GHSponsers1.55] [GitHub Sponsors-GitHub sponsor accounts] Screen reader is announcing the additional information of the hovercard without getting displayed.
  • [GHSponsers1.16] [anjuan / Sponsoring-Join the waitlist] The screen reader does not announce the associated label for the radio buttons.
  • [GHSponsers1.10] [GitHub Sponsors-Explore GitHub Sponsors] The screen reader announces irrelevant information along with the left pane list items.
  • [GHSponsers1.10] [GitHub Sponsors-Explore GitHub Sponsors] The screen reader announces the entire information at the once when focus lands on left pane list items.
  • [GHSponsers1.10] [GitHub Sponsors-Explore GitHub Sponsors] The page contains more than one main landmark.
  • [Accountmgmt3.1] [Account Management-Spending limit] The screen reader does not announce the associated label for the radio buttons which are present under 'Monthly spending limits' section.
  • [Accountmgmt2.1] [Account Management-Usage] The screen reader does not announce the column 2-Included as column header.
  • [Accountmgmt7.3] [Account Management-Payment Information] The screen reader does not announce the dialog box information which appear on invoking 'Remove billing information' control.
  • [Accountmgmt4.2] [Account Management-Billing emails] The screen reader does not announce the dialog box information which appear on invoking 'Remove' control.
  • [Accountmgmt2.1] [Account Management-Usage] Empty column header is defined for the table-'Usage minutes' under 'Actions monthly usage' section.
  • [GlobalNav3.1] [Global Navigation-Context Navigation] The screen reader does not announce the current page information when it lands on the breadcrumb navigation link -'Pages-Accessibility'.
  • [GitHubSignUp2.4] [GitHubSignUp - Welcome to Github - Recommended plan] Screen reader does not announce position count information for list items defined in the page.
  • [GithubDisc1.26] [GitHub Discussions-Transfer this discussion] The screen reader does not announce the search suggestion results when a valid/invalid input is provided in the 'Search repositories' edit field control.
  • WCAG Audit] [GithubDisc1.44] [GitHub Discussions-discussions overview] The screen reader is not announcing the information when the invalid/valid input is provided to the search field.
  • [GithubDisc1.45] [GitHub Discussions-Settings] The ARIA role does not contain particular children inside the"githuba11y/repo_the_second2" menu button.
  • [GithubDisc1.42] [GitHub Discussions-Changing the category] The Aria parent role is not defined for the 'Label' dropdown elements.
  • [GithubDisc1.14] [GitHub Discussions-Comment Options -Discussions options - Reference in new issue] The screen reader does not announce associated label information for the edit field under ‘Repository’ dropdown.
  • [GithubDisc1.19] [GitHub Discussions-Comment Options -Reference in new issue] The screen reader announces incorrect position number in the dialog box under 'Reference in new issue' menu item.
  • [GithubDisc1.19] [GitHub Discussions- Comment Options - Reference in new issue] The screen reader does not announce the search suggestion results when a valid/invalid input is provided in the 'Find a repository' edit field under Repository dropdown control.
  • Discussions feedback: Improve segmented control
  • [GithubDisc1.9] [GitHub Discussions-Label] The aria children role is not defined for the menu items inside the 'Label' dropdown.
  • [GithubDisc1.5] [GitHub Discussions-Edit category] The screen reader announces incorrect position for the checked item under ‘Category’ dropdown.
  • [GitHub home page]: Upon activating the 'Skip to main content' link , the screen reader does not announce the content present on the main landmark.
  • [GitHub home page-Product] Links that appear under the 'Explore' section 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-Type] On the 'Manage access' page, menu item radio controls are not defined under a group.
  • [BI_Form1.9] [Billing Form – Payment Method- Error message] Screen reader is not announcing the error messages of all fields that have invalid input.
1.3.2 Meaningful Sequence

Partially Supports

Exceptions include:

  • [Cntribtr&CodeFrqnc1.3 [Repo insights views-Commit Over time - Chart UI] Screen reader does not announce 'Graph node' point information
  • [AcctLogin1.25] [GitHub Account Login -Add other account] In browse mode, screen reader navigation does not move to controls
1.3.3 Sensory Characteristics

Partially Supports

Exceptions include:

  • [GithubDisc1.34] [GitHub Discussions- Manage categories] An additional information is not defined for the 'Pencil shaped icon' i.e., present at the left side of the 'GitHub discussions homepage'.
1.4.1 Use of Color

Supports

1.4.2 Audio Control

Supports

2.1.1 Keyboard

Partially Supports

Exceptions include:

  • [GlobalNav5.6] [Global Navigation-User Drawer] '+ Create new' control is not accessible by keyboard
  • [GlobalNav3.3] [Global Navigation-Context Navigation] On resizing the page up to 200%, 'Create new' control is not accessible by keyboard
  • [GlobalNav2.4] [Global Navigation-Feature Preview] Feature Preview control is not accessible by keyboard
  • [GlobalNav2.2] [Global Navigation-User Drawer] Set status control is not accessible by keyboard
  • [Cntribtr&CodeFrqnc1.4] [Repo insights views-User Commits] Controls inside 'cheshire137' profile icon are not accessible via keyboard
  • [GHSponsers1.10] [Usable-GitHub Sponsors-Explore GitHub Sponsors] The list items at the left pane are not navigable through directional keys.
  • [Issue]: The alternative text which appears on mouse hover on ‘Update readme’ control is not accessible through keyboard.
  • [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.
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:

  • [GlobalNav1.1] [Global Navigation-Hamburger menu] Keyboard focus order is not logical on the 'Global navigation' dialog box
  • [GlobalNav5.2] [Global Navigation-Test134d/Page accessibility] Keyboard focus order is not logical on the 'Navigate back to' dialog box
  • [AcctLogin1.9] [GitHub Account login-Add a Passkey-Delete passkey] Keyboard focus order is not logical on the 'Delete passkeys' dialog box
  • [SSHAuthn1.3] [SSH Authentication-Are you sure you want to delete this SSH key?] The keyboard focus order is not logical on the -'Are you sure you want to delete this SSH key?' dialog box.
  • [SSHAuthn1.8] [SSH Authentication-Are you sure you want to delete this GPG key?] The keyboard focus moves to the background control without the -'Are you sure you want to delete this GPG key?' dialog collapsing.
  • [GithubDisc1.26] [GitHub Discussion- Transfer this discussion] Keyboard focus moves to whole 'Transfer this discussion' dialog.
  • [GHSponsers1.23] [GitHub Sponsors-Bulk Sponsor] The keyboard focus in the 'Create sponsorships in bulk via file import' page is not moving in logical sequential order.
  • [GHSponsers1.68] [GitHub Sponsors-Sponsors dashboard] The keyboard focus moves to the background control without the 'Embed a link to 'Shivam2250 graphic ' menu automatically collapsing.
  • [GHSponsers1.31] [GHSponsers - GitHub Sponsors Profile] Keyboard focus navigates on the non-interactive multi-line text box after 'Write' tab.
  • [GHSponsers1.51] [GitHub Sponsors-GitHub sponsor accounts] The keyboard focus moves to the next interactive controls without collapsing the expanded menu.
  • [Accountmgmt7.1] [Account Management-Payment Information] Upon saving the blank form, the keyboard focus order is not logical.
  • [GlobalNav4.1] [Global Navigation-Local Navigation] Upon activating the 'Issues' tab control, keyboard focus is not logical in the local navigation region.
  • [GlobalNav1.2] [Global Navigation-Global Side Panel] Entire hamburger menu is getting collapsed, upon trying to close tooltip -'Close filter' using esc key.
  • [GlobalNav2.2] [Global Navigation-User Drawer] The keyboard focus moves to the next interactive control without the -'Clear status' dropdown automatically collapsing.
  • [GithubDisc1.40] [GitHub Discussion-Categories-Polls] Upon activating the "Add an option" control, the keyboard focus does not move to the newly added editable "Option" control.
  • [GithubDisc1.39] [GitHub Discussions- Q and A (Animals')] The keyboard focus disappears upon activating the 'Mark your answer' control.
  • [GithubDisc1.37] [GitHub Discussion- new category] Keyboard Focus moves to the 'categories' edit field upon activating the 'emoji picker' instead of focus moving to the emoji section.
  • [GithubDisc1.37] [GitHub Discussion- new category] Keyboard Focus moves to the background control from the last menu item of 'Emoji Picker' menu without the menu automatically collapsing.
  • [GithubDisc1.13] [GitHub Discussions-Discussions options -Quote reply] The focus order is not logical when the focus moves to the ‘Discussion options’ control from ‘Edit’ control.
  • [GithubDisc1.19] [GitHub Discussions-Comment Options - Reference in new issue] The keyboard focus moves to the background control from the last menu item without the 'Repository' dropdown automatically collapsing.
  • [GithubDisc1.6] [GitHub Discussion- Select a discussion category] Keyboard Focus moves to the background control from the last menu item of 'add or remove reaction' menu without the menu automatically collapsing.
  • [GithubDisc1.5][GitHub Discussions-Edit category] The Keyboard focus moves to the background controls of the page from the last item of ‘Category’ dropdown without the dropdown automatically collapsing.
  • [GithubDisc1.4] [GitHub Discussion- Select a discussion category] Keyboard Focus moves to the background control from the last menu item of 'Label' dropdown without the dropdown automatically collapsing.
  • [GithubDisc1.2] [GitHub Discussion- Blank Discussions page] Keyboard Focus moves to the background control of the page from the last element of ‘Sort by’ dropdown without the dropdown automatically collapsing.
  • [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 source diff’ control.
  • [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.
  • [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)

Supports

2.5.1 Pointer Gestures

Supports

2.5.2 Pointer Cancellation

Supports

2.5.3 Label in Name

Partially Supports

Exceptions include:

  • [Cntribtr&CodeFrqnc1.1] [Repo insights views-Contributors Header] Visual name and aria-label are different for date picker 'All' control
  • [AcctLogin1.14] [GitHub Account Login -Security key] Visual name and aria-label are different for 'Hide' control
  • [Accountmgmt7.4] [Account Management-Payment Information] Visual name and aria-label are different for the combo boxes for 'Expiration date' control.
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

Partially Supports

Exceptions include:

  • [Cntribtr&CodeFrqnc1.1] [Repo insights views-Contributors Header] No label defined for 'Start date and End date' edit field
4.1.1 Parsing

Partially Supports

Exceptions include:

  • [Accountmgmt7.1] [Account Management-Payment Information] Id attribute is not unique for the form fields which is present under 'Billing information' section.
  • [OrgsSer1.2] [Orgs Service-Set up your organization] Id attribute is not unique for the 'Verify your account' frame.
4.1.2 Name Role Value

Partially Supports

Exceptions include:

  • [GlobalNav5.3] [Global Navigation-Context Navigation] Interactive controls are nested together
  • [OrgsSer1.2] [Orgs Service-Set up your organization] Invalid ARIA attribute is used for element role
  • [AcctLogin1.3] [GitHub Account Login -Reset your password] Invalid ARIA attribute is used for element role
  • [AcctLogin1.13] [GitHub Account login- Two-factor authentication] Accessible name is not defined for the 'three dot' control
  • [AcctLogin1.16] [GitHub Account Login -GitHub Mobile] Invalid ARIA attribute is used for an element's role
  • [Accountmgmt5.1] [Account Management-Landing page] Proper role is not defined for the 'Get usage report' button.
  • [Accountmgmt4.2] [Account Management-Billing emails] The 'Edit' control do not have unique and descriptive label.
  • [GithubDisc1.2] [GitHub Discussions-Blank Discussions page] The aria-current attribute is not present for the 'Discussion' link.
  • [GithubDisc1.45] [GitHub Discussions-Settings] Expanded control "githuba11y/repo_the_second2" does not have required ARIA attributes defined for the radio menu elements.
  • [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.

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:

  • [GHSponsers1.61] [GitHub Sponsors-GitHub sponsor accounts] The luminosity contrast of the text 'Current balance' is 4.27:1 which is less than the required contrast ratio 4.5:1.
  • [GlobalNav3.2] [Global Navigation-Context Navigation] The luminosity contrast ratio of the ' Type / to search' placeholder text is 4.27:1, which is less than the required contrast ratio 4.5:1.
  • [GlobalNav2.2] [Global Navigation-User Drawer] The luminosity contrast ratio of the 'What's happening?' placeholder text is 4.3:1, which is less than the required contrast ratio 4.5:1.
  • [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.
1.4.4 Resize text

Partially Supports

Exceptions include:

  • [GithubDisc1.37] [GitHub Discussions- new category] The menu that appears upon activating 'Emoji picker' control is truncating upon resizing the page to 200%.
  • [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:

  • [OrgsSer1.2] [Orgs Service-Set up your organization] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 pixels
  • [Cntribtr&CodeFrqnc1.4] [Repo insights views-User Commits] On 320*256 pixel viewport, hovercard does not appear for profile icon upon receiving keyboard focus
  • [Cntribtr&CodeFrqnc1.3] [Repo insights views-Commit Over time - Chart UI] 'Graph' is overlapping, in 320*256 pixel viewport.
  • WCAG Audit] [AcctLogin1.4] [GitHub Account Login -Two-factor authentication] 'Cancel' control is truncated, in 320*256 pixel viewport.
  • WCAG Audit] [AcctLogin1.3] [GitHub Account Login -Forgot password] 'Navigate to next image' control is getting cutoff, in 320*256 pixel viewport
  • WCAG Audit] [AcctLogin1.3] [GitHub Account Login -Forgot password] Text is getting cutoff, upon setting the viewport to 320*256 pixel
  • [AcctLogin1.14] [GitHub Account Login -Security keys] Place holder text is getting cutoff, upon setting the viewport to 320*256 px
  • [AcctLogin1.17] [GitHub Account Login -Recovery Code] Two-dimensional scrolling is required to read the contents, upon setting the viewport to 320*256 px
  • [GithubDisc1.9][GitHub Discussions- Edit category] The menu item of the 'label' dropdown is not visible upon changing the viewport to 320*256 pixels.
  • [GHSponsers1.22] [GitHub Sponsors-GitHub sponsor accounts] A horizontal scroll bar appears on the page upon setting the viewport to 320*256 pixels.
  • [GHSponsers1.56] [GitHub Sponsors-GitHub sponsor accounts] A horizontal scroll bar appears on the page upon setting the viewport to 320*256 pixels.
  • [GHSponsers1.50] [GitHub Sponsors-GitHub sponsor accounts] A horizontal scroll bar appears on the page upon setting the viewport to 320*256 pixels.
  • [GHSponsers1.13] [Explore GitHub Sponsors-Explore GitHub Sponsors] Tooltip does not appear for graphical link on receiving focus upon setting the viewport to 320*256 pixels.
  • [GHSponsers1.6] [Explore GitHub Sponsors-Explore GitHub Sponsors] Horizontal scroll bar appears on the page upon setting the viewport to 320*256 pixels.
  • [Accountmgmt4.1] [Account Management-Billing emails] A Horizontal scroll bar appears on the page upon setting the viewport to 320*256pixels.
  • [Accountmgmt7.4] [Account Management-Payment Information] Upon setting the viewport to 320*256 pixels, 'Save payment information' control gets overlapped with the 'Privacy' and 'Terms' control.
  • [Accountmgmt7.4] [Account Management-Payment Information] Upon setting the viewport to 320*256 pixels, the tooltip which appear on 'Card' icon control gets truncated.
  • [AccntloginPasskey1.2] [Passkeys-Login with Passkey for Security page] Horizontal scrollbar appears on the page after setting the viewport to 320*256 pixels.
  • [AcctLogin1.16] [Account Login-SMS authentication] On setting to viewport to 320*256 pixels, the 'Please solve this puzzle so we know you are a real person' text gets truncated.
  • [AcctLogin1.1] [Account login- Login page] The horizontal scroll bar appears when the viewport changes to 320*256 pixels.
  • [OrgsSer1.20] [Orgs Service-Members] Tooltip of 'GitHub member handles' links does not appear on mouse hover upon setting the viewport to 320*256 pixels.
  • [Issue] On setting to viewport to 320*256 pixels, the sub menu controls present inside the ‘Label’ dropdown are getting cutoff.
  • [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:

  • [OrgsSer1.2] [Orgs Service-Set up your organization] Luminosity ratio of borderline for the edit field is 1.5:1
  • [AcctLogin1.10] [GitHub Account Login -Change password] Luminosity ratio of borderline for the edit field is 1.4:1
  • [SSHAuthn1.1] [SSH Authentication-Title] The luminosity ratio for borderline for the edit field is 1.2:1, which is less than the required contrast ratio 3:1.
  • [GlobalNav2.2] [Global Navigation-User Drawer] The luminosity contrast ratio for the focus indicator over the 'Everyone Your status will be visible to everyone' control is 1:1 which is less than the required contrast ratio 3:1.
  • [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.
  • [Projects/milestone] The luminosity contrast ratio for borderline over the ‘filter milestones’ control is less than 3:1.
  • [Authors-Filter by Authors] The luminosity contrast ratio for borderline over ‘Filter users’ control is less than 3:1.
1.4.12 Text-spacing

Partially Supports

Exceptions include:

  • [GlobalNav1.2] [Global Navigation-Global Side Panel] Upon applying text spacing, 'githuba11y/repo_the_second2' text is getting truncated.
  • [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

Supports

2.4.7 Focus Visible

Partially Supports

Exceptions include:

  • [Review changes] The keyboard focus is not visible on the 'Attach file' control.
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:

  • [Cntribtr&CodeFrqnc1.1] [Repo insights views-Contributors Header] Screen reader is not announcing displayed message information when user enter date manually
  • [AcctLogin1.11] [GitHub Account Login -Change password] On providing invalid input screen reader does not announce the status message information
  • [AcctLogin1.6] [GitHub Account Login -Two-factor authentication] Screen reader is not announcing the appeared status message
  • [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.
  • [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.
  • [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.

Disclaimer

©2024 GitHub Inc. All rights reserved. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. The information contained in this document represents the current view of GitHub Inc. on the issues discussed as of the date of publication. GitHub cannot guarantee the accuracy of any information presented after the date of publication.

GitHub’s WCAG 2.1 conformance reports provide the information included in ITI’s “VPAT® 2.4Rev WCAG (March 2022)” template. “Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information Technology Industry Council (ITI). This document includes material copied from or derived from the Web Content Accessibility Guidelines (WCAG 2.1). Copyright © 2017-2018 W3C® (MIT, ERCIM, Keio, Beihang). This document is not the Web Content Accessibility Guidelines (WCAG) and should not be used as a substitute for it. Excerpts of WCAG are referenced solely for purposes of detailing GitHub’s conformance with the relevant provisions. A full and complete copy of the Guidelines is available from the W3C WAI.

GitHub regularly updates its websites and provides new information about the accessibility of products as that information becomes available. Customization of the product voids this conformance statement from GitHub. Customers may make independent conformance statements if they have conducted due diligence to meet all relevant requirements for their customization. Please consult with Assistive Technology (AT) vendors for compatibility specifications of specific AT products. This document is for informational purposes only. GitHub MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.