Skip to content
https://www.oprc.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
6
REVIEW
7
PASS
11
INFO
0
Checks
24
11 PASS 7 REVIEW 6 FIX
F
Heading Hierarchy
Action
79 headings, 1 skip(s)
FIX
79 headings, 1 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: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
8 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Menu principale
  • H1 OPRC – Ordine Psicologi Regione Campania
  • H1 OPRC – Ordine Psicologi Regione Campania duplicate H1
  • H2 Servizi gratuiti per le iscritte e gli iscritti OPRC
  • H2 (empty)
  • H2 La rivista scientifica OPRC - Anno 5 n.2/2026
  • H2 LINEE D’INDIRIZZO SUI TIROCINI PROFESSIONALIZZANTI NELLA LM-51 E SULLA LORO VALUTAZIONE
  • H2 Nuovo servizio gratuito: Alert Concorsi e Bandi per Psicologi con Rivelio.it
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H2 Servizi gratuiti per le iscritte e gli iscritti OPRC
  • H2 (empty)
  • H2 La rivista scientifica OPRC - Anno 5 n.2/2026
  • H2 LINEE D’INDIRIZZO SUI TIROCINI PROFESSIONALIZZANTI NELLA LM-51 E SULLA LORO VALUTAZIONE
  • H2 Nuovo servizio gratuito: Alert Concorsi e Bandi per Psicologi con Rivelio.it
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H2 Cerca Psicologi iscritti all'Albo
  • H3 Notizie
  • H4 Chiusura Estiva degli Uffici di…
  • H4 12ª Giornata Mondiale della Malattia…
  • H4 Lettera Aperta del GdL “Etnopsicologia”sulla…
  • H4 Il cordoglio dell’Ordine degli Psicologi…
  • H4 Richiesta la banca dati per…
  • H4 Emergenza Sismica Campi Flegrei: supporto…
  • H4 ECM 2026-2028: riparte la formazione…
  • H4 Rassegna Stampa
  • H4 Categorie
  • H4 La vicinanza dell’Ordine Psicologi Regione…
  • H4 L’Ordine Psicologi Regione Campania nuovamente…
  • H4 Chiusura Estiva degli Uffici di…
  • H4 12ª Giornata Mondiale della Malattia…
  • H4 Lettera Aperta del GdL “Etnopsicologia”sulla…
  • H4 Il cordoglio dell’Ordine degli Psicologi…
  • H4 Richiesta la banca dati per…
  • H4 Emergenza Sismica Campi Flegrei: supporto…
  • H4 ECM 2026-2028: riparte la formazione…
  • H4 Rassegna Stampa
  • H4 Categorie
  • H4 La vicinanza dell’Ordine Psicologi Regione…
  • H4 L’Ordine Psicologi Regione Campania nuovamente…
  • H2 Istituzione del Servizio di Psicologia di base
  • H3 Servizi
  • H3 Eventi OPRC
  • H4 Dalla rottura al contenimento: aggressività e devianza nei giovani tra crisi del limite e intervento clinico dei servizi territoriali
  • H4 Categorie
  • H4 La “rete” che salva la vita
  • H4 Categorie
  • H4 Giornate Endocrinologiche Sannite – II edizione
  • H4 Categorie
  • H4 La soggettività dello psicoterapeuta: impatto sulla tecnica e sulla relazione
  • H4 Categorie
  • H4 Sound, Light & Medicine – Corso di Aggiornamento in endocrinologia della riproduzione
  • H4 Categorie
  • H4 Aspetti Nutrizionali e Disturbi Gastrointestinali: causa o conseguenza di un Disturbo Alimentare?
  • H4 Categorie
  • H2 Protocollo OPRC Regione Campania
  • H3 Bandi e Avvisi
  • H4 Quarto Concorso Nazionale di Poesia A.M.M.I. – La Poesia è la Rivelazione dell’Anima
  • H4 Categorie
  • H4 Terzo Concorso Nazionale A.M.M.I sulla Poesia
  • H4 Categorie
  • H4 Approvazione atti e nomina vincitori del Concorso pubblico, per titoli ed esami, per la copertura a tempo indeterminato di n. 10 posti di Dirigente Psicologo
  • H4 Categorie
  • H3 Protocollo tra Ministero dell'Istruzione e CNOP
  • H2 Giornale trimestrale dell'OPRC
  • H3 Calendario Eventi
  • H3 11
  • H3 18
  • H3 19
  • H3 OPRC – Ordine Psicologi Regione Campania
  • H4 Recapiti
  • H4 Informazioni
  • H4 Posta Elettronica
  • H4 Seguici su
  • H3 Sezione Link Utili
  • H5 Suggerimenti per la ricerca skipped

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
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::
4 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 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <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

B
Heading Text Quality
3 heading-text-quality issue(s) detected
REVIEW
3 heading-text-quality issue(s) detected
Info::
3 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "11" - H3: "18" - H3: "19"
Got: 3 ≤2-char heading(s)
Warning::
2 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: - H4: 133 chars - H4: 157 chars
Got: 2 >120-char heading(s)
Info::
2 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: 2 all-caps heading(s)
C
Form Accessibility
Action
5 of 5 controls have issues
REVIEW
5 of 5 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="provincia">
Warning::
4 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">; <input type="text" name="nome">; <input type="text" name="cognome">
5 controls
0 labeled
4 placeholder only
1 unlabeled
ControlTypeLabelMethod
stext(Cerca)placeholder only
stext(Cerca)placeholder only
nometext(Nome dell'iscritto)placeholder only
cognometext(Cognome dell'iscritto)placeholder only
provinciaselect(none)none

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

<select name="provincia">

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">; <input type="text" name="nome">; <input type="text" name="cognome">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Pagina non trovata – OPRC – Ordine Psicologi Regione Campania Custom Styling Navigation Homepage Link Search Form
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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA 1 pass AA only
h1 OPRC – Ordine Psicologi Regione Campan…
1.59:1
#000000
on
#212D5A
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Cerca Psicologi iscritti all'Albo
1.59:1
#000000
on
#212D5A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Istituzione del Servizio di Psicologia d…
1.59:1
#000000
on
#212D5A
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Protocollo OPRC Regione Campania
1.59:1
#000000
on
#212D5A
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Giornale trimestrale dell'OPRC
1.59:1
#364992
on
#212D5A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Notizie
1.59:1
#000000
on
#212D5A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Servizi
1.59:1
#000000
on
#212D5A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Eventi OPRC
1.59:1
#000000
on
#212D5A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bandi e Avvisi
1.59:1
#000000
on
#212D5A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Protocollo tra Ministero dell'Istruzione…
1.59:1
#000000
on
#212D5A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Calendario Eventi
1.59:1
#000000
on
#212D5A
needs 3.0:1 (large text)
19px · bottom of viewport

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 OPRC – Ordine Psic…1.59:13.0:1
#000000
#212D5A
Fail
h2 Menu principale3.43:13.0:1
#000000
#5C6365
Pass
h2 Servizi gratuiti per…13.23:13.0:1
#FFFFFF
#212D5A
Pass
h2 La rivista scientifi…13.23:13.0:1
#FFFFFF
#212D5A
Pass
h2 LINEE D’INDIRIZZO …13.23:13.0:1
#FFFFFF
#212D5A
Pass
h2 Nuovo servizio gratu…13.23:13.0:1
#FFFFFF
#212D5A
Pass
h2 Servizi gratuiti per…13.23:13.0:1
#FFFFFF
#212D5A
Pass
h2 La rivista scientifi…13.23:13.0:1
#FFFFFF
#212D5A
Pass
h2 LINEE D’INDIRIZZO …13.23:13.0:1
#FFFFFF
#212D5A
Pass
h2 Nuovo servizio gratu…13.23:13.0:1
#FFFFFF
#212D5A
Pass
h2 Cerca Psicologi iscr…1.59:13.0:1
#000000
#212D5A
Fail
h2 Istituzione del Serv…1.59:13.0:1
#000000
#212D5A
Fail
h2 Protocollo OPRC Regi…1.59:13.0:1
#000000
#212D5A
Fail
h2 Giornale trimestrale…1.59:13.0:1
#364992
#212D5A
Fail
h3 Notizie1.59:13.0:1
#000000
#212D5A
Fail
h3 Servizi1.59:13.0:1
#000000
#212D5A
Fail
h3 Eventi OPRC1.59:13.0:1
#000000
#212D5A
Fail
h3 Bandi e Avvisi1.59:13.0:1
#000000
#212D5A
Fail
h3 Protocollo tra Minis…1.59:13.0:1
#000000
#212D5A
Fail
h3 Calendario Eventi1.59:13.0:1
#000000
#212D5A
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.

B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 30 passed
REVIEW
89

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div#owl-one > div.owl-dots > button.owl-dot div.row > div#owl-one > div.owl-dots > button.owl-dot
div.row > div#owl-one > div.owl-dots > button.owl-dot div.row > div#owl-one > div.owl-dots > button.owl-dot
div.row > div#owl-one > div.owl-dots > button.owl-dot div.row > div#owl-one > div.owl-dots > button.owl-dot
div.row > div#owl-one > div.owl-dots > button.owl-dot div.row > div#owl-one > div.owl-dots > button.owl-dot
div.row > div#owl-one > div.owl-dots > button.owl-dot div.row > div#owl-one > div.owl-dots > button.owl-dot
div.row > div#owl-one > div.owl-dots > button.owl-dot div.row > div#owl-one > div.owl-dots > button.owl-dot
div.row > div#owl-one > div.owl-dots > button.owl-dot div.row > div#owl-one > div.owl-dots > button.owl-dot
div.row > div#owl-one > div.owl-dots > button.owl-dot div.row > div#owl-one > div.owl-dots > button.owl-dot
div.row > div#owl-one > div.owl-dots > button.owl-dot div.row > div#owl-one > div.owl-dots > button.owl-dot
div.row > div#owl-one > div.owl-dots > button.owl-dot div.row > div#owl-one > div.owl-dots > button.owl-dot

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
footer#footer > div.container > section.postFooter > a footer#footer > div.container > section.postFooter > a
footer#footer > div.container > section.postFooter > a footer#footer > div.container > section.postFooter > 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.

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
Accetto body.t-Pac > div.cookiebar > p.text-white > button.btn

These are opportunities to improve the legibility of your content.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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.
`[accesskey]` values are unique
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Uses ARIA roles only on compatible elements
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.
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Skip links are focusable.
`<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>`.
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
A
Alt Text Quality
All 56 images OK
PASS
All 56 images OK
Info::
8 image(s) with alt text over 125 characters
Info::
8 decorative image(s) correctly marked
Info::
40 image(s) with good alt text
56 images 40 good alt text 8 decorative
IssueCount
too long8 image(s)
A+
Form Input Types
5 form control(s) checked, no type mismatches
PASS
5 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 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
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button>
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.)
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 32 visible text node(s) render at >= 12 CSS pixels
PASS
All 32 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback