Skip to content
https://ordinemedicilatina.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
6
REVIEW
5
PASS
13
INFO
0
Checks
24
13 PASS 5 REVIEW 6 FIX
D
Form Accessibility
Action
4 of 19 controls have issues
FIX
4 of 19 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">; <input type="text" name="s">
Info::
15 control(s) properly labeled
19 controls
15 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#is-search-input-276123searchSearch for:none
#is-search-input-276123searchSearch for:none
#checkbox-necessarycheckboxTecnici necessariaria-label
#checkbox-analyticscheckboxAnaliticiaria-label
#checkbox-marketingcheckboxMarketingaria-label
#wt-cli-checkbox-necessarycheckboxTecnici necessariaria-label
#wt-cli-checkbox-analyticscheckboxanalyticsaria-label
#wt-cli-checkbox-marketingcheckboxmarketingaria-label
#at-profile-epilepsycheckboxnone
#at-profile-visioncheckboxnone
#at-profile-adhdcheckboxnone
#at-profile-cognitivecheckboxnone
#at-profile-motorcheckboxnone
#at-profile-blindcheckboxnone
#at-useful-links-selectselectLink Utiliaria-label
stext(Cerca)placeholder only
stext(Cerca)placeholder only
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="s">; <input type="text" name="s">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-kqzwr3
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://ordinemedicilatina.it/manifest.webmanifest contains invalid JSON. Browsers cannot parse it.
Got: https://ordinemedicilatina.it/manifest.webmanifest

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
Info::
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
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
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 2 <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
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN CONTENTINFO footer

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
Heading Hierarchy
Action
36 headings, 2 skip(s)
REVIEW
36 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Menu principale
  • H1 OMCeO Latina
  • H1 OMCeO Latina Ordine dei Medici Chirurghi ed Odontoiatri della Provincia di Latina duplicate H1
  • H5 L’Ordine skipped
  • H5 Servizi Online
  • H5 Formazione
  • H2 SPORTELLO GIOVANI ISCRITTI
  • H2 MODIFICA ORARIO DI APERTURA
  • H2 AVVISO DI CONVOCAZIONE ASSEMBLEA ORDINARIA DEGLI ISCRITTI
  • H2 Le ultime notizie
  • H3 AVVISO DI CONVOCAZIONE ASSEMBLEA ORDINARIA DEGLI ISCRITTI
  • H3 EVENTO PATROCINATO -”5° CONGRESSO INTERREGIOANLE SIICP LAZIO-UMBRIA” – MONTE PORZIO CATONE 14 NOVEMBRE 2026 –
  • H3 EVENTO PATROCINATO – “ALLATTAMENTO AL SENO MATERNO” – 07 NOVEMBRE 2026, APRILIA (LT)
  • H3 Messaggio di condoglianze decesso Dott. D’Onofrio Agostino
  • H3 Messaggio di condoglianze decesso Dott. Giuseppe Santamaria
  • H3 PUBBLICAZIONE DELL’ESITO DELL’AVVISO PUBBLICO PER IL CONFERIMENTO DI N. 7 INCARICHI DI MEDICO GENERICO FIDUCIARIO PER L’ASSISTENZA SANITARIA E MEDICO-LEGALE AL PERSONALE NAVIGANTE, MARITTIMO E D
  • H3 REGIONE LAZIO: “FARMACI EROGABILI A CARICO DEL SERVIZIO SANITARIO NAZIONALE – SSN AI SENSI DELLA L.648/96; RECEPIMENTO ELENCO AIFA SETTEMBRE 2026.”
  • H3 REGIONE LAZIO: ELENCO DEI FARMACI DI CUI È SCADUTA LA COPERTURA BREVETTUALE E RELATIVI PREZZI DI RIFERIMENTO; LISTA DI TRASPARENZA DEL 15 OTTOBRE 2026.
  • H3 REGIONE LAZIO: EROGAZIONE IN DISTRIBUZIONE PER CONTO DEI FARMACI SODIO ZIRCONIO CICLOSILICATO (LOKELMA) E PATIROMER CALCIO (VELTASSA) A FAR DATA 16 OTTOBRE 2026.
  • H2 Seguici anche sui social
  • H2 Albo Dinamico Online
  • H3 Tutti i servizi
  • H2 Utilità
  • H2 Le nostre rubriche
  • H2 I progetti
  • H4 I documentari e gli approfondimenti skipped
  • H3 OMCeO Latina
  • H4 Orari
  • H4 Link Utili
  • H4 Recapiti
  • H4 Informazioni
  • H4 Posta Elettronica
  • H4 Seguici su
  • H3 Sezione Link Utili
  • H4 Privacy Overview
  • H2 AccessyTrace

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 ▾

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

B
Mobile-Readable Font Sizes
99% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
99% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
1 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> 11.0px ("ENTE DI DIRITTO PUBBLICO NON ECONOMICO O...").
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
3 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: 194 chars - H3: 147 chars - H3: 151 chars
Got: 3 >120-char heading(s)
Info::
10 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: 10 all-caps heading(s)
A+
Alt Text Quality
All 9 images OK
PASS
All 9 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
8 image(s) with good alt text
9 images 8 good alt text
IssueCount
too long1 image(s)
A+
Form Input Types
19 form control(s) checked, no type mismatches
PASS
19 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
19 form control(s) checked, no input-semantic issues
PASS
19 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<html lang="it-IT"> is set and valid
Got: it-IT
A+
Tabindex Anti-Patterns
75 explicit tabindex attribute(s) checked, no anti-patterns
PASS
75 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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)
ElementRatioRequiredFGBGResult
h1 OMCeO Latina21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Menu principale21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SPORTELLO GIOVANI IS…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 MODIFICA ORARIO DI A…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AVVISO DI CONVOCAZIO…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Le ultime notizie21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Seguici anche sui so…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Albo Dinamico Online21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Utilità21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Le nostre rubriche21.00:13.0:1
#000000
#FFFFFF
Pass
h2 I progetti21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AccessyTrace21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AVVISO DI CONVOCAZIO…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 EVENTO PATROCINATO -…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 EVENTO PATROCINATO …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Messaggio di condogl…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Messaggio di condogl…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 PUBBLICAZIONE DELL…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 REGIONE LAZIO: “FA…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 REGIONE LAZIO: ELENC…21.00:13.0:1
#000000
#FFFFFF
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 96/100 — 3 failing, 33 passed
PASS
96

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
30 Ottobre 2026 a.omceo-card-link > div.omceo-card-body > p.omceo-date > time
28 Ottobre 2026 a.omceo-card-link > div.omceo-card-body > p.omceo-date > time
28 Ottobre 2026 a.omceo-card-link > div.omceo-card-body > p.omceo-date > time
28 Ottobre 2026 a.omceo-card-link > div.omceo-card-body > p.omceo-date > time
28 Ottobre 2026 a.omceo-card-link > div.omceo-card-body > p.omceo-date > time
26 Ottobre 2026 a.omceo-card-link > div.omceo-card-body > p.omceo-date > time
23 Ottobre 2026 a.omceo-card-link > div.omceo-card-body > p.omceo-date > time
23 Ottobre 2026 a.omceo-card-link > div.omceo-card-body > p.omceo-date > time
23 Ottobre 2026 a.omceo-card-link > div.omceo-card-body > p.omceo-date > time
Facebook div.social-card > div.social-buttons > a.social-btn > span
YouTube div.social-card > div.social-buttons > a.social-btn > span
Impostazioni div.wt-cli-template > div.cli-bar-actions > div.cli-bar-btn_container > a#wt-cli-settings-btn

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
I documentari e gli approfondimenti div#pgc-7-9-0 > div#panel-7-9-0-0 > div.panel-widget-style > h4

These are opportunities to improve keyboard navigation in your application.

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
Seguici anche tramite il nostro bollettino "Medicina Pontina" div.oml-vp__row > div.oml-vp__center > div.oml-vp__panel > a.oml-vp__cta
AVVISO DI CONVOCAZIONE ASSEMBLEA ORDINARIA DEGLI ISCRITTI 30 Ottobre 2026 È i… section#newsgrid-6986 > div.omceo-news-grid > article.omceo-card > a.omceo-card-link
EVENTO PATROCINATO -”5° CONGRESSO INTERREGIOANLE SIICP LAZIO-UMBRIA” – MONTE PO… section#newsgrid-6986 > div.omceo-news-grid > article.omceo-card > a.omceo-card-link
EVENTO PATROCINATO – “ALLATTAMENTO AL SENO MATERNO” – 07 NOVEMBRE 2026, APRILIA… section#newsgrid-6986 > div.omceo-news-grid > article.omceo-card > a.omceo-card-link
Messaggio di condoglianze decesso Dott. D’Onofrio Agostino 28 Ottobre 2026 Ap… section#newsgrid-6986 > div.omceo-news-grid > article.omceo-card > a.omceo-card-link
Messaggio di condoglianze decesso Dott. Giuseppe Santamaria 28 Ottobre 2026 A… section#newsgrid-6986 > div.omceo-news-grid > article.omceo-card > a.omceo-card-link
PUBBLICAZIONE DELL’ESITO DELL’AVVISO PUBBLICO PER IL CONFERIMENTO DI N. 7 INCAR… section#newsgrid-6986 > div.omceo-news-grid > article.omceo-card > a.omceo-card-link
REGIONE LAZIO: “FARMACI EROGABILI A CARICO DEL SERVIZIO SANITARIO NAZIONALE – S… section#newsgrid-6986 > div.omceo-news-grid > article.omceo-card > a.omceo-card-link
REGIONE LAZIO: ELENCO DEI FARMACI DI CUI È SCADUTA LA COPERTURA BREVETTUALE E R… section#newsgrid-6986 > div.omceo-news-grid > article.omceo-card > a.omceo-card-link
REGIONE LAZIO: EROGAZIONE IN DISTRIBUZIONE PER CONTO DEI FARMACI SODIO ZIRCONIO… section#newsgrid-6986 > div.omceo-news-grid > article.omceo-card > a.omceo-card-link
○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
●Input buttons have discernible text.
●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.
●`[accesskey]` values are unique
●`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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
○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
○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 type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.

Send Feedback