Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 5 REVIEW 2 FIX

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 ✗

Link & Button Quality

Action

5 issue(s) across 143 links and 25 buttons

REVIEW

5 issue(s) across 143 links and 25 buttons

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /platform ("Learn more"); /features/copilot ("Learn more")

12 link(s) open in new tab without warning

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

Got: https://docs.github.com/en; https://learn.github.com/skills; https://learn.github.com/credentials; https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilo…; https://github.blog/changelog/; https://docs.github.com/en; https://github.blog/; https://help.github.com/; https://learn.github.com/skills; https://www.githubstatus.com/ (+2 more)

3 button(s) with no accessible text

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

Got: button#icon-button-31069fd1-e0d0-4e27-b5a7-909278e78baf; button[data-testid="IconButton"]; button[data-testid="IconButton"]

129 link(s) with descriptive text

143 links

0 empty

2 generic text

12 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://github.com/platform	GitHubRepository hosting, code…	img no alt	Add alt attribute to the image
https://github.com/features/copilot	CopilotAI coding agent for tas…	img no alt	Add alt attribute to the image
https://docs.github.com/en	Documentation	new tab	Add '(opens in new tab)' to text
https://learn.github.com/skills	Training	new tab	Add '(opens in new tab)' to text
https://learn.github.com/credentials	Certifications	new tab	Add '(opens in new tab)' to text
https://docs.github.com/en/copilot/how-t…	Customize Copilot	new tab	Add '(opens in new tab)' to text
https://github.blog/changelog/	ChangelogYour source for the l…	new tab	Add '(opens in new tab)' to text
https://docs.github.com/en	Documentation	new tab	Add '(opens in new tab)' to text
https://github.blog/	Blog	new tab	Add '(opens in new tab)' to text
https://help.github.com/	Customer support	new tab	Add '(opens in new tab)' to text
https://learn.github.com/skills	Training	new tab	Add '(opens in new tab)' to text
https://www.githubstatus.com/	GitHub Status	new tab	Add '(opens in new tab)' to text
https://github.blog/changelog/	Changelog	new tab	Add '(opens in new tab)' to text
https://githubuniverse.com/	GitHub UniverseThe event for d…	new tab	Add '(opens in new tab)' to text
https://github.com/events/universe/recap…	GitHub Universe ‘26 Recap	img no alt	Add alt attribute to the image
/platform	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Platform
/features/copilot	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Copilot
<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

151 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/platform ("Learn more"); /features/copilot ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://docs.github.com/en; https://learn.github.com/skills; https://learn.github.com/credentials; https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilo…; https://github.blog/changelog/; https://docs.github.com/en; https://github.blog/; https://help.github.com/; https://learn.github.com/skills; https://www.githubstatus.com/ (+2 more)

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#icon-button-31069fd1-e0d0-4e27-b5a7-909278e78baf; button[data-testid="IconButton"]; button[data-testid="IconButton"]

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

Tap Target Adequacy

Action

5 tap target(s) too small or too close together

REVIEW

5 tap target(s) too small or too close together

5 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found · GitHub · GitHub ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

13 icon(s) detected

REVIEW

13 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'>.

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light dark

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #1e2327

Detection limited to meta tags and inline styles

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

Dark Mode✓ Dark Mode Supported

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

Detection limited to meta tags and inline styles.

Landmark Structure

25 landmarks

PASS

25 landmarks

<main> landmark present

7 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Skip link target(s) don't exist on page: #start-of-content

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Hierarchy

28 headings

PASS

28 headings

Single H1 present

H2 Navigation Menu
H1 Software still starts with you
H2 Product walkthrough
H2 GitHub activity
H2 GitHub Platform
H3 GitHub
H3 Copilot
H2 More ways to use GitHub
H3 Actions
H3 Code Quality
H3 Code Security
H3 Secret Protection
H3 Codespaces
H2 Whatever you're building, you can build it on GitHub
H2 What our customers say
H2 Companies using GitHub
H2 Customer stories
H3 Figma streamlines development and strengthens security
H3 Mercedes-Benz standardizes source code and automates onboarding
H3 Mercado Libre cuts coding time by 50%with GitHub Copilot
H2 Featured repositories
H2 Join the world's largest developer community
H2 Site-wide Links
H3 The developer newsletter
H3 Products
H3 Developers
H3 Support
H3 Company

A+

Heading Text Quality

All 28 heading(s) have substantive, well-formed text

PASS

All 28 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 22 images OK

PASS

All 22 images OK

15 decorative image(s) correctly marked

7 image(s) with good alt text

22 images 7 good alt text 15 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#_R_9j8l_	email	Enter your email	for/id
#_R_1atcl_	email	Enter your email	for/id

A+

Form Input Types

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

2 form control(s) checked, no input-semantic issues

PASS

2 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

All 193 visible text node(s) render at >= 12 CSS pixels

PASS

All 193 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: GitHub

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name GitHub ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name GitHub Display Mode standalone Icons 11 icon(s)

PWA Depth

2 PWA signal(s) surfaced

PASS

2 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

Manifest is missing `theme_color`

Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

iOS smart-banner opt-in present (`apple-itunes-app`)

The page declares a companion iOS app via `<meta name="apple-itunes-app" content="app-id=...">`. iOS Safari shows a smart banner offering to open the page in the app, with an unobtrusive 'X' to dismiss. Recommended when you have a published companion app.

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

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
h2 Navigation Menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Product walkthrough	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h2 GitHub activity	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h2 GitHub Platform	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h2 More ways to use Git…	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h2 Whatever you're buil…	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h2 What our customers s…	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h2 Companies using GitH…	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h2 Customer stories	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h2 Featured repositorie…	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h2 Join the world's lar…	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h2 Site-wide Links	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h3 GitHub	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h3 Copilot	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h3 Actions	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h3 Code Quality	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h3 Code Security	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h3 Secret Protection	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h3 Codespaces	16.98:1	3.0:1	#000000	#E4E8E6	Pass
h3 The developer newsle…	16.98:1	3.0:1	#000000	#E4E8E6	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 96/100 — 1 failing, 26 passed

PASS

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to testimonial 1 `div.Primer_Brand__TestimonialGroup-module__TestimonialGroup__controls___S4ca5 > div.Primer_Brand__CarouselPagination-module__CarouselPagination___PH90q > div.Primer_Brand__CarouselPagination-module__CarouselPagination__indicators___ReV_f > button.Primer_Brand__CarouselPagination-module__CarouselPagination__indicator___cq9Tv`
Go to testimonial 2 `div.Primer_Brand__TestimonialGroup-module__TestimonialGroup__controls___S4ca5 > div.Primer_Brand__CarouselPagination-module__CarouselPagination___PH90q > div.Primer_Brand__CarouselPagination-module__CarouselPagination__indicators___ReV_f > button.Primer_Brand__CarouselPagination-module__CarouselPagination__indicator___cq9Tv`
Go to testimonial 3 `div.Primer_Brand__TestimonialGroup-module__TestimonialGroup__controls___S4ca5 > div.Primer_Brand__CarouselPagination-module__CarouselPagination___PH90q > div.Primer_Brand__CarouselPagination-module__CarouselPagination__indicators___ReV_f > button.Primer_Brand__CarouselPagination-module__CarouselPagination__indicator___cq9Tv`
Go to testimonial 4 `div.Primer_Brand__TestimonialGroup-module__TestimonialGroup__controls___S4ca5 > div.Primer_Brand__CarouselPagination-module__CarouselPagination___PH90q > div.Primer_Brand__CarouselPagination-module__CarouselPagination__indicators___ReV_f > button.Primer_Brand__CarouselPagination-module__CarouselPagination__indicator___cq9Tv`
Go to testimonial 5 `div.Primer_Brand__TestimonialGroup-module__TestimonialGroup__controls___S4ca5 > div.Primer_Brand__CarouselPagination-module__CarouselPagination___PH90q > div.Primer_Brand__CarouselPagination-module__CarouselPagination__indicators___ReV_f > button.Primer_Brand__CarouselPagination-module__CarouselPagination__indicator___cq9Tv`

These items highlight common accessibility best practices.

○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

●Image elements have `[alt]` attributes

●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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Identical links have the same purpose.

●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 `tooltip` elements 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.

○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.

○Skip links are focusable.

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

○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

○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.

○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.