Accessibility Conformance Report for GitHub.com

(Based on VPAT® Version 2.4)

Report Date

This report was last updated on May 27, 2025.

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:

User scenarios

  • Account management
  • Account management controllers
  • Actions
  • Advisory Database
  • App authorization
  • App authorization using SAML
  • App installation
  • Audit logs
  • Billing
  • Branch protection
  • Captcha
  • Code Review
  • Commit comment
  • Community and safety
  • Copilot for knowledge base
  • Copilot Settings
  • Create a branch and commit a change
  • Create, review, and merge a pull request
  • Customer Stories
  • Customer Terms
  • Dependabot
  • Dependency Graph
  • Deployments
  • Desktop
  • Discussions
  • Diversity Report
  • Email preferences center
  • Enterprise
  • Enterprise Startups
  • Enterprise Trial
  • Events
  • Features
  • Feeds
  • Homepage
  • HTML pipeline
  • Insights
  • Issues
  • Join a repository
  • Merge queue
  • Models
  • Mona-sans
  • Notebooks
  • OAuth app authorization
  • OAuth app authorization using SAML
  • Open Source
  • Organizations
  • Our Leadership
  • Premium Support
  • Press
  • Procurement
  • Read and edit a file within a repo
  • Read notifications
  • ReadME Project
  • Release
  • Review and modify accessibility settings
  • Review, update, and assign issues
  • Sign in
  • Sign out
  • Sign up
  • Solutions DevOps
  • Sponsors
  • Star
  • User profiles
  • Verifiable domains

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.2 (WCAG 2.2 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.2

Level A Success Criteria

Success Criteria Conformance Level Remarks and Explanations
1.1.1 Non-text Content

Partially Supports

Exceptions include:

  • [SecDashbrd1.21] ARIA progress bar nodes do not have an accessible name
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:

  • [GHIssueViewr1.19] Screen reader is not announcing the associative label information
  • [GHIssueViewr1.2] Screen reader is not announcing the associative information
  • [GHIssueViewr1.1] Screen Reader is not announcing displayed error message for edit field
  • [Issueexp1.7] Screen reader is not announcing the associative label information
  • [GHIssueTypes1.6]Screen reader is not announcing the associative information
  • [IssueDashSavdView1.4] Controls do not have required child role
  • [verifiableDomains2.11] Screen reader is not announcing the associative information
  • [IssueDashSavdView1.2] Screen reader is not announcing the associative label information
  • [VerifiableDomains1.5] Screen reader is not announcing the associative information
  • [verifiableDomains1.7] Screen reader is not announcing the associative information
  • [IssueDashSavdView1.2] Screen reader is not announcing the associative label information for edit field
  • [AcctLogin1.6] Screen reader does not announce current step information
  • [GHSecurity1.5] Sections and sub-sections of 'Two layers of powerful protection' section are defined under same heading level 2
  • [AcctLogin1.3] Unnecessarily heading is defined for text present under 'Verify your account' section
  • [ProfAuditReq1.7] Screen reader is not announcing the associative information
  • [ProfAuditReq1.22] Certain ARIA roles are not contained by particular parents
  • [GHEnterpriseLandingPgIOS1.3] VoiceOver announces heading on text '17000+'
  • [GHEnterpriseLandingPgAndroid1.5] '88%' is unnecessarily defined as a heading
  • [GHEnterpriseLandingPgAndroid1.4] Talkback is announcing unnecessary information for 'Scale, AI, Reliability and Security' Navigation Controls
  • [EnterpriseLandingpage(mac)1.2] Voice over is not announcing the list count information on list items
  • [GHQuickActionTasks1.2] Screen reader is not announcing the associative information
  • [EnterpriseLandingpage1.9] Sections and sub-sections of 'Frequently asked questions' section are defined under same heading level 3
  • [EnterpriseLandingpage1.5] '88%' is unnecessarily defined as a heading
  • [GHissueDshbd1.2] Screen reader does not announce the tooltip information
  • [ProfAuditReq1.7] Screen reader is not announcing the associative information
  • [ScalbleWbPltfm4.2] Screen reader is announcing incorrect position for the radio controls
  • [ScalbleWbPltfm12.1] Screen reader announces heading on text '150M+'
  • [ScalbleWbPltfm6.3] Screen reader is not announcing the associative information
  • [GH-PersonalInstructions_1.1] Screen reader does not announce the displayed error message
  • [SecDashbrd1.21] Text -'Most blocked secret types' is not programmatically defined as heading
  • [GHDependencyGrph1.7] List items under 'license' control do not have require child roles
  • [GHDependencyGrph1.4] List items under 'owner' control do not have require child roles
  • [GHDependencyGrph1.4] ARIA parent role is not defined for controls under 'owner' dropdown
  • [GHDependencyGrph1.7] Search landmark is incorrectly defined
  • [GHDependencyGrph1.5] Screen reader is not announcing the associative information
  • [SecDashbrd1.1] Screen Reader announces incomplete tooltip information
  • [GHDependencyGrph1.2] Status message is unnecessarily defined as a heading
  • [SecDashbrd1.1] Screen reader announces incorrect search suggestion information for the 'filter' edit field
  • [CopilotSettings1.27] Screen reader does not announce the displayed status message
  • [CopilotSettings1.30] List items under 'Select a policy' control do not have require child roles
  • [CopilotSettings1.25] Screen reader does not announce the displayed error message
  • [CopilotSettings1.4] Screen reader does not announce the associated information
  • [CopilotSettings1.9] List items are not correctly structured
  • [GithubDisc1.32] Page does not contain a level one heading
  • [GHSponsers1.19] '$561.11' is unnecessarily displayed as a heading
  • [GHSponsers1.19] Text -'Total Sponsors' is not programmatically defined as heading
  • [GithubDisc1.4] ARIA parent role is not defined for controls under 'labels' dropdown
  • [GHSponsers2.17] Text -' Recognition' is not programmatically defined as heading
  • [GithubDisc1.4] List items under 'Filter labels' control do not have require child roles
  • [GHSponsers2.17] Status message is unnecessarily defined as a heading
  • [GHSponsers1.2] Screen reader is announcing information from the other user into the current one
  • [GHSponsers2.17] Screen reader is not announcing the associated information for checkbox
  • [GHSponsers2.17] Screen reader is announcing incorrect count for list item inside the dropdown
  • [GHSponsers2.34] Screen reader does not announce the associated label information
  • [GHSponsers1.16] Screen reader is announcing incorrect information as 'Unavailable' after invoking 'Show more' control
  • [GHSponsers2.12] Screen reader is not announcing complete information for 'Monthly amount you're aiming for:' control
  • [DependbotAlerts4.3] Elements with an ARIA role that require child roles do not contain them
  • [DependbotAlerts4.3] Page does not contain a level one heading
  • [GH_Stars6.2] Page does not have level 1 heading
  • [User Feedback] Screen reader announces previous error message with latest error message
  • [GHActions_LargeRunner1.14] Screen Reader does not announce the associated 'disabled' information
  • [GHActions_LargeRunner1.7] Screen Reader does not announce the displayed error message for edit field
  • [GHActions_LargeRunner1.8] Aria parent role is not defined for the 'No configuration' control
  • [GHActions_LargeRunner1.8] List items under 'Select network configuration' dropdown menu do not have require child roles
  • [GHSponsers3.4] Screen reader does not announce the associated label for 'State/Province' control
  • [GHModels1.1] Screen reader is not announcing the search result information
  • [GHModels4.5] Screen reader is not announcing the updated information
  • [GHModels1.4] ARIA parent role is not defined for controls under 'By' dropdown
  • [GHModels1.4] List items under 'By' control do not have require child roles
  • [GHissuesmilestones1.5] <dl> element for the 'Title' Form group is not structured correctly
  • [GHIssueIndex1.5] List items under 'Filter' control does not have require child roles
  • [GHadvisorydatabse3.1] Screen reader does not announce the associated label information for 'Write' control
  • [GHIssueIndex1.5] Screen reader does not announce the group label information for list item
  • [GHIssueIndex1.5] List items under 'Filter by Project' control does not have require child roles
  • [Issueexp1.7] Screen Reader does not announce the displayed error message for edit field
  • [Issueexp1.2] Screen reader does not announce the associative label information for dropdown control
  • [Rleasepage1.3] <li> elements are not used semantically for controls under branches tab
  • [Rleasepage1.3] ARIA parent role is not defined for the controls under branches tab
  • [Rleasepage1.3] Elements with an ARIA role that require child roles does not contain them
  • [Issueexp1.7] Screen reader does not announce as required information for mandatory form elements
  • [Rleasepage1.1] Screen reader does not announce the additional information below the "Set as a pre-release" checkbox
  • [EmailPrefCenter1.2] [Email Preference Center-Subscription preferences] Screen reader does not announce the associated information for check box controls
  • [EcoSysAuth2.1] [GitHub Apps - GitHub App Authorization] Text -'Resources on your account' is not programmatically defined as heading
  • [EcoSysAuth3.3] [GitHub Apps - GitHub App Installation] Level one heading is not defined in the page
  • [Accountmgmt7.6] [Marketplace-Payment Information] Level one heading is not defined in the page
  • [Accountmgmt4.1] [Account Management-Billing emails] 'Add' control is not descriptive
  • [Accountmgmt7.4] [Account Management-Payment Information] Screen Reader does not announce the associated label information for 'PayPal' control
  • [Accountmgmt7.1] [Account Management-Payment Information] Screen Reader does not announce the associated label information for edit field
  • [Accountmgmt2.1] [Account Management-Usage]Screen reader is not announcing the count of elements present in billing navigation landmark
  • [OrgsSer1.2] Screen Reader is not announcing the group label for the checkbox
  • [GlobalNav5.5] [Global Navigation-User Drawer] Screen reader does not announce the count and position for all list items
  • [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.32] 'Sign out' control is not descriptive
  • [AcctLogin1.14] [GitHub Account Login -Security key] Screen reader is announcing as table, when focus lands on edit field
  • [AcctLogin1.6] Screen reader is not announcing the associative label information
  • [AcctLogin1.5] [GitHub Account Login -Two-factor authentication] Order of headings is not in logical sequence
  • [ProfAuditReq1.7] Screen Reader does not announce the associated label information for 'social accounts' edit field
  • [ProfAuditReq1.6] [Profile Audit-Change your avatar/ Public profile] Screen Reader does not announce the associated additional information for 'Name' edit field.
  • [GHDotCom-FeturCodeSp8.1] [GITHUBDOTCOM -Secure by design] Text ‘Isolated environments’ is unnecessarily exposed as heading of level 3.
  • [GHDotCom-FeturCodeSe7.2] [GITHUBDOTCOM-Way more than grep] Text ‘Suggestions, completions, and more’ is unnecessarily exposed as heading of level 2.
  • [GHDotCom-Readme31.3] [GITHUBDOTCOM - Readme] Text ‘Champion accessibility to unleash untapped potential’ is unnecessarily exposed as heading of level 3.
  • [GHDotCom-PreSprt18.2] [GitHub Dot Com Page-Premium Support] The content appears after invoking the 'compare all features' control is not defined in a tabular format.
  • [GHDotCom-PreSprt18.4] [GITHUBDOTCOM-Premium Support] Sections and sub-sections are defined under same heading level 3.
  • [GHDotCom-Entrprs17.7] [GITHUBDOTCOM - Enterprise] Heading structure is incorrect for ‘Start your journey with GitHub’ header and its underlying content.
  • [GHDotCom-Entrprs17.5] [GITHUBDOTCOM - Enterprise] Texts under ‘Efficiency and security at every step’ heading are unnecessarily defined in heading.
  • [GHDotCom-FeturC9.3] [GITHUBDOTCOM - Features Copilot] Texts under ‘The competitive advantage developers ask for by name.’ heading are unnecessarily exposed as heading
  • [GH_Hovercard1.8] [GitHub Hovercard- Dependabot Alert] Screen reader announces unnecessary extra information when the focus lands on 'Insecure temporary file usage in SWHKD' control.
1.3.2 Meaningful Sequence

Partially Supports

Exceptions include:

  • [AcctLogin1.22] In browse mode, screen reader navigation is not sequential after 'See More' control
  • [GHDependencyGrph1.7] In browse mode, screen reader navigation is not sequential after 'Sponsor' control
  • [GHIssueViewr1.5] In browse mode, the screen reader focus is not logical inside the 'andrefcdias' hovercard
  • [Rleasepage1.10] In browse mode screen reader navigation is not logical on activating the 'Toggle V.0.1's commit message' control
  • [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
  • [GH_Hovercard1.18] In browse mode, the screen reader focus is not logical after the '127.0.0.1' text inside the '@imjohnbo' hovercard
1.3.3 Sensory Characteristics

Partially Supports

Exceptions include:

  • [IssueDashSavdView1.2]: Tooltip is not defined for the icon buttons
  • [ActnUsgMetrcs1.2] No additional information is provided for the 'Filter' icon
  • [GH-PersonalInstructions_1.1] Tooltip is not defined for the 'Show templates' control
  • [SecDashbrd1.1] No additional information is provided for the 'Filter' icon
  • [Visual Requirment-GHSponsers2.28] No additional information is provided for the 'dot' (.) control
  • [ProfAuditReq1.2] [Profile Audit-Set status] Tooltip is not defined for the 'Set status' control
1.4.1 Use of Color

Partially Supports

Exceptions include:

  • [AcctLogin1.3] Color is the sole medium to identify the link 'Click here to get a new password reset link'
  • [AcctLogin1.22] Color is the sole medium for identifying Activity indicator
  • [GH_Adt-Secrtylog1.4] Link 'Learn more about filters' has insufficient color contrast 1.17:1 with the surrounding text
  • [ProfAuditReq1.37] Color is the sole medium to indicate level of contributions
  • [GH_Hovercard1.1] Link 'github/copilot-api#1571' has insufficient color contrast 1.17:1 with the surrounding text
  • [SocialImpactWeb5.3] Link 'The Hive' solely relies on color
  • [GHSponsers1.2] Link 'results as CSV' has insufficient color contrast 1.2:1 with the surrounding text
  • [PR_MergeQueue1.4] Link have insufficient color contrast 1.2:1 with the surrounding text
  • [Repo_Insights1.2] Color is the sole medium to indicate the progress bars
  • [UserDashboard1.5] Link 'Teamelite12/test' has insufficient color contrast 2.6:1 with the surrounding text
  • [User Feedback] Only (slight) color change is used to indicate PR approvals between active and deactivated users
  • [GH_CMSF2_ Tempt1.4] [GitHub CMS F2 template-Frequently Asked Questions] Link 'Lobortis mattis ' has insufficient color contrast with the surrounding text.
1.4.2 Audio Control

Supports
2.1.1 Keyboard

Partially Supports

Exceptions include:

  • [Keyboard Navigaion-GH_Adt-Secrtylog1.2] Value of 'user_agent' is not accessible via keyboard
  • [GHIssueViewr1.5] Tooltip is not accessible through keyboard
  • [AcctLogin1.14] Tooltip is not accessible through keyboard
  • [AcctLogin1.18] 'Edit' control is not accessible with keyboard
  • [ProfAuditReq1.2] Tooltip is not accessible through keyboard
  • [ActnUsgMetrcs1.13] Tooltip is not accessible through keyboard
  • [GHDependencyGrph1.5] Tooltip is not accessible through keyboard
  • [GHSponsers2.31] List items present within the 'Payouts' and 'Years' tab are not accessible via keyboard
  • [SocialImpactWeb1.2] 'Photo image of GitHub' control of the video is not keyboard accessible
  • [Repo_Insights1.11] Data pointers are not accessible via keyboard
  • [Repo_Insights1.9] Graph bars are not accessible via keyboard
  • [Repo_Insights1.3] Graph bars are not accessible via keyboard
  • [WCAG] [User Feedback] Adding an owner to a new organization has a poor UX because of dropdown suggestions
  • [SecCover1.9] Tooltip is not accessible with Keyboard
  • [OrgsSer1.22] Cancel invitations control is not keyboard accessible
  • [GHActnUsgMetrics1.2] [GithubAtionUsageMetrics - Workflows] Tooltip is not accessible through keyboard
  • [GHDotCom-Mona-sans29.2] [GitHub Dot Com Page-Mona-sans] The 'Video content' is not accessible by the keyboard.
  • [GH_Hovercard1.5] The tooltip for the ''jbarnette" control is not accessible through the 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

Partially Supports

Exceptions include:

  • [ScalbleWbPltfm1.1] No mechanism to pause/stop/hide the auto-scrolling content
2.3.1 Three Flashes or Below Threshold

Supports
2.4.1 Bypass Blocks

Supports
2.4.2 Page Titled

Partially Supports

Exceptions include:

  • [User Feedback] Milestone individual pages should contain milestone name in page title
2.4.3 Focus Order

Partially Supports

Exceptions include:

  • [GHIssueViewr1.2] Keyboard focus moves to hidden content in 'Listed #387' hovercard
  • [GHIssueViewr1.3] Keyboard focus order is not logical upon selecting the checkbox.
  • [GHIssueTypes1.2] Keyboard focus does not retain back to 'more options' control upon closing the dialog
  • [IssueDashSavdView1.8] Keyboard focus does not retain on 'Saved views menu' control upon closing the dialog by esc key
  • [AcctLogin1.8] keyboard focus is not logical, When the Continue control is activated
  • [AcctLogin1.6] Keyboard focus order is not logical upon activating 'Enable two-factor authentication'
  • [AcctLogin1.26] keyboard focus is not logical, When Use your Authenticator app control is activated
  • [ProfAuditReq1.38] Keyboard focus order is not logical upon activating '2024' control
  • [ProfAuditReq1.35] Keyboard Focus does not retain on 'Contribution settings' control
  • [GHEnterpriseLandingPgIOS1.3] Focus does not navigate in a logical manner on 'Learn more about the ROI of GitHub' link
  • [GHEnterpriseLandingPgIOS1.1] Focus navigates on hidden element after 'Dashboard' link
  • [GHEnterpriseLandingPgAndroid1.3] Keyboard focus order is illogical under 'The enterprise-ready platform that developers know and love' heading
  • [ProfAuditReq1.3] Screen reader focus does not retain on the 'Busy' checkbox on activation
  • [GH-PersonalInstructions_1.2] Keyboard focus order is not in logical order
  • [SecDashbrd1.17] Keyboard focus order is not in logical order
  • [SecDashbrd1.1] Keyboard focus order is not in logical order
  • [CopilotSettings1.30] Keyboard focus lands on the hidden control for expanded 'Select a policy' control
  • [CopilotSettings1.7] Keyboard focus is not retained on the dropdown control upon closing 'Confirm seats purchase' dialog
  • [Repo_Insights1.10] After applying 200% zoom, Keyboard focus is not in sync at the Additions and deletions control
  • [UserDashboard1.2]: Keyboard focus moves to the background control
  • [GHIssueViewr1.16] Keyboard focus is not logical upon invoking the 'Convert to issue' control
  • [GHIssueViewr1.6] Keyboard focus order is not logical upon invoking 'Load More' control
  • [GHCodespaces2.1] Upon closing the submenu with the esc key, the entire dialog box getting collapsed
  • [Rleasepage1.2] Keyboard focus does not retain on the triggered control upon activating the close control
  • [EcoSysAuth1.1] [GitHub Apps-OAuth App Authorization] Keyboard focus order is not logical after chevron icon
  • [Accountmgmt7.2] [Account Management-Payment Information] Keyboard focus is not sequential upon activating save control.
  • [Accountmgmt7.7] [Account Management-Payment Information] Keyboard focus order is not logical on invoking 'Add Information' control.
  • [Accountmgmt7.7] [Account Management-Payment Information] Keyboard focus moves to the background control without the -'Extra billing information' dialog collapsing
  • [AccntSettings1.2] [Account Management Controllers -Really change your username?] Keyboard focus order is not logical on dialog box
  • [OrgsSer1.12] Keyboard focus order is not logical on the 'Invite Member' dialog box.
  • [GH_Adt-Secrtylog1.5] Audit Log Security Logs-Export] Keyboard focus does not move to close button of the open status message
  • [AcctLogin1.9] [GitHub Account login-Add a Passkey-Delete passkey] Keyboard focus order is not logical on the 'Delete passkeys' dialog box
  • [ProfAuditReq1.24] [Profile Audit-Edit pinned items] Keyboard focus order is not logical on the 'Edit pinned items' dialog box
  • [GHDotCom-GHDotCom-EntrprsTrail22.1] [GitHub Dot Com Page-Enterprise Trail] In browse mode, screen reader focus is not moving to "Modsy" and "HashiCorp" graphic logo icons.
  • [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.
2.4.4 Link Purpose (In Context)

Partially Supports

Exceptions include:

  • [AcctLogin1.22] 'See More' link is not descriptive
  • [GHEnterpriseLandingPgAndroid1.10] 'Back to Content' link is not descriptive enough to identify the purpose
  • [Repo_Insights1.3] 'Profile' links present on the graph does not have discernible text
  • [GHDotCom-FeturCodeSe7.1] [GITHUBDOTCOM-Feature Code Search] Links 'try it now and watch video' are not descriptive enough.
  • [GHDotCom-feturIntgrns28.2] [GITHUBDOTCOM - Feature Integrations] ‘Learn More’ link is not descriptive enough when read aloud by screen reader.
  • [GHDotCom-FeturActns5.2] [GITHUBDOTCOM - Features Actions] Link 'View Docs' is not descriptive.
2.5.1 Pointer Gestures

Supports
2.5.2 Pointer Cancellation

Supports
2.5.3 Label in Name

Partially Supports

Exceptions include:

  • [GHIssueTypes1.1] Visual label and aria label are different for '10 types (max 25)' heading
  • [VerifiableDomains2.5] Visual name and aria-label are different for the 'Copy verification steps' control
  • [ProfAuditReq1.26] Visual name and `aria-label` are different for the 'Starred' control
  • [GHSponsers1.16] Visible label does not match the actual programmatic label 'Choose a custom amount'
  • [GlobalNav2.2] [Global Navigation-User Drawer] Visible label does not match the actual programmatic label 'What's happening?'
2.5.4 Motion Actuation

Supports
3.1.1 Language of Page

Supports
3.2.1 On Focus

Partially Supports

Exceptions include:

  • [GHActions_LargeRunner1.1] New page is getting displayed automatically while invoking the 'disable delete' menu control
3.2.2 On Input

Supports
3.2.6 Consistent Help

Not Evaluated
3.3.1 Error Identification

Supports
3.3.2 Labels or Instructions

Partially Supports

Exceptions include:

  • [AcctLogin1.7] Visible label is not defined for the Passkey nickname edit field
  • [Programmatic Acess-OrgsSer1.5] No instructions are provided for the edit field
3.3.7 Redundant Entry

Not Evaluated
4.1.2 Name Role Value

Partially Supports

Exceptions include:

  • [GHIssueTypes1.4] Screen reader does not announce the required information for edit field
  • [GHIssueViewr1.5] Accessible Name is not defined for the button
  • [GHIssueViewr1.2] Accessible name is not defined for form element
  • [IssueDashSavdView1.2] Invalid ARIA attribute defined for 'Change icon and color' control
  • [IssueDashSavdView1.2] Screen reader does not announce the state information
  • [ProfAuditReq1.38] 'Contribution activity in 2025' control is incorrectly defined as link
  • [ProfAuditReq1.25] Screen reader announces incorrect information for the selected option
  • [ProfAuditReq1.22] Screen reader does not announce current value for 'sort' dropdown.
  • [GHEnterpriseLandingPgIOS1.1] VoiceOver does not announce the name of the button present next to 'Enterprise'
  • [ActnUsgMetrcs1.13] Screen reader does not announce sort information for table headers
  • [ActnUsgMetrcs1.4] Screen reader does not announce current value for 'Qualifier' control
  • [GHEnterpriseLandingPgAndroid1.1] Talkback does not announce Name for Chevron expandable icon
  • [ActnUsgMetrcs1.4] Invalid ARIA attribute defined for 'Filter values' search field
  • [GHissueDshbd1.1] Screen reader does not announce the Role information
  • [ProfAuditReq1.2] Screen reader does not announce current value for 'Choose an emoji' control
  • [SecDashbrd1.17] Screen reader does not announce sort information for table headers.
  • [SecDashbrd1.1] Screen reader is not announcing the value for 'Qualifier' control
  • [GithubDisc1.16] ARIA attributes do not conform to valid values
  • [GHSponsers2.17] Label is not defined for the form element
  • [GHSponsers2.26] Screen reader is not announcing the value for 'Send email to' control
  • [GHSponsers2.7] Screen reader is not announcing the associated information for checkbox
  • [Repo_Insights1.1] Invalid ARIA attribute defined for the list items present within the 'Period' dropdown
  • [GHActions_LargeRunner1.8] Supported aria attribute is not defined for 'No configuration' list item
  • [AccntSettings1.3] ARIA dialog does not have an accessible name
  • [GHIssueViewr1.4] Role attribute does not have appropriate value for the control
  • [Rleasepage1.2] Role attribute does not have appropriate value for the control
  • [Accountmgmt4.2] [Account Management- Billing emails] Role attribute has an appropriate value for the element
  • [GlobalNav1.2] [Global Navigation-Repositories] Interactive controls are nested together
  • [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

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:

  • [GHIssueViewr1.21] Luminosity ratio for text 'No Matches' is 3.5:1
  • [Issueexp1.3] Luminosity ratio for text 'No Matches' is 3.5:1
  • [GHSponsers2.21] Luminosity Contrast ratio for 'No matches' text is 3.5:1
  • [GHIssueTypes1.6] Luminosity ratio for text 'No Matches' is 3.5:1
1.4.4 Resize text

Partially Supports

Exceptions include:

  • [GHEnterpriseLandingPgAndroid1.2] 'Unlock GitHub's Premium Features' Page gets truncated on settings browser zoom to 200%
  • [GHEnterpriseLandingPgIOS1.2] Upon resize the webpage to 200% of its original size, the contents of the page are getting cut off
1.4.5 Images of Text

Supports
1.4.10 Reflow

Partially Supports

Exceptions include:

  • [GHIssueViewr1.17] On setting the viewport to 320*256 px, GitHub handles texts are being cut off.
  • [GHIssueViewr1.3] Horizontal scroll bar appear for the reacted controls upon setting view port to 320*256 px
  • [Supporting the Platform-IssueDashSavdView1.2] On setting viewport to 320*256 px, controls are getting cutoff
  • [VerifiableDomains2.5] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [OrgsSer1.23] On setting the viewport to 320*256 px, 'Page 1' control is disappearing
  • [OrgsSer1.23] On setting the viewport to 320*256 px, placeholder text is getting cutoff
  • [Support Platform -VerifiableDomains1.5] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [GHSecurity1.2] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [ProfAuditReq1.25] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [EnterpriseLandingpage1.2] On setting viewport to 320*256 px, control is getting cutoff
  • [ActnUsgMetrcs1.13] On setting the viewport to 320*256 px, 'Page 1' control is disappearing
  • [ActnUsgMetrcs2.2] On setting the viewport to 320*256 px, control is getting truncated
  • [GHDependencyGrph1.5] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [GHDependencyGrph1.2] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [CopilotSettings1.28] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [CopilotSettings1.5] On setting the viewport to 320*256 px, text is getting overlapped
  • [CopilotSettings1.5] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [GHSponsers2.21] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [GHSponsers2.1] On setting the viewport to 320*256 px, controls are disappearing
  • [GHSponsers1.6] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [GHSponsers2.21] On setting viewport to 320*256 px, controls are getting cutoff
  • [GHSponsers2.5] List items within the dialog are not visible upon setting the viewport to 320*256 px
  • [Repo_Insights1.9] On setting the viewport to 320*256 px, text is getting overlapped
  • [GHActions_LargeRunner1.14] Content is disappearing upon setting the viewport to 320*256 px
  • [Supporting the platform-GHActions_LargeRunner1.5] Text is getting cutoff after setting the viewport to 320*256px
  • [Supporting the platform-GHActions_LargeRunner1.1] 'Search network configurations' placeholder text is getting cutoff after setting the viewport to 320*256px
  • [PR_MergeQueue1.4] On setting the viewport to 320*256 px, text is getting truncated
  • [GHOctocaptcha1.2] On setting the viewport to 320*256 px, Visual Puzzle controls are getting cut off.
  • [GHIssueTypes1.5] 'Unique name for your issue type' placeholder text is getting cutoff after setting the viewport to 320*256px
  • [GHModels3.4] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [GHDiversityReport1.2] On setting viewport to 320*256 px, star user images are getting disappeared
  • [AccntSettings3.1] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [GHadvisorydatabse1.3] Two-dimensional scrolling is required to read the contents of the page upon setting the viewport to 320*256 px
  • [Accountmgmt4.1] [Account Management-Billing emails] Edit control moves out of the designed box upon changing the viewport to 320*256 px
  • [OrgsSer1.7] [Orgs Service- Members] Keyboard focus indicator overlaps with the content on setting the viewport to 320*256 px
  • [OrgsSer1.23] [Orgs Service-Members] On setting the viewport to 320*256 pixels, 'Control and Text' is hard to read and use.
  • [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 px
  • [Repo_Insights1.7] Commits over time graph is overlapping, in 320*256 pixel viewport.
  • [AcctLogin1.20] On setting viewport to 320*256 px, Placeholder text is getting cutoff
  • [ProfAuditReq1.15] [Profile Audit-Following] Two-dimensional scrolling is required to read the contents of the 'Following' page upon setting the viewport to 320*256 px
  • [ProfAuditReq1.15] [Profile Audit-Following] After setting the viewport to 320*256 px, 'Following' icon and control are getting overlapped
  • [GH_ViewScrn6.50] On setting to viewport to 320*256 px, sub menu controls overlap
1.4.11 Non-text Contrast

Partially Supports

Exceptions include:

  • [GHSecurity1.1] Luminosity contrast ratio of the focus indicator for 'Pricing' control is 2.4:1
  • [GHSecurity1.11] Luminosity contrast ratio of the 'Not included' icon is less than 3:1
  • [AcctLogin1.1] Luminosity ratio of borderline for the edit field is 1.3:1
  • [GHEnterpriseLandingPgIOS1.5] Contrast ratio for focus indicator is 2.28:1 on link 'Learn more about Copilot for Business'
  • [EnterpriseLandingpage1.6] Luminosity contrast ratio of the focus indicator for 'Read customer story' control is 1:1
  • [EnterpriseLandingpage1.7] Luminosity ratio of the focus indicator for 'Explore GitHub Enterprise Importer' control is 1.1:1
  • [GHEnterpriseLandingPgAndroid1.6] Luminosity contrast ratio of the focus indicator for 'Read Customer Story' control is 1.8:1
  • [GHEnterpriseLandingPgAndroid1.5] Luminosity contrast ratio of the focus indicator for 'Learn more about Copilot for business' control is 2:1
  • [GHEnterpriseLandingPgAndroid1.6] Luminosity contrast ratio of the focus indicator for 'Learn more about CI/CD' control is 1.5:1
  • [ActnUsgMetrcs1.13] Luminosity contrast ratio of the focus indicator for 'page 1' control is 1:1
  • [EnterpriseLandingpage1.6] Luminosity contrast ratio of the focus indicator for 'Learn more about CI/CD' control is 1:1
  • [EnterpriseLandingpage1.5] Luminosity contrast ratio of the focus indicator for image is 1.1:1
  • [EnterpriseLandingpage1.4] Luminosity contrast ratio of the focus indicator for 'Learn more about Copilot for business' control is 1.1:1
  • [ProfAuditReq1.7] Luminosity ratio of border for the edit field is 1.4:1
  • [GHDependencyGrph1.2] Luminosity contrast ratio of border for the 'Filter by ecosystem' edit field is 1.4:1
  • [CopilotSettings1.28] Luminosity contrast ratio for the orange selected tab indicator with base line indication is 1.8:1
  • [CopilotSettings1.8] Luminosity contrast ratio for the orange selected tab indicator with base line indication is 1.8:1
  • [GHSponsers2.31] Luminosity contrast ratio of the focus indicator for 'Payouts' tab is 1.4:1
  • [GHSponsers1.8] Luminosity ratio of border for the edit field is 1.4:1
  • [Visual Requirment-GHSponsers2.26] Luminosity ratio of border for the edit field is 1.3:1
  • [GHActions_LargeRunner1.6] Luminosity ratio of border for the edit field is 1.4:1
  • [Accountmgmt7.1] [Account Management-Payment Information] Luminosity ratio of borderline for the edit field is 1.5:1
  • [AccntSettings1.3] [Account Management Controllers -Enter a new username] Luminosity ratio of borderline for the edit field is 1.5:1
  • [OrgsSer1.2] 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
  • [ProfAuditReq1.30] Luminosity contrast ratio for 'No contribution' controls is 1.1: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.
1.4.12 Text-spacing

Partially Supports

Exceptions include:

  • [ActnUsgMetrcs1.3] Upon applying text spacing, 'Source repository' text is getting cutoff
  • [Supporting the Platform-html ppln1.10] 'Copied' tooltip is not adapting the text spacing.
  • [SecDashbrd1.17] Upon applying text spacing, controls are getting overlapped
  • [GHNotebooks1.9] Upon applying text spacing, controls are getting overlapped
  • [GHIssueViewr1.7] Upon applying text spacing, 'subhash chamoli' text is getting truncated
  • [GHCodespaces1.11] Upon applying text spacing, 'Select a repository' dropdown text is getting truncated
  • [OrgsSer1.23] Placeholder text is getting cutoff on applying text spacing.
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:

  • [AcctLogin1.6] 'Select' control is not descriptive
  • [ProfAuditReq1.36] Incorrect aria-label is defined for the 'expand' control
  • [GHSponsers1.9] Descriptive group label is not defined for the 'combo boxes'
  • [GHSponsers2.5] Descriptive aria label is not defined for the 'Edit' control
2.4.7 Focus Visible

Partially Supports

Exceptions include:

  • [OrgsSer1.2] Keyboard focus indicator is not visible on 'Audio' control
  • [AcctLogin1.3] Keyboard focus indicator is not visible on the 'Audio' control
  • [GHEnterpriseLandingPgAndroid1.3] Keyboard focus indicator is not visible on 'Images' link control
  • [EnterpriseLandingpage1.1] Keyboard focus indicator is not visible on 'Play/Pause' control
  • [GH_Hovercard1.16] Keyboard focus indicator is not visible on 'sindresorhus' control
  • [Repo_Insights1.2] Keyboard focus indicator is not visible on progress bars
2.4.11 Focus Not Obscured (Minimum)

Not Evaluated
2.5.7 Dragging Movements

Not Evaluated
2.5.8 Target Size (Minimum)

Not Evaluated
3.1.2 Language of Parts

Supports
3.2.3 Consistent Navigation

Supports
3.2.4 Consistent Identification

Supports
3.3.3 Error Suggestion

Partially Supports

Exceptions include:

  • [OrgsSer1.2] No error suggestion appears by providing invalid input on the 'Contact email' control
3.3.4 Error Prevention (LFD)

Supports
3.3.8 Accessible Authentication (Minimum)

Not Evaluated
4.1.3 Status Messages

Partially Supports

Exceptions include:

  • [GHIssueViewr1.7] Screen Reader is not announcing the displayed warning message after exceeding limit of 10
  • [GHIssueViewr1.20] Screen reader does not announce the search result information on providing invalid input
  • [Issueexp1.3] Screen reader does not announce the search result information on providing invalid input
  • [IssueDashSavdView1.4] Screen reader is not announcing search result information upon selecting valid suggestions/data
  • [AcctLogin1.12] Screen reader does not announce displayed status message
  • [AcctLogin1.12] Screen reader does not announce displayed status message
  • [AcctLogin1.8] Screen reader does not announce displayed status message
  • [ProfAuditReq1.38] Screen reader does not announce the 'contributions in year' information
  • [ProfAuditReq1.4] Screen reader does not announce auto-filled Information after 'Busy' checkbox is selected
  • [ActnUsgMetrcs1.12] Screen reader does not announce the displayed alert message
  • [ActnUsgMetrcs1.4] Visual status message does not match the screen reader announcement
  • [ScalbleWbPltfm4.2] Screen reader does not announce the displayed error message
  • [html ppln2.20] Screen Reader does not announce displayed status message information
  • [SecDashbrd1.1] Screen reader does not announce the search result information on providing invalid input
  • [CopilotSettings1.28] Screen reader does not announce the search result information on providing invalid input
  • [GHSponsers2.17] Screen reader does not automatically announce the displayed status message
  • [GHSponsers2.21] Screen reader announces incorrect search result information on providing invalid input
  • [GHSponsers2.10] Screen reader does not announce the search result information on providing invalid input
  • [GHActions_LargeRunner1.11] Screen reader does not announce displayed status message information
  • [GHActions_LargeRunner1.4] Screen reader is not announcing updated status message information
  • [GHActions_LargeRunner1.8] Screen reader does not announce the search result information on providing invalid input
  • [GHSponsers1.17] Screen reader is not announcing displayed status message information
  • [GHSponsers3.2] Screen reader is not announcing displayed status message information
  • [GHIssueTypes1.3] Screen reader is not announcing status message information
  • [GHIssueTypes1.6] Screen reader announces incorrect search result information after being given invalid input
  • [GHIssueViewr1.7] Screen reader announce incorrect the search result information on providing invalid input
  • [GHIssueIndex1.4] Screen reader does not announce the search result information on providing invalid input
  • [Issueexp1.2] Screen reader is announcing incorrect updated information after providing invalid input in 'Filter type' input field
  • [GHCodespaces3.2] Screen reader does not announce the search result information on providing invalid input
  • [Rleasepage1.9] Screen reader does not announce the search results on providing invalid input
  • [OrgsSer1.8] Screen reader does not announce the displayed status message information
  • [GH_Adt-Secrtylog1.5] Audit Log Security Logs-Export] Screen reader does not announce the status message information
  • [ProfAuditReq1.32] Upon selecting the checkboxes screen reader does not announce the changing status message information

Disclaimer

©2025 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.2 conformance reports provide the information included in ITI’s “VPAT® 2.5 WCAG (November 2023)” 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.2). 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.

Back to conformance reports