Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-4t2cwt

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://github.io/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://github.io/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Breadcrumb navigation detected

Got: aria-label

Skip navigation link detected

4 navigation landmark(s) detected

Breadcrumbs aria-label navigation

Skip Link Skip link detected

Labeled Navigation 4 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Form Accessibility

2 of 4 controls have issues

REVIEW

2 of 4 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="text" name="survey-token">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text">

2 control(s) properly labeled

4 controls

2 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#survey-yes	radio	Yes	aria-label
#survey-no	radio	No	aria-label
input	text	(Search articles)	placeholder only
survey-token	text	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

5 issue(s) across 56 links and 13 buttons

REVIEW

5 issue(s) across 56 links and 13 buttons

2 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /en/site-policy/privacy-policies/github-privacy-statement; /contributing

5 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button[data-testid="mobile-search-button"]; button#:R1j776:; button[data-testid="mobile-search-button"]; button#:R4j776:; button[data-testid="sidebar-hamburger"]

54 link(s) with descriptive text

56 links

0 empty

0 generic text

2 new tab

5 empty buttons

Element	Text	Issue	Suggested Fix
/en/site-policy/privacy-policies/github-…	Privacy policy	new tab	Add '(opens in new tab)' to text
/contributing	Learn how to contribute	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

62 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

/en/site-policy/privacy-policies/github-privacy-statement; /contributing

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button[data-testid="mobile-search-button"]; button#:R1j776:; button[data-testid="mobile-search-button"]; button#:R4j776:; button[data-testid="sidebar-hamburger"]

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

A+

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

17 headings

PASS

17 headings

Single H1 present

H2 GitHub Pages
H1 GitHub Pages documentation
H2 Articles
H3 About custom domains and GitHub Pages
H3 About GitHub Pages and Jekyll
H3 About Jekyll build errors for GitHub Pages sites
H3 Adding a theme to your GitHub Pages site using Jekyll
H3 Adding content to your GitHub Pages site using Jekyll
H3 Configuring a publishing source for your GitHub Pages site
H3 Creating a custom 404 page for your GitHub Pages site
H3 Creating a GitHub Pages site
H3 Creating a GitHub Pages site with Jekyll
H2 Help and support
H3 Did you find what you needed?
H3 Help us make these docs great!
H3 Still need help?
H2 Legal

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 GitHub Pages documen…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Articles	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Help and support	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Legal	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Did you find what yo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Help us make these d…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Still need help?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title GitHub Pages documen…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span GitHub Docs	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Version:	20.27:1	4.5:1	#000000	#FAFBFC	Pass
span Free, Pro, & Team	19.73:1	4.5:1	#000000	#F6F8FA	Pass
span Search or ask Copilo…	19.73:1	4.5:1	#000000	#F6F8FA	Pass
span Search or ask	19.73:1	4.5:1	#000000	#F6F8FA	Pass
span Copilot	19.73:1	4.5:1	#000000	#F6F8FA	Pass
span Select language: cur…	19.73:1	4.5:1	#000000	#F6F8FA	Pass
span Search or ask Copilo…	19.73:1	4.5:1	#000000	#F6F8FA	Pass
span Search or ask	19.73:1	4.5:1	#000000	#F6F8FA	Pass
span Copilot	19.73:1	4.5:1	#000000	#F6F8FA	Pass
span Open menu	19.73:1	4.5:1	#000000	#F6F8FA	Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 27 passed

PASS

100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●ARIA `tooltip` elements have accessible names

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.