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 4 REVIEW 6 FIX

Tabindex Anti-Patterns

Action

0 positive, 44 -1-on-focusable

FIX

0 positive, 44 -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 id="sm-17869835198609788-1">

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

tabindex="-1" on naturally-focusable <a id="sm-17869835198646655-1">

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

404 Error Page

Action

HTTP 508, bare page

FIX

HTTP 508, bare page

Unexpected status code: HTTP 508

Expected HTTP 404 but received 508. This may confuse search engine crawlers.

Got: HTTP 508

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 508 ✗Page Title 508 Resource Limit Is Reached ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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

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

8 landmarks

REVIEW

8 landmarks

<main> landmark present

5 <nav> landmark(s) found

3 of 5 <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

Heading Hierarchy

Action

46 headings, 2 skip(s)

REVIEW

46 headings, 2 skip(s)

Multiple H1 headings (4 found)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H2 → H4 (missing H3)

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

H1 Sono un consulente SEO Napoli e Italia, miglioro il posizionamento e la visibilità di siti web e e-commerce sui motori di ricerca.
H1 Consulente SEO Napoli e in tutta Italia duplicate H1
H3 CONSULENZA SEO skipped
H3 SVILUPPO SITI WEB
H3 ASSISTENZA WEB
H1 Cerchi Consulente SEO Napoli? duplicate H1
H2 Rendi forte la tua strategia digitale
H3 Scopri come posso aiutare la tua azienda a crescere oggi stesso!
H1 Il Consulente SEO è la soluzionea Napoli e tutta Italia duplicate H1
H2 Consulente SEO Napoli A chi è utile?
H3 Aziende
H3 Freelance
H3 Imprenditori
H3 Agenzie Web
H2 In cosa posso aiutarti?
H2 Tutti i servizi di Seonapsi hanno come fulcro la SEO (ottimizzazione per i motori di ricerca).
H2 NO, NON BASTA FARE UN SITO INTERNET
H2 Consulente SEO Napoli
H3 Posizionamento SEO per il tuo sito web a Napoli e tutta Italia
H3 Documenti strategici SEO
H3 Solo tecniche SEO White Hat
H3 Consulente SEO Napoli e tutta Italia
H2 Realizza sito web ottimizzato SEO
H3 A Napoli e in tutta Italia
H3 "Chiavi in mano" e accesso completo
H3 Zero costi di gestione
H3 Design personalizzato
H3 Backup automatico
H3 SEO friendly
H3 Firewall contro gli attacchi
H2 Accendi le SEONAPSI
H3 Meta tag e AI: come ottimizzarli per uno snippet che converte davvero
H3 Evoluzione della SEO con le nuove AI: cosa cambia davvero per chi lavora online
H3 Ai seo: come farsi trovare (e citare) dai motori di ricerca intelligenti
H3 Classi CSS in WordPress: guida pratica per personalizzare il tuo sito con precisione
H3 Posizionamento SEO: come scalare Google con una strategia che funziona davvero
H3 Contenuti generati da AI: come stanno cambiando il web, la SEO e la trasparenza
H3 Ricerche Correlate su Google: cosa sono e come usarle [SEO]
H3 Cosa sono i GPTs? la rivoluzione dei modelli linguistici nell’intelligenza artificiale
H3 Cerchi un consulente SEO a Napoli (ma anche in tutta Italia) affidabile e con esperienza?
H2 Lo hai trovato
H4 L'intuizione 🧠 skipped
H4 Servizi e Prodotti
H4 Il Blog
H4 Mini About
H4 Social

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

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

Action

3 issue(s) across 140 links and 6 buttons

REVIEW

3 issue(s) across 140 links and 6 buttons

3 link(s) with no accessible text

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

Got: https://www.facebook.com/seonapsi/; https://www.instagram.com/seonapsi/; https://www.linkedin.com/in/raoulgargiulo/

11 link(s) open in new tab without warning

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

Got: https://cookiedatabase.org/tcf/purposes/; https://www.facebook.com/seonapsi/; https://www.instagram.com/seonapsi/; https://www.linkedin.com/in/raoulgargiulo/; http://search.google.com/local/reviews?placeid=ChIJ9W6T7iIJOxMR67ABRfUG9zE; http://search.google.com/local/reviews?placeid=ChIJ9W6T7iIJOxMR67ABRfUG9zE; https://wordpress.org/plugins/publication-widget-seonapsi/; https://www.google.com/maps/place/Via+Giulio+Cesare,+19,+80125+Napoli+NA/@40.…; https://www.seonapsi.com/privacy-policy/; https://www.seonapsi.com/cookie-policy/ (+1 more)

126 link(s) with descriptive text

140 links

3 empty

0 generic text

11 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://cookiedatabase.org/tcf/purposes/	Per saperne di più su questi …	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/seonapsi/	Facebook-f	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/seonapsi/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/raoulgargiul…	Linkedin-in	new tab	Add '(opens in new tab)' to text
http://search.google.com/local/reviews?p…	Valutazione di Google 5.0	new tab	Add '(opens in new tab)' to text
http://search.google.com/local/reviews?p…	Valutazione di Google 5.0	new tab	Add '(opens in new tab)' to text
https://wordpress.org/plugins/publicatio…	– Publication Widget per Wor…	new tab	Add '(opens in new tab)' to text
https://www.google.com/maps/place/Via+Gi…	Via G. Cesare, 19 - 80125 Napo…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/seonapsi/	(empty)	empty	Add link text or aria-label
https://www.instagram.com/seonapsi/	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/in/raoulgargiul…	(empty)	empty	Add link text or aria-label
https://www.seonapsi.com/privacy-policy/	Privacy policy	new tab	Add '(opens in new tab)' to text
https://www.seonapsi.com/cookie-policy/	Cookie policy	new tab	Add '(opens in new tab)' to text
http://www.luigimassa.com/	Design: Luigi Massa	new tab	Add '(opens in new tab)' to text

132 links and buttons have descriptive text

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

https://www.facebook.com/seonapsi/; https://www.instagram.com/seonapsi/; https://www.linkedin.com/in/raoulgargiulo/

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://cookiedatabase.org/tcf/purposes/; https://www.facebook.com/seonapsi/; https://www.instagram.com/seonapsi/; https://www.linkedin.com/in/raoulgargiulo/; http://search.google.com/local/reviews?placeid=ChIJ9W6T7iIJOxMR67ABRfUG9zE; http://search.google.com/local/reviews?placeid=ChIJ9W6T7iIJOxMR67ABRfUG9zE; https://wordpress.org/plugins/publication-widget-seonapsi/; https://www.google.com/maps/place/Via+Giulio+Cesare,+19,+80125+Napoli+NA/@40.…; https://www.seonapsi.com/privacy-policy/; https://www.seonapsi.com/cookie-policy/ (+1 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

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

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 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: - H1: 130 chars

Got: 1 >120-char heading(s)

4 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: 4 all-caps heading(s)

Alt Text Quality

All 33 images OK

PASS

All 33 images OK

21 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

11 image(s) with good alt text

33 images 11 good alt text 1 decorative

Issue	Count
too long	21 image(s)

Form Accessibility

1 of 11 controls have issues

PASS

1 of 11 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response">

10 control(s) properly labeled

11 controls

10 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#cmplz-functional-optin	checkbox	Funzionale	for/id
#cmplz-preferences-optin	checkbox	Preferenze	for/id
#cmplz-statistics-optin	checkbox	Statistiche	for/id
#cmplz-marketing-optin	checkbox	Marketing	for/id
#form-field-name	text	Nome	for/id
#form-field-email	email	Email	for/id
#form-field-field_7eaa4bc	select	A quali servizi sei interessato?	for/id
#form-field-field_16ae4fa	text	Che budget hai in mente?	for/id
#form-field-message	textarea	Messaggio	for/id
#form-field-field_813d779	checkbox	ho letto ed accetto la privacy	for/id
#g-recaptcha-response	textarea	(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+

Form Input Types

11 form control(s) checked, no type mismatches

PASS

11 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "it-IT"

PASS

Lang attribute set to "it-IT"

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

Got: it-IT

Iframe Accessibility

1/2 iframe(s) missing title; 0 placeholder(s)

PASS

1/2 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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

PASS

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

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

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+

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 Sono un consulente S…	8.12:1	3.0:1	#000000	#93A59E	Pass
h1 Consulente SEO	8.12:1	3.0:1	#000000	#93A59E	Pass
h1 Napoli e in tutta It…	8.12:1	3.0:1	#000000	#93A59E	Pass
h1 Cerchi Consulente SE…	8.12:1	3.0:1	#000000	#93A59E	Pass
h1 Il Consulente SEO è…	8.12:1	3.0:1	#000000	#93A59E	Pass
h1 a Napoli e tutta Ita…	8.12:1	3.0:1	#000000	#93A59E	Pass
h2 Rendi forte la tua s…	8.12:1	3.0:1	#000000	#93A59E	Pass
h2 Consulente SEO Napol…	8.12:1	3.0:1	#000000	#93A59E	Pass
h2 A chi è utile?	8.12:1	3.0:1	#000000	#93A59E	Pass
h2 In cosa posso aiutar…	8.12:1	3.0:1	#000000	#93A59E	Pass
h2 Tutti i servizi di S…	8.12:1	3.0:1	#000000	#93A59E	Pass
h2 NO, NON BASTA FARE U…	8.12:1	3.0:1	#000000	#93A59E	Pass
h2 Consulente SEO Napol…	8.12:1	3.0:1	#000000	#93A59E	Pass
h2 Realizza sito web ot…	8.12:1	3.0:1	#000000	#93A59E	Pass
h2 Accendi le SEONAPSI	8.12:1	3.0:1	#000000	#93A59E	Pass
h2 Lo hai trovato	8.12:1	3.0:1	#000000	#93A59E	Pass
h3 CONSULENZA SEO	8.12:1	3.0:1	#000000	#93A59E	Pass
h3 SVILUPPO SITI WEB	8.12:1	3.0:1	#000000	#93A59E	Pass
h3 ASSISTENZA WEB	8.12:1	3.0:1	#000000	#93A59E	Pass
h3 Scopri come posso ai…	8.12:1	3.0:1	#000000	#93A59E	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.

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.

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
OK `div#cmplz-cookiebanner-container > div.cmplz-cookiebanner > div.cmplz-buttons > button.cmplz-btn`
NO GRAZIE `div#cmplz-cookiebanner-container > div.cmplz-cookiebanner > div.cmplz-buttons > button.cmplz-btn`
PREFERENZE `div#cmplz-cookiebanner-container > div.cmplz-cookiebanner > div.cmplz-buttons > button.cmplz-btn`
Cookie Policy `div#cmplz-cookiebanner-container > div.cmplz-cookiebanner > div.cmplz-links > a.cmplz-link`
Privacy Policy `div#cmplz-cookiebanner-container > div.cmplz-cookiebanner > div.cmplz-links > a.cmplz-link`
CONSULENZA SEO `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title`
SVILUPPO SITI WEB `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title`
ASSISTENZA WEB `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title`
Aziende `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title`
Freelance `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title`
Imprenditori `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title`
Agenzie Web `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title`
Posizionamento SEO per il tuo sito web a Napoli e tutta Italia `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title`
A Napoli e in tutta Italia `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title`
Lo hai trovato `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h2.elementor-heading-title`
privacy `div.elementor-field-subgroup > span.elementor-field-option > label > a`

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
CONSULENZA SEO `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title`
L'intuizione 🧠 `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-title`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a `div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a`
div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a `div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a`
div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a `div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

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

●Select elements have associated label elements.

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

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

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

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●No form fields have multiple labels

○`[accesskey]` values are unique

○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

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

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

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

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