Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 6 REVIEW 4 FIX

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.

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 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

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

Action

16 landmarks

REVIEW

16 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

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

Page Structure — as a screen reader sees it

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Heading Hierarchy

56 headings, 1 skip(s)

REVIEW

56 headings, 1 skip(s)

Multiple H1 headings (2 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.

H1 Web Agency Roma
H2 L'eccellenza nella SEO e nel Web Marketing
H3 Perché affidarsi alla mia Web Agency?
H1 Ho pubblicato il mio libro che spiega come AI può lavorare con la SEO: Disponibile su Amazon duplicate H1
H2 Servizi Web Agency Roma
H3 Digital Off Site
H3 Content & Outreach
H3 SEO Tecnica
H3 Formazione
H3 Link Building
H3 Audit Avanzato
H3 Pay Per Click
H3 White Label
H2 Team Specializzato e Competente
H3 Profili del Team
H3 Formazione Continua e Certificazioni
H2 Sono presente in queste città per Consulenze
H3 Consulente SEO Roma
H3 Consulente SEO Milano
H3 Consulente SEO Napoli
H3 Consulente SEO Torino
H3 Consulente SEO Firenze
H2 Metodo SEO e Strumenti di Lavoro
H3 Tecnologie e Software Utilizzati
H3 Processi e Workflow Interni
H2 Monitoraggio e misurazione dei risultati ottenuti
H2 Cosa Faccio per Posizionare I Miei Clienti in Prima Pagina
H4 Analisi Sito Web: skipped
H4 Parole Chiave:
H4 Fattori On/Off-Page:
H4 Tendenze SEO:
H4 SEO Locale:
H4 Performance Sito:
H2 10 motivi per affidarti alla mia Web Agency
H2 Conclusioni
H2 Domande Frequenti - Web Agency
H3 Cosa fa una Web agency?
H3 Quanto costa affidarsi a una Web agency?
H3 Come scegliere la migliore Web agency per il mio business?
H3 Una Web agency può garantire la prima posizione su Google?
H3 SEO freelance o Web agency?
H3 Meglio una Web agency o un freelance?
H3 Quali servizi offre una Web agency per il digital marketing?
H3 Una Web agency può aiutare il mio e-commerce a vendere di più?
H3 Quanto tempo serve per creare un sito web con una Web agency?
H3 Una Web agency può gestire i miei social media?
H2 Hai bisogno di creare un sito web e farlo apparire in prima pagina su Google?
H2 Contattami e ti spiegherò come posso far crescere la tua attività in 6 mesi!
H3 Parliamo di crescita digitale
H3 Compila Il Form
H3 WEB AGENCY ROMA
H3 GIUSEPPE TARTARELLI
H3 SEO ITALIA
H3 servizi
H3 Link utili
H3 Social Media

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

Mobile-Readable Font Sizes

97% of visible text renders at >= 12 CSS px (2 below threshold)

REVIEW

97% of visible text renders at >= 12 CSS px (2 below threshold)

2 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: <a> 11.0px ("Privacy Policy"); <a> 11.0px ("Cookie Policy").

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 Pagina Non Trovata - SpecialistaSEO ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

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

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

h1 Web Agency Roma

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Ho pubblicato il mio libro che spiega co…

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h2 L'eccellenza nella SEO e nel Web Marketi…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Servizi Web Agency Roma

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Team Specializzato e Competente

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sono presente in queste città per Consu…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Metodo SEO e Strumenti di Lavoro

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Monitoraggio e misurazione dei risultati…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Cosa Faccio per Posizionare I Miei Clien…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 10 motivi per affidarti alla mia Web Age…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Conclusioni

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Domande Frequenti - Web Agency

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Hai bisogno di creare un sito web e farl…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contattami e ti spiegherò come posso fa…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Perché affidarsi alla mia Web Agency?

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Digital Off Site

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Content & Outreach

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 SEO Tecnica

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Formazione

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Link Building

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Web Agency Roma	1.00:1	3.0:1	#000000	#000000	Fail
h1 Ho pubblicato il mio…	1.00:1	3.0:1	#000000	#000000	Fail
h2 L'eccellenza nella S…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Servizi Web Agency R…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Team Specializzato e…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Sono presente in que…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Metodo SEO e Strumen…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Monitoraggio e misur…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Cosa Faccio per Posi…	1.00:1	3.0:1	#000000	#000000	Fail
h2 10 motivi per affida…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Conclusioni	1.00:1	3.0:1	#000000	#000000	Fail
h2 Domande Frequenti - …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Hai bisogno di crear…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Contattami e ti spie…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Perché affidarsi al…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Digital Off Site	1.00:1	3.0:1	#000000	#000000	Fail
h3 Content & Outreach	1.00:1	3.0:1	#000000	#000000	Fail
h3 SEO Tecnica	1.00:1	3.0:1	#000000	#000000	Fail
h3 Formazione	1.00:1	3.0:1	#000000	#000000	Fail
h3 Link Building	1.00:1	3.0:1	#000000	#000000	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 Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

3 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 3 all-caps heading(s)

A+

Alt Text Quality

All 14 images OK

PASS

All 14 images OK

14 image(s) with good alt text

14 images 14 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 7 controls have issues

PASS

1 of 7 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="submit">

6 control(s) properly labeled

7 controls

6 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
your-name	text	NOME	none
your-email	email	EMAIL	none
your-subject	text	OGGETTO	none
your-message	textarea	MESSAGGIO (facoltativo)	none
acceptance-979	checkbox		none
_wpcf7_ak_hp_textarea	textarea	Δ	none
input	submit	(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

Link & Button Quality

80 links, 4 buttons — all OK

PASS

80 links, 4 buttons — all OK

18 link(s) open in new tab without warning

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

Got: https://www.amazon.it/Percorso-Essere-Primo-Google-efficacemente/dp/B0F35DFCX…; https://docs.google.com/forms/d/e/1FAIpQLSc6eSfneQ0tmE6AIjfkOUFnA9uMgMdSbPHXB…; https://pagespeed.web.dev; https://www.specialistaseo.net/seo-roma/; https://www.specialistaseo.net/seo-milano/; https://www.specialistaseo.net/seo-napoli/; https://www.specialistaseo.net/seo-torino/; https://www.specialistaseo.net/seo-firenze/; https://www.seozoom.it/seo/; https://www.iubenda.com/privacy-policy/17977420 (+8 more)

62 link(s) with descriptive text

80 links

0 empty

0 generic text

18 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.amazon.it/Percorso-Essere-Pr…	Disponibile su Amazon	new tab	Add '(opens in new tab)' to text
https://docs.google.com/forms/d/e/1FAIpQ…	PREVENTIVO SEO GRATUITO IN 24…	new tab	Add '(opens in new tab)' to text
https://pagespeed.web.dev	SCANSIONA IL TUO SITO E CONTAT…	new tab	Add '(opens in new tab)' to text
https://www.specialistaseo.net/seo-roma/	SEO Roma	new tab	Add '(opens in new tab)' to text
https://www.specialistaseo.net/seo-milan…	SEO Milano	new tab	Add '(opens in new tab)' to text
https://www.specialistaseo.net/seo-napol…	SEO Napoli	new tab	Add '(opens in new tab)' to text
https://www.specialistaseo.net/seo-torin…	SEO Torino	new tab	Add '(opens in new tab)' to text
https://www.specialistaseo.net/seo-firen…	SEO Firenze	new tab	Add '(opens in new tab)' to text
https://www.seozoom.it/seo/	SEO Updates	new tab	Add '(opens in new tab)' to text
https://www.iubenda.com/privacy-policy/1…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.iubenda.com/privacy-policy/1…	Cookie Policy	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/profile.php?id=…	Facebook-f	new tab	Add '(opens in new tab)' to text
https://x.com/Specialista_SEO	Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/specialistaseo…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@SpecialistaSEOR…	Youtube	new tab	Add '(opens in new tab)' to text
https://it.pinterest.com/consulenzaseoro…	Pinterest	new tab	Add '(opens in new tab)' to text
https://www.iubenda.com/privacy-policy/1…	cookie policy	new tab	Add '(opens in new tab)' to text
https://www.iubenda.com/it/cookie-soluti…	Created with iubenda(il link s…	new tab	Add '(opens in new tab)' to text

66 links and buttons have descriptive text

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

https://www.amazon.it/Percorso-Essere-Primo-Google-efficacemente/dp/B0F35DFCX…; https://docs.google.com/forms/d/e/1FAIpQLSc6eSfneQ0tmE6AIjfkOUFnA9uMgMdSbPHXB…; https://pagespeed.web.dev; https://www.specialistaseo.net/seo-roma/; https://www.specialistaseo.net/seo-milano/; https://www.specialistaseo.net/seo-napoli/; https://www.specialistaseo.net/seo-torino/; https://www.specialistaseo.net/seo-firenze/; https://www.seozoom.it/seo/; https://www.iubenda.com/privacy-policy/17977420 (+8 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

7 form control(s) checked, no type mismatches

PASS

7 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

Tabindex Anti-Patterns

21 explicit tabindex attribute(s) checked, no anti-patterns

PASS

21 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

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

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

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

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

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 28 passed

PASS

Accessibility

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cosa fa una Web agency? `div.elementor-widget-container > div.elementor-accordion > div.elementor-accordion-item > h3#elementor-tab-title-1691`

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.

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
Digital Off Site `div.elementor-widget-container > div.elementor-image-box-wrapper > div.elementor-image-box-content > h3.elementor-image-box-title`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

These items highlight common accessibility best practices.

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

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

●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

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

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Elements with visible text labels have matching accessible names.

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

○Form elements have associated labels

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

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

○Identical links have the same purpose.

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

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.