github.io Accessibility Report

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

Technology
0 /100
C Needs Improvement

5 issues found across 3 categories

1 Critical 3 Major 1 Minor

WCAG Compliance Overview

Perceivable 2 issues
Operable 2 issues
Understandable 0 issues
Robust 1 issues

Issues Found

Links missing accessible name

Critical

Links must have discernible text so screen reader users understand their purpose.

WCAG 2.4.4
4 element(s) affected
  • <a href="https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/abou">
  • <a href="https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pag">
  • <a href="https://docs.github.com/pages">
  • <a href="/">
How to fix

Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

Heading levels skip order

Major

Headings should follow a logical order (h1 → h2 → h3) without skipping levels.

WCAG 1.3.1
2 element(s) affected
  • <h4> "Create a repository" (after h2)
  • <h4> "Blogging with Jekyll" (after h1)
How to fix

Restructure headings to follow sequential order. Don't skip from h1 to h3.

Duplicate element IDs

Major

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

WCAG 4.1.1
1 element(s) affected
  • id="setup-in-desktop"
How to fix

Make each id attribute value unique within the page.

Generic link text

Major

Links must have descriptive text that indicates their purpose. Generic text like 'click here' or 'read more' does not help screen reader users understand where the link goes.

WCAG 2.4.4
1 element(s) affected
  • <a href="https://docs.github.com/en/pages/configuring-a-custom-domain">read more</a>
How to fix

Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.

Incorrect list structure

Minor

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

WCAG 1.3.1
3 element(s) affected
  • <li> inside <div>
How to fix

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

Top Priority Fixes

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

  1. #1
    Links missing accessible name Critical

    Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

  2. #2
    Heading levels skip order Major

    Restructure headings to follow sequential order. Don't skip from h1 to h3.

  3. #3
    Duplicate element IDs Major

    Make each id attribute value unique within the page.

Frequently Asked Questions

Is github.io accessible?

github.io scored 58/100 (grade C) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is github.io WCAG compliant?

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

Is github.io EAA compliant?

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

What accessibility issues does github.io have?

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

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing