Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 12 -1-on-focusable

FIX

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

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

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

16 landmarks

REVIEW

16 landmarks

<main> landmark present

4 <nav> landmark(s) found

2 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

B

Heading Hierarchy

95 headings, 1 skip(s)

REVIEW

95 headings, 1 skip(s)

Multiple H1 headings (4 found)

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

Heading level skipped: H2 → H4 (missing H3)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 Poste.it
H3 Il mondo Poste
H3 In evidenza
H4 Area personale MyPoste
H2 Posta e pacchi
H3 Posta
H3 Pacchi
H3 Servizi in evidenza
H3 Avvisi
H2 Conti e invio denaro
H3 Conti
H3 Invio denaro
H3 Servizi in evidenza
H4 Accedi al conto
H2 Carte
H3 Carte
H3 Gestione carte
H3 Servizi in evidenza
H2 Finanziamenti
H3 Prodotti
H4 Simula la rata
H2 Risparmio Postale
H3 Buoni e Libretti
H4 L'offerta online a confronto
H2 Investimenti
H3 Investimento assicurativo
H3 Fondi comuni d'investimento
H3 Risparmio amministrato
H3 Gestioni patrimoniali
H3 Servizi in evidenza
H4 Accedi alla tua Area Personale
H2 Assicurazioni e previdenza
H4 Simula la tua protezione skipped
H3 Protezione
H3 Previdenza
H3 Protezione finanziamenti
H3 Servizi in evidenza
H2 Energia
H3 Luce e Gas
H3 Servizi in evidenza
H2 Telefonia
H3 Casa
H3 Mobile
H4 Ricarica online
H2 Filatelia
H3 Filatelia
H2 Servizi al cittadino e SPID
H3 Servizi della PA per il Progetto Polis
H3 Servizi digitali certificati
H3 Altri servizi al cittadino
H4 App PosteID
H2 Business
H2 I nostri siti
H2 Business
H2 User Test
H2 Bacheca
H2 (empty)
H2 Ciao,
H3 Come posso creare un account su poste.it?
H3 Ho dimenticato le credenziali del mio account Poste. Cosa posso fare?
H1 Deposito Supersmart Premium
H1 Poste Vivere Protetti duplicate H1
H1 Personalizzare le consegne, come vuoi tu duplicate H1
H1 BancoPosta Universo Tematico duplicate H1
H2 Cerca spedizioni
H2 Cerca un ufficio e prenota
H2 Servizi in evidenza
H2 Cerca spedizioni
H2 Cerca un ufficio e prenota
H2 Offerte e promozioni
H3 Quinto BancoPosta
H3 Oltre 1 milione di contratti
H3 Poste Progetto Obbligazionario IV
H3 PosteMobile è Extra Wow
H3 Non è solo un’app.
H3 PosteMobile Back 200
H3 Poste Italiane per tutte le persone
H3 Le truffe aumentano. Non abbassare la guardia.
H3 Il risparmio che fa scuola
H3 Poste Italiane per tutte le persone
H3 Le truffe aumentano. Non abbassare la guardia.
H3 Il risparmio che fa scuola
H2 News
H3 Poste Italiane: avviso di convocazione dell’Assemblea Ordinaria del 18 giugno 2026 e relazione illustrativa sull’unico argomento posto all’ordine del giorno
H3 Poste Italiane: Risultati finanziari del primo trimestre 2026
H3 Poste Italiane: il passaporto si può richiedere in circa 7.500 Uffici Postali in Italia
H2 Footer Poste Italiane
H3 Area personale
H3 Assistenza
H3 Canali
H3 Normative
H3 Aggiornamenti operativi
H3 L'azienda
H3 Accessibilità
H3 Altri siti

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

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Torna in cima ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

B

Favicon & Branding

21 icon(s) detected

REVIEW

21 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: Poste.it

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name Poste.it ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name Poste.it Display Mode standalone Icons 2 icon(s)

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: - H3: 156 chars

Got: 1 >120-char heading(s)

A+

Alt Text Quality

All 34 images OK

PASS

All 34 images OK

1 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

32 image(s) with good alt text

34 images 32 good alt text 1 decorative

Issue	Count
too long	1 image(s)

A

Form Accessibility

1 of 4 controls have issues

PASS

1 of 4 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="checkbox">

3 control(s) properly labeled

4 controls

3 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#inline-checkbox-select-all	checkbox	Seleziona tutti	for/id
#input-servizio-cerca	text	Inserisci codice spedizione	for/id
#input-servizio-cerca-xs	text	Inserisci codice spedizione	for/id
input	checkbox	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A

Link & Button Quality

284 links, 56 buttons — all OK

PASS

284 links, 56 buttons — all OK

17 link(s) open in new tab without warning

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

Got: https://www.poste.it/cookie-policy.html; https://www.saronweb.it/posteprotezione/ricercastrutturemap; https://www.facebook.com/PosteItaliane; https://twitter.com/posteitaliane; https://it.linkedin.com/company/poste-italiane; https://www.instagram.com/posteitaliane/; https://www.youtube.com/user/POSTEITALIANE; https://www.poste.it/posteaircargo; https://www.postel.it/; https://www.sda.it/wps/portal/sdait.home/ (+7 more)

267 link(s) with descriptive text

284 links

0 empty

0 generic text

17 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.poste.it/cookie-policy.html	cookie policy	new tab	Add '(opens in new tab)' to text
https://www.saronweb.it/posteprotezione/…	Network Salute	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/PosteItaliane	Facebook …	new tab	Add '(opens in new tab)' to text
https://twitter.com/posteitaliane	Twitter …	new tab	Add '(opens in new tab)' to text
https://it.linkedin.com/company/poste-it…	Linkedin …	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/posteitaliane/	Instagram …	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/POSTEITALIA…	Youtube …	new tab	Add '(opens in new tab)' to text
https://www.poste.it/posteaircargo	Poste Air Cargo	new tab	Add '(opens in new tab)' to text
https://www.postel.it/	Postel	new tab	Add '(opens in new tab)' to text
https://www.sda.it/wps/portal/sdait.home…	SDA	new tab	Add '(opens in new tab)' to text
https://www.poste.it/nexive-network	Nexive Network	new tab	Add '(opens in new tab)' to text
https://www.poste.it/postevita-fondo-sal…	PosteVita Fondosalute	new tab	Add '(opens in new tab)' to text
https://www.poste.it/posteaircargo	Poste Air Cargo	new tab	Add '(opens in new tab)' to text
https://www.postel.it/	Postel	new tab	Add '(opens in new tab)' to text
https://www.sda.it/wps/portal/sdait.home…	SDA	new tab	Add '(opens in new tab)' to text
https://www.poste.it/nexive-network	Nexive Network	new tab	Add '(opens in new tab)' to text
https://www.poste.it/postevita-fondo-sal…	PosteVita Fondosalute	new tab	Add '(opens in new tab)' to text

323 links and buttons have descriptive text

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

https://www.poste.it/cookie-policy.html; https://www.saronweb.it/posteprotezione/ricercastrutturemap; https://www.facebook.com/PosteItaliane; https://twitter.com/posteitaliane; https://it.linkedin.com/company/poste-italiane; https://www.instagram.com/posteitaliane/; https://www.youtube.com/user/POSTEITALIANE; https://www.poste.it/posteaircargo; https://www.postel.it/; https://www.sda.it/wps/portal/sdait.home/ (+7 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

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

PASS

Lang attribute set to "it"

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

Got: it

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

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 11 visible text node(s) render at >= 12 CSS pixels

PASS

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

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

A

PWA Depth

2 PWA signal(s) surfaced

PASS

2 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

Manifest is missing `theme_color`

Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

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.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Deposito Supersmart …	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h1 Poste Vivere Protett…	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h1 Personalizzare le co…	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h1 BancoPosta Universo …	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Poste.it	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Posta e pacchi	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Conti e invio denaro	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Carte	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Finanziamenti	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Risparmio Postale	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Investimenti	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Assicurazioni e prev…	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Energia	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Telefonia	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Filatelia	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Servizi al cittadino…	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Business	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 I nostri siti	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 Business	9.68:1	3.0:1	#000000	#B0B0B0	Pass
h2 User Test	9.68:1	3.0:1	#000000	#B0B0B0	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+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 32 passed

PASS

97

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Poste Italiane dà valore alla tua privacy Questo sito web utilizza cookie tecn… `body#homepage > div.content-alert-browser > div#consent_blackbar > div#truste-consent-track`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Privati `div.col-sm-12 > div.content-fedbar-wrap > div#business-button-open-sm > button.offcanvas-toggle`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]`s are contained by their required parent element

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●`button`, `link`, and `menuitem` elements have accessible names

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

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

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

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

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

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

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

○All heading elements contain content.

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

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