Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 13 -1-on-focusable

FIX

0 positive, 13 -1-on-focusable

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

No apple-touch-icon detected

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

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #669bbb

No dark mode signals detected

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

Detection limited to meta tags and inline styles

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

Dark ModePartial Dark Mode

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

Detection limited to meta tags and inline styles.

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

3 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 3 <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.

C

Alt Text Quality

Action

5 of 34 images have issues

REVIEW

5 of 34 images have issues

5 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 decorative image(s) correctly marked

27 image(s) with good alt text

34 images 27 good alt text 2 decorative 5 missing

Issue	Count
missing	5 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B

Mobile-Readable Font Sizes

90% of visible text renders at >= 12 CSS px (11 below threshold)

REVIEW

90% of visible text renders at >= 12 CSS px (11 below threshold)

11 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.5px ("Flying Bird Toy"); <span> 10.5px ("Verified Buyer"); <span> 10.5px ("Luxury Plush Shark Bed"); <span> 10.5px ("Verified Buyer"); <span> 10.5px ("Interactive Cat Laser Collar").

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA 2 pass AA only

h2 Cookie consent

2.13:1

#000000

on

#39454D

needs 3.0:1 (large text)

24px · top of page (header area)

title Adjustable Pet Harness Leash Set – Top…

1.90:1

#000000

on

#2E3E48

needs 4.5:1 (normal text)

16px · top of page (header area)

p We and our partners, including Shopify, …

3.14:1

#000000

on

#5C5C5C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Privacy Policy

3.14:1

#000000

on

#5C5C5C

needs 4.5:1 (normal text)

16px · top of page (header area)

span Manage preferences

3.14:1

#000000

on

#5C5C5C

needs 4.5:1 (normal text)

16px · above the fold

button Accept

3.14:1

#000000

on

#5C5C5C

needs 4.5:1 (normal text)

16px · above the fold

button Decline

3.14:1

#000000

on

#5C5C5C

needs 4.5:1 (normal text)

16px · above the fold

a Skip to content

3.14:1

#000000

on

#5C5C5C

needs 4.5:1 (normal text)

16px · above the fold

em Big Deals + Fast Delivery!

3.14:1

#000000

on

#5C5C5C

needs 4.5:1 (normal text)

16px · above the fold

em Big Deals + Fast Delivery!

3.14:1

#000000

on

#5C5C5C

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Cookie consent	2.13:1	3.0:1	#000000	#39454D	Fail
h2 Your cart is current…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Sign up and get	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 your first order	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 What Pet Parents Are…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Checkout securely wi…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Overview	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Specifications	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Packing List	16.98:1	3.0:1	#000000	#E7E7E7	Pass
title Adjustable Pet Harne…	1.90:1	4.5:1	#000000	#2E3E48	Fail
p We and our partners,…	3.14:1	4.5:1	#000000	#5C5C5C	Fail
a Privacy Policy	3.14:1	4.5:1	#000000	#5C5C5C	Fail
span Manage preferences	3.14:1	4.5:1	#000000	#5C5C5C	Fail
button Accept	3.14:1	4.5:1	#000000	#5C5C5C	Fail
button Decline	3.14:1	4.5:1	#000000	#5C5C5C	Fail
a Skip to content	3.14:1	4.5:1	#000000	#5C5C5C	Fail
strong Spoil Your Pets Toda…	3.14:1	3.0:1	#000000	#5C5C5C	Pass
em Big Deals + Fast Del…	3.14:1	4.5:1	#000000	#5C5C5C	Fail
strong Spoil Your Pets Toda…	3.14:1	3.0:1	#000000	#5C5C5C	Pass
em Big Deals + Fast Del…	3.14:1	4.5:1	#000000	#5C5C5C	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

7 landmarks

PASS

7 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A

Heading Hierarchy

10 headings, 1 skip(s)

PASS

10 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H2 Cookie consent
H2 Your cart is currently empty.
H2 Sign up and get 15% off your first order
H2 This site uses cookies
H1 Adjustable Pet Harness Leash Set
H3 Checkout securely with skipped
H3 Overview
H3 Specifications
H3 Packing List
H2 What Pet Parents Are Saying

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

A+

Heading Text Quality

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

PASS

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

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

A+

Form Accessibility

All 11 controls labeled

PASS

All 11 controls labeled

11 control(s) properly labeled

11 controls

11 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#CartNoteForm-sections--22557635182809__cart-drawer	textarea	Order note	for/id
#CartDiscountForm-sections--22557635182809__cart-drawer	text	Discount code	for/id
#SearchFormInput-sections--22557635182809__search-drawer	search	Search	for/id
#NewsletterForm--sections--22557635182809__newsletter-popup	email	Enter your email	for/id
#template--22557634953433__main-product-9831590232281-color-0	radio	Off-whiteOff-white	for/id
#template--22557634953433__main-product-9831590232281-color-1	radio	Dark greenDark green	for/id
#template--22557634953433__main-product-9831590232281-color-2	radio	BlackBlack	for/id
#template--22557634953433__main-product-9831590232281-specifications-0	radio	S	for/id
#template--22557634953433__main-product-9831590232281-specifications-1	radio	M	for/id
#template--22557634953433__main-product-9831590232281-specifications-2	radio	L	for/id
#Quantity-template--22557634953433__main-product-9831590232281	number	Quantity	for/id

A

Link & Button Quality

51 links, 60 buttons — all OK

PASS

51 links, 60 buttons — all OK

12 link(s) open in new tab without warning

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

Got: https://toppetshop.com/policies/privacy-policy; //www.facebook.com/sharer.php?u=https://toppetshop.com/products/adjustable-pe…; //twitter.com/intent/tweet?text=Adjustable%20Pet%20Harness%20Leash%20Set&url=…; //telegram.me/share/url?url=https://toppetshop.com/products/adjustable-pet-ha…; //web.whatsapp.com/send?text=https://toppetshop.com/products/adjustable-pet-h…; mailto:?&subject=Adjustable%20Pet%20Harness%20Leash%20Set&body=https://toppet…; //www.facebook.com/sharer.php?u=https://toppetshop.com/products/adjustable-pe…; //twitter.com/intent/tweet?text=Adjustable%20Pet%20Harness%20Leash%20Set&url=…; //telegram.me/share/url?url=https://toppetshop.com/products/adjustable-pet-ha…; //web.whatsapp.com/send?text=https://toppetshop.com/products/adjustable-pet-h… (+2 more)

39 link(s) with descriptive text

51 links

0 empty

0 generic text

12 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://toppetshop.com/policies/privacy-…	Privacy Policy	new tab	Add '(opens in new tab)' to text
/	Top Pet Shop	img no alt	Add alt attribute to the image
//www.facebook.com/sharer.php?u=https://…	Share on Facebook	new tab	Add '(opens in new tab)' to text
//twitter.com/intent/tweet?text=Adjustab…	Share on X	new tab	Add '(opens in new tab)' to text
//telegram.me/share/url?url=https://topp…	Share on Telegram	new tab	Add '(opens in new tab)' to text
//web.whatsapp.com/send?text=https://top…	Share on WhatsApp	new tab	Add '(opens in new tab)' to text
mailto:?&subject=Adjustable%20Pet%20Harn…	Share by Email	new tab	Add '(opens in new tab)' to text
//www.facebook.com/sharer.php?u=https://…	Facebook Sha…	new tab	Add '(opens in new tab)' to text
//twitter.com/intent/tweet?text=Adjustab…	X (Twitter) …	new tab	Add '(opens in new tab)' to text
//telegram.me/share/url?url=https://topp…	Telegram Sha…	new tab	Add '(opens in new tab)' to text
//web.whatsapp.com/send?text=https://top…	WhatsApp Sha…	new tab	Add '(opens in new tab)' to text
mailto:?&subject=Adjustable%20Pet%20Harn…	E-mail Share…	new tab	Add '(opens in new tab)' to text
https://www.shopify.com?utm_campaign=pow…	.	new tab	Add '(opens in new tab)' to text

99 links and buttons have descriptive text

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

https://toppetshop.com/policies/privacy-policy; //www.facebook.com/sharer.php?u=https://toppetshop.com/products/adjustable-pe…; //twitter.com/intent/tweet?text=Adjustable%20Pet%20Harness%20Leash%20Set&url=…; //telegram.me/share/url?url=https://toppetshop.com/products/adjustable-pet-ha…; //web.whatsapp.com/send?text=https://toppetshop.com/products/adjustable-pet-h…; mailto:?&subject=Adjustable%20Pet%20Harness%20Leash%20Set&body=https://toppet…; //www.facebook.com/sharer.php?u=https://toppetshop.com/products/adjustable-pe…; //twitter.com/intent/tweet?text=Adjustable%20Pet%20Harness%20Leash%20Set&url=…; //telegram.me/share/url?url=https://toppetshop.com/products/adjustable-pet-ha…; //web.whatsapp.com/send?text=https://toppetshop.com/products/adjustable-pet-h… (+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

A+

Form Input Types

11 form control(s) checked, no type mismatches

PASS

11 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

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

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found – Top Pet Shop ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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 90/100 — 3 failing, 24 passed

PASS

90

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
REAL FEEDBACK `div.tps-wrap > div.tps-previews__head > div > span.tps-eyebrow`
VERIFIED BUYER `div.tps-previews__grid > div.tps-preview-card > div.tps-preview-card__foot > span.tps-preview-card__badge`
VERIFIED BUYER `div.tps-previews__grid > div.tps-preview-card > div.tps-preview-card__foot > span.tps-preview-card__badge`
VERIFIED BUYER `div.tps-previews__grid > div.tps-preview-card > div.tps-preview-card__foot > span.tps-preview-card__badge`
VERIFIED BUYER `div.tps-previews__grid > div.tps-preview-card > div.tps-preview-card__foot > span.tps-preview-card__badge`
VERIFIED BUYER `div.tps-previews__grid > div.tps-preview-card > div.tps-preview-card__foot > span.tps-preview-card__badge`
VERIFIED BUYER `div.tps-previews__grid > div.tps-preview-card > div.tps-preview-card__foot > span.tps-preview-card__badge`
VERIFIED BUYER `div.tps-previews__grid > div.tps-preview-card > div.tps-preview-card__foot > span.tps-preview-card__badge`
VERIFIED BUYER `div.tps-previews__grid > div.tps-preview-card > div.tps-preview-card__foot > span.tps-preview-card__badge`

These are opportunities to improve the legibility of your content.

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
Checkout securely with `div.trust-badge-6a667f4d2fd43-47226684-471785102157 > div.giraffly-right-Bar-Preview-Example > div.giraffly-right-Bar-Preview-width > h3`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
product-info#ProductInfo-template--22557634953433__main-product-9831590232281 > div.product__text > div > img `product-info#ProductInfo-template--22557634953433__main-product-9831590232281 > div.product__text > div > img`
product-info#ProductInfo-template--22557634953433__main-product-9831590232281 > div.product__text > div > img `product-info#ProductInfo-template--22557634953433__main-product-9831590232281 > div.product__text > div > img`
product-info#ProductInfo-template--22557634953433__main-product-9831590232281 > div.product__text > div > img `product-info#ProductInfo-template--22557634953433__main-product-9831590232281 > div.product__text > div > img`
product-info#ProductInfo-template--22557634953433__main-product-9831590232281 > div.product__text > div > img `product-info#ProductInfo-template--22557634953433__main-product-9831590232281 > div.product__text > div > img`
product-info#ProductInfo-template--22557634953433__main-product-9831590232281 > div.product__text > div > img `product-info#ProductInfo-template--22557634953433__main-product-9831590232281 > div.product__text > div > img`

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.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Form elements have associated labels

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

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

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

●Elements use only permitted ARIA attributes

●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

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

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

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