Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 33 -1-on-focusable

FIX

0 positive, 33 -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.)

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

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

F

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Search

Skip Link

Labeled Navigation 1 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Favicon & Branding

9 icon(s) detected

REVIEW

9 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

B

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Bang

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name Bang ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name Bang Display Mode standalone Theme Color #000000 Background Color #000000 Icons 2 icon(s)

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: dark light

prefers-color-scheme CSS detected in inline styles

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 dark light ✓Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA 6 pass AA only

title Unlimited adult porn videos in 4K and Ul…

1.26:1

#000000

on

#1E1E1E

needs 4.5:1 (normal text)

16px · top of page (header area)

span get unlimited porn

1.26:1

#000000

on

#1E1E1E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Get Access

4.23:1

#000000

on

#697177

needs 4.5:1 (normal text)

16px · above the fold

span Originals

1.31:1

#000000

on

#25201F

needs 4.5:1 (normal text)

16px · above the fold

div Loading...

1.16:1

#000000

on

#161616

needs 4.5:1 (normal text)

16px · above the fold

span Videos

1.16:1

#000000

on

#161616

needs 4.5:1 (normal text)

16px · above the fold

span Newest Videos

1.16:1

#000000

on

#161616

needs 4.5:1 (normal text)

16px · above the fold

span Trending Videos

1.16:1

#000000

on

#161616

needs 4.5:1 (normal text)

16px · above the fold

span Most Popular

1.16:1

#000000

on

#161616

needs 4.5:1 (normal text)

16px · above the fold

span Most Liked

1.16:1

#000000

on

#161616

needs 4.5:1 (normal text)

16px · above the fold

span Movies

1.16:1

#000000

on

#161616

needs 4.5:1 (normal text)

16px · above the fold

span Studios

1.16:1

#000000

on

#161616

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Hottest Porn Videos …	3.10:1	3.0:1	#000000	#5E46BE	Pass
h2 Top Movies	3.10:1	3.0:1	#000000	#5E46BE	Pass
h2 Hottest Movies	3.10:1	3.0:1	#000000	#5E46BE	Pass
h3 Hottest Pornstars	3.10:1	3.0:1	#000000	#5E46BE	Pass
h3 Top Channels	3.10:1	3.0:1	#000000	#5E46BE	Pass
h3 Porn	3.10:1	3.0:1	#000000	#5E46BE	Pass
title Unlimited adult porn…	1.26:1	4.5:1	#000000	#1E1E1E	Fail
span get unlimited porn	1.26:1	4.5:1	#000000	#1E1E1E	Fail
span Free Access	18.61:1	4.5:1	#000000	#EEF2F1	Pass
a Sign In	9.45:1	4.5:1	#000000	#AEAFA1	Pass
a Get Access	4.23:1	4.5:1	#000000	#697177	Fail
span Originals	1.31:1	4.5:1	#000000	#25201F	Fail
div Loading...	1.16:1	4.5:1	#000000	#161616	Fail
span Videos	1.16:1	4.5:1	#000000	#161616	Fail
span Newest Videos	1.16:1	4.5:1	#000000	#161616	Fail
span Trending Videos	1.16:1	4.5:1	#000000	#161616	Fail
span Most Popular	1.16:1	4.5:1	#000000	#161616	Fail
span Most Liked	1.16:1	4.5:1	#000000	#161616	Fail
span Movies	1.16:1	4.5:1	#000000	#161616	Fail
span Studios	1.16:1	4.5:1	#000000	#161616	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

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Hierarchy

8 headings

PASS

8 headings

Single H1 present

H1 new bang! originals
H2 Hottest Porn Videos - 4K
H2 Top Movies
H2 Hottest Movies
H3 original series
H3 Hottest Pornstars
H3 Top Channels
H3 Porn Categories

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 129 images OK

PASS

All 129 images OK

2 image(s) with alt text over 125 characters

127 image(s) with good alt text

129 images 127 good alt text

Issue	Count
too long	2 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A

Link & Button Quality

210 links, 5 buttons — all OK

PASS

210 links, 5 buttons — all OK

25 link(s) open in new tab without warning

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

Got: https://www.bangswag.com/; https://store.bang.com/; https://affiliates.bang.com/; https://blog.bang.com/models/; https://x.com/bang_twts; https://www.instagram.com/bang_network/; https://www.reddit.com/r/BangOfficial/; https://www.youtube.com/c/BangBTS; https://www.tiktok.com/@bangbehindthescenes; https://blog.bang.com (+15 more)

185 link(s) with descriptive text

210 links

0 empty

0 generic text

25 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.bangswag.com/	Swag	new tab	Add '(opens in new tab)' to text
https://store.bang.com/	Store	new tab	Add '(opens in new tab)' to text
https://affiliates.bang.com/	Affiliates	new tab	Add '(opens in new tab)' to text
https://blog.bang.com/models/	Models	new tab	Add '(opens in new tab)' to text
https://x.com/bang_twts	X	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/bang_network/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.reddit.com/r/BangOfficial/	Reddit	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/c/BangBTS	Youtube	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@bangbehindthesce…	TikTok	new tab	Add '(opens in new tab)' to text
https://blog.bang.com	Blog	new tab	Add '(opens in new tab)' to text
https://www.bangswag.com/	Swag	new tab	Add '(opens in new tab)' to text
https://affiliates.bang.com	Affiliates	new tab	Add '(opens in new tab)' to text
https://blog.bang.com/models/	Models	new tab	Add '(opens in new tab)' to text
https://store.bang.com/	Store	new tab	Add '(opens in new tab)' to text
https://segpaycs.com/	SegPay US	new tab	Add '(opens in new tab)' to text
https://epoch.com	Epoch	new tab	Add '(opens in new tab)' to text
https://www.echst.net	ECHST	new tab	Add '(opens in new tab)' to text
https://secure.vend-o.com/customers	Vendo	new tab	Add '(opens in new tab)' to text
https://segpaycs.com/	SegPay EU	new tab	Add '(opens in new tab)' to text
/terms-of-service	Terms of Service	new tab	Add '(opens in new tab)' to text
/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
/digital-services-act	EU DSA	new tab	Add '(opens in new tab)' to text
/report	Report Abuse, Content, Complai…	new tab	Add '(opens in new tab)' to text
/anti-trafficking	Anti Trafficking	new tab	Add '(opens in new tab)' to text
https://www.rtalabel.org	RTA label	new tab	Add '(opens in new tab)' to text

190 links and buttons have descriptive text

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

https://www.bangswag.com/; https://store.bang.com/; https://affiliates.bang.com/; https://blog.bang.com/models/; https://x.com/bang_twts; https://www.instagram.com/bang_network/; https://www.reddit.com/r/BangOfficial/; https://www.youtube.com/c/BangBTS; https://www.tiktok.com/@bangbehindthescenes; https://blog.bang.com (+15 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

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

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+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

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

PASS

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

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

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 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).

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

A+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 23 passed

PASS

96

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
DOWNLOAD `section.justify-items-center > div.xs:w-full > div.grid > span.w-max`
ULTRA HD 4K `section.justify-items-center > div.xs:w-full > div.grid > span.w-max`
161,000+ `section.justify-items-center > div.xs:w-full > div.grid > span.w-max`
EXCLUSIVE `section.justify-items-center > div.xs:w-full > div.grid > span.w-max`

These are opportunities to improve the legibility of your content.

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
support@bang.com `footer#footer > section.relative > p.text-xs > a.text-card-foreground`

○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

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

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

●Links have a discernible name

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

●Touch targets have sufficient size and spacing.

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

○Form elements have associated labels

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

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

○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

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