github.com Accessibility Report

Accessibility audit of github.com — scanned on Feb 20, 2026

Technology
0 /100
D Poor

6 issues found across 3 categories

3 Critical 2 Major 1 Minor

WCAG Compliance Overview

Perceivable 3 issues
Operable 0 issues
Understandable 0 issues
Robust 3 issues

Issues Found

Form inputs missing labels

Critical

Form elements must have associated labels so users know what information to enter.

WCAG 1.3.1
1 element(s) affected
  • <textarea name="feedback">
How to fix

Add <label> elements with matching for attributes, or use aria-label.

Buttons missing accessible name

Critical

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
2 element(s) affected
  • <button>
  • <button>
How to fix

Add text content, aria-label, or title to all <button> elements.

Videos missing captions

Critical

Video content must have captions for deaf and hard-of-hearing users.

WCAG 1.2.2
2 element(s) affected
  • <video> "(inline)"
  • <video> "(inline)"
How to fix

Add closed captions or subtitles to all video content.

Duplicate element IDs

Major

Element IDs must be unique to ensure correct assistive technology behavior.

WCAG 4.1.1
11 element(s) affected
  • id="clip0_1_610"
  • id="clip0_1_688"
  • id="clip0_43_208"
  • id="clip0_99_61"
  • id="clip0_66_71316"
How to fix

Make each id attribute value unique within the page.

Invalid ARIA attributes

Major

ARIA attributes must be valid and used correctly to work with assistive technologies.

WCAG 4.1.2
1 element(s) affected
  • <dialog aria-describedby="feedback-dialog-description"> (missing ref)
How to fix

Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

Incorrect list structure

Minor

List items must be contained within <ul>, <ol>, or <dl> elements.

WCAG 1.3.1
16 element(s) affected
  • <dt> outside <dl>
  • <dd> outside <dl>
How to fix

Ensure <li> elements are direct children of <ul> or <ol>.

Top Priority Fixes

Here are the most impactful changes github.com should make to improve accessibility:

  1. #1
    Buttons missing accessible name Critical

    Add text content, aria-label, or title to all <button> elements.

  2. #2
    Videos missing captions Critical

    Add closed captions or subtitles to all video content.

  3. #3
    Form inputs missing labels Critical

    Add <label> elements with matching for attributes, or use aria-label.

Frequently Asked Questions

Is github.com accessible?

github.com scored 36/100 (grade D) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is github.com WCAG compliant?

Our scan found 6 accessibility issues on github.com. Full WCAG compliance requires addressing all critical and major issues identified above.

Is github.com EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see github.com's compliance status.

What accessibility issues does github.com have?

See the full issue list above with severity levels, affected elements, and recommended fixes for github.com.

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing