Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 17 -1-on-focusable

FIX

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

D

Mobile-Readable Font Sizes

Action

28% of visible text renders at >= 12 CSS px (368 below threshold)

FIX

28% of visible text renders at >= 12 CSS px (368 below threshold)

368 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.0px ("Offerta prima di tutto"); <span> 10.0px ("Un solo sistema di ricavi"); <span> 10.0px ("Risultati, non metriche di facciata"); <span> 10.0px ("AYVION"); <span> 10.0px ("/ CENTRO DI CONTROLLO RICAVI").

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ 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: #070806

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

No navigation patterns

FIX

No navigation patterns

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

Landmark Structure

7 landmarks

REVIEW

7 landmarks

<main> landmark present

4 <nav> landmark(s) found

1 of 4 <nav> elements are unlabeled

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

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

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

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title AYVION — Il tuo reparto Marketing & Vendite esterno ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

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

h2 La tua agenzia festeggia il CPL.

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Non ti serve qualcuno che ottimizzi un a…

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Dal primo euro investito all’ultimo eu…

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Puoi migliorare le campagne

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Non vendiamo strumenti.

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Il problema non è avere più specialist…

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Il principio non cambia.

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AYVION non è per tutti.

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Il problema potrebbe non essere generare…

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Prima di comprare attenzione, costruiamo…

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Un lead non è un risultato. È l'inizio…

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Puoi abbassare il CPL e contemporaneamen…

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Prima delle campagne viene il business.

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Se l'offerta regge ma non genera abbasta…

1.04:1

#000000

on

#060705

needs 3.0:1 (large text)

19px · bottom of viewport

title AYVION | Reparto Marketing & Vendite Est…

1.04:1

#000000

on

#060705

needs 4.5:1 (normal text)

16px · top of page (header area)

span Metodo AYVION

1.04:1

#000000

on

#060705

needs 4.5:1 (normal text)

16px · top of page (header area)

span Per chi lavoriamo

1.04:1

#000000

on

#060705

needs 4.5:1 (normal text)

16px · top of page (header area)

span ▾

1.04:1

#000000

on

#060705

needs 4.5:1 (normal text)

16px · top of page (header area)

a Professionisti & Studi

1.04:1

#000000

on

#060705

needs 4.5:1 (normal text)

16px · above the fold

a PMI & Aziende Locali

1.04:1

#000000

on

#060705

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 La tua agenzia feste…	1.04:1	3.0:1	#000000	#060705	Fail
h2 Non ti serve qualcun…	1.04:1	3.0:1	#000000	#060705	Fail
h2 Dal primo euro inves…	1.04:1	3.0:1	#000000	#060705	Fail
h2 Puoi migliorare le c…	1.04:1	3.0:1	#000000	#060705	Fail
h2 Non vendiamo strumen…	1.04:1	3.0:1	#000000	#060705	Fail
h2 Il problema non è a…	1.04:1	3.0:1	#000000	#060705	Fail
h2 Il principio non cam…	1.04:1	3.0:1	#000000	#060705	Fail
h2 AYVION non è per tu…	1.04:1	3.0:1	#000000	#060705	Fail
h2 Il problema potrebbe…	1.04:1	3.0:1	#000000	#060705	Fail
h3 Prima di comprare at…	1.04:1	3.0:1	#000000	#060705	Fail
h3 Un lead non è un ri…	1.04:1	3.0:1	#000000	#060705	Fail
h3 Puoi abbassare il CP…	1.04:1	3.0:1	#000000	#060705	Fail
h3 Prima delle campagne…	1.04:1	3.0:1	#000000	#060705	Fail
h3 Se l'offerta regge m…	1.04:1	3.0:1	#000000	#060705	Fail
title AYVION \| Reparto Mar…	1.04:1	4.5:1	#000000	#060705	Fail
span Metodo AYVION	1.04:1	4.5:1	#000000	#060705	Fail
span Per chi lavoriamo	1.04:1	4.5:1	#000000	#060705	Fail
span ▾	1.04:1	4.5:1	#000000	#060705	Fail
a Professionisti & Stu…	1.04:1	4.5:1	#000000	#060705	Fail
a PMI & Aziende Locali	1.04:1	4.5:1	#000000	#060705	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+

Heading Hierarchy

15 headings

PASS

15 headings

Single H1 present

H1 Il marketing non inizia dalle campagne.Inizia dall’offerta.
H2 La tua agenzia festeggia il CPL. Il tuo commerciale dice che i lead non comprano.
H2 Non ti serve qualcuno che ottimizzi un altro pezzo.Ti serve qualcuno che guardi cosa succede dall'offerta fino all'incasso.
H3 Prima di comprare attenzione, costruiamo qualcosa che meriti attenzione.
H3 Un lead non è un risultato. È l'inizio del processo commerciale.
H3 Puoi abbassare il CPL e contemporaneamente aumentare il costo di ogni nuovo cliente.
H2 Dal primo euro investito all’ultimo euro incassato.Una sola regia.
H3 Prima delle campagne viene il business.
H2 Puoi migliorare le campagnee peggiorare il business.
H2 Non vendiamo strumenti.Interveniamo dove il sistema perde soldi.
H3 Se l'offerta regge ma non genera abbastanza opportunità, interveniamo qui.
H2 Il problema non è avere più specialisti.È avere più specialisti che ottimizzano obiettivi diversi.
H2 Il principio non cambia.Cambia la complessità della macchina.
H2 AYVION non è per tutti.E va bene così.
H2 Il problema potrebbe non essere generare più lead. Potrebbe essere tutto quello che succede prima e dopo.

A

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 123 chars

Got: 1 >120-char heading(s)

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

44 links, 4 buttons — all OK

PASS

44 links, 4 buttons — all OK

44 link(s) with descriptive text

44 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

48 links and buttons have descriptive text

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

PASS

Lang attribute set to "it"

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

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

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 96/100 — 1 failing, 24 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
UPDATED 09:41 · ILLUSTRATIVE DATA `div.relative > div.ayv-panel > div.flex > span.ml-auto`
ACTIVITY `div.relative > div.ayv-panel > div.flex > span.font-[var(--font-mono)]`
DEMO `div.relative > div.ayv-panel > div.flex > span.shrink-0`
01 · STRATEGY & OFFER `div.lg:col-span-5 > div.relative > div.relative > span.font-[var(--font-mono)]`
03 · SALES SYSTEM & CRM `div.lg:col-span-5 > div.relative > div.relative > span.font-[var(--font-mono)]`
SCENARIO 02 `div.lg:col-span-7 > div.ayv-panel > div.mt-8 > span.font-[var(--font-mono)]`
SCENARIO 03 `div.lg:col-span-7 > div.ayv-panel > div.mt-8 > span.font-[var(--font-mono)]`
ILLUSTRATIVE SCENARIO `div.mt-10 > div.border > div.border-t > span.font-[var(--font-mono)]`
ILLUSTRATIVE SCENARIO `div.mt-10 > div.border > div.border-t > span.font-[var(--font-mono)]`
no opportunity lost `div.border > div.grid > div.ayv-hoverline > p.mt-1`
PIPELINE `div.grid > div.ayv-hoverline > div.flex > span.truncate`
status of every opportunity `div.border > div.grid > div.ayv-hoverline > p.mt-1`
FOLLOW-UP `div.grid > div.ayv-hoverline > div.flex > span.truncate`
response speed `div.border > div.grid > div.ayv-hoverline > p.mt-1`
SALESPEOPLE `div.grid > div.ayv-hoverline > div.flex > span.truncate`
shared process `div.border > div.grid > div.ayv-hoverline > p.mt-1`
TEAM `div.grid > div.ayv-hoverline > div.flex > span.truncate`
performance by person `div.border > div.grid > div.ayv-hoverline > p.mt-1`
TERRITORIES `div.grid > div.ayv-hoverline > div.flex > span.truncate`
coverage and priorities `div.border > div.grid > div.ayv-hoverline > p.mt-1`
CHANNELS `div.grid > div.ayv-hoverline > div.flex > span.truncate`
acquisition mix `div.border > div.grid > div.ayv-hoverline > p.mt-1`
FORECAST `div.grid > div.ayv-hoverline > div.flex > span.truncate`
forecast revenue `div.border > div.grid > div.ayv-hoverline > p.mt-1`
LEADERSHIP `div.grid > div.ayv-hoverline > div.flex > span.truncate`
one direction `div.border > div.grid > div.ayv-hoverline > p.mt-1`
ECONOMICS `div.grid > div.ayv-hoverline > div.flex > span.truncate`
CAC · margin · revenue `div.border > div.grid > div.ayv-hoverline > p.mt-1`
AYVION LOGIC UNCHANGED `div.mt-5 > div.border > div.flex > span.font-[var(--font-mono)]`
TEAM `div.grid > div.ayv-hoverline > div.flex > span.truncate`
performance by person `div.border > div.grid > div.ayv-hoverline > p.mt-1`
TERRITORIES `div.grid > div.ayv-hoverline > div.flex > span.truncate`
coverage and priorities `div.border > div.grid > div.ayv-hoverline > p.mt-1`
CHANNELS `div.grid > div.ayv-hoverline > div.flex > span.truncate`
acquisition mix `div.border > div.grid > div.ayv-hoverline > p.mt-1`
FORECAST `div.grid > div.ayv-hoverline > div.flex > span.truncate`
forecast revenue `div.border > div.grid > div.ayv-hoverline > p.mt-1`
LEADERSHIP `div.grid > div.ayv-hoverline > div.flex > span.truncate`
one direction `div.border > div.grid > div.ayv-hoverline > p.mt-1`
ECONOMICS `div.grid > div.ayv-hoverline > div.flex > span.truncate`
CAC · margin · revenue `div.border > div.grid > div.ayv-hoverline > p.mt-1`
AYVION LOGIC UNCHANGED `div.mt-5 > div.border > div.flex > span.font-[var(--font-mono)]`
AYVION LOGIC UNCHANGED `div.mt-5 > div.border > div.flex > span.font-[var(--font-mono)]`
EMAIL `div.md:border-l > ul.mt-6 > li > span.block`
OFFER. ACQUISITION. SALES. ONE DIRECTION. `div.ayv-container > div.flex > div.flex > span.font-[var(--font-mono)]`

These are opportunities to improve the legibility of your content.

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

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

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

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

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

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.