Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 19 -1-on-focusable

FIX

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

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

No dark mode signals

FIX

No dark mode signals

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 ModeNo Dark Mode Detected

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

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

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 3 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

B

Landmark Structure

7 landmarks

REVIEW

7 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

No banner (header) landmark

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

C

Link & Button Quality

Action

14 issue(s) across 103 links and 5 buttons

REVIEW

14 issue(s) across 103 links and 5 buttons

14 link(s) with no accessible text

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

Got: https://www.fabioantichi.it/tnews-del-web-marketing-6-novembre/; https://www.fabioantichi.it/news-marketing-3-novembre/; https://www.fabioantichi.it/news-marketing-30-ottobre/; https://www.fabioantichi.it/mews-marketing-28-ottobre/; https://www.fabioantichi.it/12221-2/; https://www.fabioantichi.it/news-marketing-26-ottobre/; https://www.fabioantichi.it/news-marketing-21-ottobre/; https://www.fabioantichi.it/come-posizionarsi-nellintelligenza-artificiale-st…; https://www.fabioantichi.it/news-marketing-12-ottobre/; https://www.fabioantichi.it/news-marketing-7-ottobre-%f0%9f%a4%aa/ (+4 more)

5 link(s) open in new tab without warning

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

Got: https://wa.me/393391531121?text=Ciao%20Fabio%21%20Vorrei%20parlarti%20di%20un…; https://wa.me/393391531121?text=Ciao%20Fabio%21%20Vorrei%20parlarti%20di%20un…; https://www.otellino.it/; https://www.omarattia.it; https://www.iubenda.com/privacy-policy/83856991/cookie-policy?an=no&s_ck=fals…

84 link(s) with descriptive text

103 links

14 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.fabioantichi.it/tnews-del-we…	(empty)	empty	Add link text or aria-label
https://www.fabioantichi.it/news-marketi…	(empty)	empty	Add link text or aria-label
https://www.fabioantichi.it/news-marketi…	(empty)	empty	Add link text or aria-label
https://www.fabioantichi.it/mews-marketi…	(empty)	empty	Add link text or aria-label
https://www.fabioantichi.it/12221-2/	(empty)	empty	Add link text or aria-label
https://www.fabioantichi.it/news-marketi…	(empty)	empty	Add link text or aria-label
https://www.fabioantichi.it/news-marketi…	(empty)	empty	Add link text or aria-label
https://www.fabioantichi.it/come-posizio…	(empty)	empty	Add link text or aria-label
https://www.fabioantichi.it/news-marketi…	(empty)	empty	Add link text or aria-label
https://www.fabioantichi.it/news-marketi…	(empty)	empty	Add link text or aria-label
https://www.fabioantichi.it/news-marketi…	(empty)	empty	Add link text or aria-label
https://www.fabioantichi.it/news-marketi…	(empty)	empty	Add link text or aria-label
https://www.fabioantichi.it/news-marketi…	(empty)	empty	Add link text or aria-label
https://wa.me/393391531121?text=Ciao%20F…	Scrivimi su WhatsApp →	new tab	Add '(opens in new tab)' to text
https://wa.me/393391531121?text=Ciao%20F…	WhatsApp	new tab	Add '(opens in new tab)' to text
https://www.otellino.it/	Otellino	new tab	Add '(opens in new tab)' to text
https://www.omarattia.it	Omar Attia	new tab	Add '(opens in new tab)' to text
https://www.iubenda.com/privacy-policy/8…	cookie policy	new tab	Add '(opens in new tab)' to text
https://aladinia.app/t/h	(empty)	empty	Add link text or aria-label

89 links and buttons have descriptive text

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

https://www.fabioantichi.it/tnews-del-web-marketing-6-novembre/; https://www.fabioantichi.it/news-marketing-3-novembre/; https://www.fabioantichi.it/news-marketing-30-ottobre/; https://www.fabioantichi.it/mews-marketing-28-ottobre/; https://www.fabioantichi.it/12221-2/; https://www.fabioantichi.it/news-marketing-26-ottobre/; https://www.fabioantichi.it/news-marketing-21-ottobre/; https://www.fabioantichi.it/come-posizionarsi-nellintelligenza-artificiale-st…; https://www.fabioantichi.it/news-marketing-12-ottobre/; https://www.fabioantichi.it/news-marketing-7-ottobre-%f0%9f%a4%aa/ (+4 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://wa.me/393391531121?text=Ciao%20Fabio%21%20Vorrei%20parlarti%20di%20un…; https://wa.me/393391531121?text=Ciao%20Fabio%21%20Vorrei%20parlarti%20di%20un…; https://www.otellino.it/; https://www.omarattia.it; https://www.iubenda.com/privacy-policy/83856991/cookie-policy?an=no&s_ck=fals…

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

C

Mobile-Readable Font Sizes

Action

86% of visible text renders at >= 12 CSS px (20 below threshold)

REVIEW

86% of visible text renders at >= 12 CSS px (20 below threshold)

20 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: <small> 10.0px ("Fabio Antichi"); <small> 10.0px ("Scalare online nell'era dell'AI"); <span> 11.0px ("News · 6 Nov 2026"); <span> 11.0px ("News · 3 Nov 2026"); <span> 11.0px ("News · 30 Ott 2026").

B

Favicon & Branding

4 icon(s) detected

REVIEW

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

✓ Multiple Sizes Present

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 6 fail WCAG AA

REVIEW

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

14 pass 6 fail WCAG AA

h1 SEO, GEO, Google Ads e

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

32px · mid-page

h2 Cosa faccio,

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Le ultime

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Senza impegno.

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Informativa

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Nasci, Cresci, Fattura.

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 SEO, GEO, Google Ads…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Cosa faccio,	1.00:1	3.0:1	#000000	#000000	Fail
h2 Le ultime	1.00:1	3.0:1	#000000	#000000	Fail
h2 Senza impegno.	1.00:1	3.0:1	#000000	#000000	Fail
h2 Informativa	1.00:1	3.0:1	#000000	#000000	Fail
h3 Nasci, Cresci, Fattu…	1.00:1	3.0:1	#000000	#000000	Fail
title Fabio Antichi - Cons…	19.69:1	4.5:1	#000000	#FAF7F5	Pass
a Vai al contenuto	19.69:1	4.5:1	#000000	#FAF7F5	Pass
a Chi sono	19.19:1	4.5:1	#000000	#F4F5F2	Pass
a Consulenze	19.00:1	4.5:1	#000000	#F2F4F2	Pass
a Corsi	18.80:1	4.5:1	#000000	#F0F3F1	Pass
a Il libro	18.56:1	4.5:1	#000000	#EDF2F0	Pass
a News	18.37:1	4.5:1	#000000	#EBF1F0	Pass
a Newsletter	18.18:1	4.5:1	#000000	#E9F0EF	Pass
a Parliamone	17.99:1	4.5:1	#000000	#E7EFEF	Pass
span →	17.76:1	4.5:1	#000000	#E4EEEE	Pass
summary Menu	17.58:1	4.5:1	#000000	#E2EDEE	Pass
a Chi sono	17.39:1	4.5:1	#000000	#E0ECED	Pass
a Consulenze	17.24:1	4.5:1	#000000	#DFEBED	Pass
a Corsi	17.20:1	4.5:1	#000000	#DEEBEC	Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A

Heading Hierarchy

27 headings, 1 skip(s)

PASS

27 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

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

H1 Fabio Antichi: SEO, GEO, Google Ads e ChatGPT Ads.
H2 Cosa faccio, in pratica.
H3 Nasci, Cresci, Fattura.
H2 Le ultime news.
H3 News del Web Marketing 6 Novembre
H3 News Marketing 3 Novembre
H3 News Marketing 30 ottobre
H3 Mews Marketing 28 Ottobre
H3 News Marketing 27 Ottobre
H3 News Marketing 26 Ottobre
H3 News Marketing 23 ottobre
H3 News Marketing 21 ottobre
H3 Come posizionarsi nell’intelligenza artificiale: storia, evoluzione e tecniche GEO
H3 Eventi e Iterventi con Fabio Antichi
H3 Chi è Fabio Antichi
H3 News Marketing 19 ottobre
H3 Ecco le 10 news di marketing del 16 ottobre 2026 che devi sapere
H3 News Marketing 12 ottobre
H3 News Marketing 7 ottobre
H3 News Marketing 2 ottobre
H3 News Marketing 30 settembre
H3 News Marketing 23 settembre
H2 Parliamone. Senza impegno.
H5 Esplora skipped
H5 Contatti
H5 Altro
H2 Informativa

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 27 heading(s) have substantive, well-formed text

PASS

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

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

A+

Alt Text Quality

All 23 images OK

PASS

All 23 images OK

13 decorative image(s) correctly marked

10 image(s) with good alt text

23 images 10 good alt text 13 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#s-home	search	Cerca un articolo	for/id

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

1 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 "it-IT"

PASS

Lang attribute set to "it-IT"

<html lang="it-IT"> is set and valid

Got: it-IT

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 Page Not Found - Fabio Antichi Google ADS Adwords & SEO Consulenze e Corsi ✓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

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.

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 27 passed

PASS

95

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
IL LIBRO · BESTSELLER AMAZON `div.wrap > div.book > div > span.eyebrow`

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
ESPLORA `div.wrap > div.footer-grid > div > h5`

These are opportunities to improve keyboard navigation in your application.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Skip links are focusable.

●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

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

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