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 1 REVIEW 7 FIX

Heading Hierarchy

Action

44 headings, 3 skip(s)

FIX

44 headings, 3 skip(s)

Multiple H1 headings (8 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Navigation Menu
H1 Search code, repositories, users, issues, pull requests...
H1 Provide feedback duplicate H1
H1 Saved searches duplicate H1
H2 Use saved searches to filter your results more quickly
H1 Home duplicate H1
H1 Browser Support duplicate H1
H2 Desktop
H2 Mobile
H1 Selectors duplicate H1
H2 CSS3
H2 Other selectors and conventions
H4 Changes skipped
H4 Additions
H4 Form Selector Additions
H4 Positional Selector Additions
H1 API duplicate H1
H2 Public API
H4 Sizzle( String selector[, DOMNode context[, Array results]] ) skipped
H4 Sizzle.matchesSelector( DOMElement element, String selector )
H4 Sizzle.matches( String selector, Array<DOMElement> elements )
H2 Extension API
H4 Sizzle.selectors.match.NAME = RegExp skipped
H3 Finding
H4 Sizzle.selectors.find.NAME = function( match, context, isXML ) {}
H3 Filtering
H4 Sizzle.selectors.preFilter.NAME = function( match ) {}
H5 Sizzle.selectors.filter.NAME: function( element, match[1][, match[2], match[3], ...] ) {}
H3 Attributes
H4 Sizzle.selectors.attrHandle.LOWERCASE_NAME = function( elem, casePreservedName, isXML ) {}
H3 Pseudo-selectors (pseudos)
H4 Sizzle.selectors.pseudos.NAME = function( elem ) {}
H4 Sizzle.selectors.createPseudo(function)
H5 Backwards-compatible plugins for pseudos with arguments
H4 Sizzle.selectors.setFilters.LOWERCASE_NAME = function( elements, argument, not ) {}
H2 Internal API
H3 Sizzle.selectors.cacheLength
H3 Sizzle.compile( selector )
H1 Thanks duplicate H1
H2 Toggle table of contents Pages 2
H3 Uh oh!
H3 Clone this wiki locally
H2 Footer
H3 Footer navigation

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

Action

19 issue(s) across 198 links and 28 buttons

FIX

19 issue(s) across 198 links and 28 buttons

13 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #browsers; #desktop; #mobile; #selectors; #api; #public-api; #extension-api; #finding; #filtering; #attributes (+3 more)

11 link(s) open in new tab without warning

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

Got: https://docs.github.com; https://github.blog; https://github.blog/changelog; https://skills.github.com; https://docs.github.com; https://support.github.com; https://securitylab.github.com; https://maintainers.github.com; https://stars.github.com; https://archiveprogram.github.com (+1 more)

6 button(s) with no accessible text

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

Got: button#icon-button-f5214ae8-7d04-4474-8be5-1825b5ccff46; button#query-builder-test-clear-button; button#icon-button-1ddfe64f-5ee3-409b-a619-53def8ca66a5; button#icon-button-d5c7e6b8-62eb-4c65-8b85-0387731d991d; button#action-menu-c6bd8b1d-455d-40bf-bdfd-9337bd8e2c38-button; button#icon-button-d90a86b6-faab-439a-970e-af330796e2e4

174 link(s) with descriptive text

198 links

13 empty

0 generic text

11 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
https://docs.github.com	Documentation	new tab	Add '(opens in new tab)' to text
https://github.blog	Blog	new tab	Add '(opens in new tab)' to text
https://github.blog/changelog	Changelog	new tab	Add '(opens in new tab)' to text
https://skills.github.com	GitHub Skills	new tab	Add '(opens in new tab)' to text
https://docs.github.com	Documentation	new tab	Add '(opens in new tab)' to text
https://support.github.com	Customer support	new tab	Add '(opens in new tab)' to text
https://securitylab.github.com	Security Lab	new tab	Add '(opens in new tab)' to text
https://maintainers.github.com	Maintainer Community	new tab	Add '(opens in new tab)' to text
https://stars.github.com	GitHub Stars	new tab	Add '(opens in new tab)' to text
https://archiveprogram.github.com	Archive Program	new tab	Add '(opens in new tab)' to text
https://docs.github.com/search-github/gi…	Search syntax tips	new tab	Add '(opens in new tab)' to text
#browsers	(empty)	empty	Add link text or aria-label
#desktop	(empty)	empty	Add link text or aria-label
#mobile	(empty)	empty	Add link text or aria-label
#selectors	(empty)	empty	Add link text or aria-label
#api	(empty)	empty	Add link text or aria-label
#public-api	(empty)	empty	Add link text or aria-label
#extension-api	(empty)	empty	Add link text or aria-label
#finding	(empty)	empty	Add link text or aria-label
#filtering	(empty)	empty	Add link text or aria-label
#attributes	(empty)	empty	Add link text or aria-label
#pseudo-selectors	(empty)	empty	Add link text or aria-label
#back-compat	(empty)	empty	Add link text or aria-label
#internal-api	(empty)	empty	Add link 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
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

196 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#browsers; #desktop; #mobile; #selectors; #api; #public-api; #extension-api; #finding; #filtering; #attributes (+3 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://docs.github.com; https://github.blog; https://github.blog/changelog; https://skills.github.com; https://docs.github.com; https://support.github.com; https://securitylab.github.com; https://maintainers.github.com; https://stars.github.com; https://archiveprogram.github.com (+1 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-f5214ae8-7d04-4474-8be5-1825b5ccff46; button#query-builder-test-clear-button; button#icon-button-1ddfe64f-5ee3-409b-a619-53def8ca66a5; button#icon-button-d5c7e6b8-62eb-4c65-8b85-0387731d991d; button#action-menu-c6bd8b1d-455d-40bf-bdfd-9337bd8e2c38-button; button#icon-button-d90a86b6-faab-439a-970e-af330796e2e4

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

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-jp8fpd

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

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://sizzlejs.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://sizzlejs.com/manifest.json

Manifest contains invalid JSON.

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 ✗

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.

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+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

Form Accessibility

1 of 7 controls have issues

PASS

1 of 7 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="feedback" id="feedback">

6 control(s) properly labeled

7 controls

6 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#query-builder-test	text	Search	for/id
#include_email	checkbox	Include my email address so I can be contacted	aria-label
#custom_scope_name	text	Name	for/id
#custom_scope_query	text	Query	for/id
#wiki-pages-filter	text	Find a page or section	aria-label
#wiki-clone-url	text	Clone URL for this wiki	aria-label
#feedback	textarea	(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

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 Search code, reposit…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Provide feedback	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Saved searches	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Home	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Browser Support	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Selectors	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 API	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Thanks	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Navigation Menu	19.73:1	3.0:1	#000000	#F6F8FA	Pass
h2 Use saved searches t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Desktop	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Mobile	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 CSS3	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Other selectors and …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Public API	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Extension API	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Internal API	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Finding	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Filtering	21.00:1	3.0:1	#000000	#FFFFFF	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.

Lighthouse Accessibility Audits

Score 91/100 — 3 failing, 23 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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Changes `div#wiki-body > div.markdown-body > div.markdown-heading > h4.heading-element`
Sizzle( String selector[, DOMNode context[, Array results]] ) `div#wiki-body > div.markdown-body > div.markdown-heading > h4.heading-element`
Sizzle.selectors.match.NAME = RegExp `div#wiki-body > div.markdown-body > div.markdown-heading > h4.heading-element`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.markdown-body > div.markdown-heading > h1.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h1.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h1.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h1.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h1.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h1.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h3.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h3.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h3.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h3.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h3.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h3.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h3.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h3.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h5.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h5.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
div.markdown-body > div.markdown-heading > h1.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h1.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h1.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h1.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h1.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h1.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor`
div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor `div.markdown-body > div.markdown-heading > h2.heading-element > a.anchor`
Terms `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Privacy `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Security `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Status `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Community `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Docs `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Contact `nav > ul.list-style-none > li.mx-2 > a.Link--secondary`
Manage cookies `ul.list-style-none > li.mx-2 > cookie-consent-link > button.Link--secondary`
Do not share my personal information `ul.list-style-none > li.mx-2 > cookie-consent-link > button.Link--secondary`

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

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

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

●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 are distinguishable without relying on color.

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○Elements with visible text labels have matching accessible names.

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