Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 13 -1-on-focusable

FIX

0 positive, 13 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

7 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 7 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

B

Heading Hierarchy

32 headings, 1 skip(s)

REVIEW

32 headings, 1 skip(s)

Multiple H1 headings (4 found)

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

Heading level skipped: H1 → H3 (missing H2)

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

1 hidden heading(s) (aria-hidden)

H2 Navigation Menu
H1 Search code, repositories, users, issues, pull requests...
H3 Explore hidden
H1 Provide feedback duplicate H1
H1 Saved searches duplicate H1
H2 Use saved searches to filter your results more quickly
H1 The future of building happens together duplicate H1
H2 GitHub features
H2 GitHub customers
H2 Accelerate your entire workflow
H3 Your AI partner everywhere. Copilot is ready to work with you at each step of the software development lifecycle.
H3 Automate your path to production
H3 Code instantly from anywhere
H3 Keep momentum on the go
H3 Shape your toolchain
H2 Built-in application security where found means fixed
H3 Apply fixes in seconds. Spend less time debugging and more time building features with Copilot Autofix.
H2 Work together, achieve more
H3 Plan with clarity. Organize everything from high-level roadmaps to everyday tasks.
H3 Keep track of your tasks
H3 Share ideas and ask questions
H3 Review code changes together
H3 Fund open source projects
H2 From startups to enterprises, GitHub scales with teams of any size in any industry.
H2 Millions of developers and businesses call GitHub home
H2 Footnotes
H2 Site-wide Links
H3 Subscribe to our developer newsletter
H3 Platform
H3 Ecosystem
H3 Support
H3 Company

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

C

Link & Button Quality

Action

2 issue(s) across 155 links and 46 buttons

REVIEW

2 issue(s) across 155 links and 46 buttons

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)

2 button(s) with no accessible text

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

Got: button#query-builder-test-clear-button; button#icon-button-9bc462ee-c9eb-4041-8848-30eb42c90770

144 link(s) with descriptive text

155 links

0 empty

0 generic text

11 new tab

2 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
/customer-stories/figma	TechnologyFigma streamlines de…	img no alt	Add alt attribute to the image
/customer-stories/mercedes-benz	AutomotiveMercedes-Benz standa…	img no alt	Add alt attribute to the image
/customer-stories/mercado-libre	Financial servicesMercado Libr…	img no alt	Add alt attribute to the image
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

188 links and buttons have descriptive text

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#query-builder-test-clear-button; button#icon-button-9bc462ee-c9eb-4041-8848-30eb42c90770

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

C

Tap Target Adequacy

Action

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

REVIEW

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

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

B

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 ✗

B

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

B

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.

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Search code, repositories, users, issues…

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Provide feedback

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Saved searches

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

32px · bottom of viewport

h1 The future of building happens together

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Navigation Menu

1.11:1

#000000

on

#050740

needs 3.0:1 (large text)

24px · top of page (header area)

h2 Use saved searches to filter your result…

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 GitHub features

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 GitHub customers

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Millions of developers and businesses ca…

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Footnotes

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Site-wide Links

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Explore

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Automate your path to production

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Code instantly from anywhere

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Keep momentum on the go

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Shape your toolchain

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Apply fixes in seconds.

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Keep track of your tasks

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Share ideas and ask questions

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Review code changes together

1.40:1

#000000

on

#23272E

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Search code, reposit…	1.40:1	3.0:1	#000000	#23272E	Fail
h1 Provide feedback	1.40:1	3.0:1	#000000	#23272E	Fail
h1 Saved searches	1.40:1	3.0:1	#000000	#23272E	Fail
h1 The future of buildi…	1.40:1	3.0:1	#000000	#23272E	Fail
h2 Navigation Menu	1.11:1	3.0:1	#000000	#050740	Fail
h2 Use saved searches t…	1.40:1	3.0:1	#000000	#23272E	Fail
h2 GitHub features	1.40:1	3.0:1	#000000	#23272E	Fail
h2 GitHub customers	1.40:1	3.0:1	#000000	#23272E	Fail
h2 Millions of develope…	1.40:1	3.0:1	#000000	#23272E	Fail
h2 Footnotes	1.40:1	3.0:1	#000000	#23272E	Fail
h2 Site-wide Links	1.40:1	3.0:1	#000000	#23272E	Fail
h3 Explore	1.40:1	3.0:1	#000000	#23272E	Fail
h3 Automate your path t…	1.40:1	3.0:1	#000000	#23272E	Fail
h3 Code instantly from …	1.40:1	3.0:1	#000000	#23272E	Fail
h3 Keep momentum on the…	1.40:1	3.0:1	#000000	#23272E	Fail
h3 Shape your toolchain	1.40:1	3.0:1	#000000	#23272E	Fail
h3 Apply fixes in secon…	1.40:1	3.0:1	#000000	#23272E	Fail
h3 Keep track of your t…	1.40:1	3.0:1	#000000	#23272E	Fail
h3 Share ideas and ask …	1.40:1	3.0:1	#000000	#23272E	Fail
h3 Review code changes …	1.40:1	3.0:1	#000000	#23272E	Fail

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

Landmark Structure

18 landmarks

PASS

18 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

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.

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 Text Quality

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

PASS

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

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

A

Alt Text Quality

All 24 images OK

PASS

All 24 images OK

3 image(s) with alt text over 125 characters

17 decorative image(s) correctly marked

4 image(s) with good alt text

24 images 4 good alt text 17 decorative

Issue	Count
too long	3 image(s)

A

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
#hero_user_email	email	Enter your email	for/id
#bottom_cta_section_user_email	email	Enter your email	for/id
#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

Form Input Types

2 input(s) using type=text where a specific type would help

PASS

2 input(s) using type=text where a specific type would help

Input "query-builder-test" should use type="search" (currently type="text")

Field name "query-builder-test" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "custom_scope_query" should use type="search" (currently type="text")

Field name "custom_scope_query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

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

PASS

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

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

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

PASS

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

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

A

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)

A

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+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 29 passed

PASS

97

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
Terms `nav > ul.list-style-none > li > a.Link--secondary`
What is Git? `nav > ul.list-style-none > li > a.Link--secondary`
Manage cookies `ul.list-style-none > li > cookie-consent-link > button.Link--secondary`
Do not share my personal information `ul.list-style-none > li > cookie-consent-link > button.Link--secondary`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Code `div.Toggle-wrapper > div > div#_R_2k5b_ > button#_R_2k5b_-button`

○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

●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

●`[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

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

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

●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

●`[lang]` attributes have a valid value

●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"]`

○`[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 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

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

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