Accessibility

D

Landmark Structure

Action

5 landmarks

FIX

5 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

2 of 2 <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

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

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

F

Heading Hierarchy

Action

19 headings, 6 skip(s)

FIX

19 headings, 6 skip(s)

Multiple H1 headings (5 found)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (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 Pino Galvagno
H4 Sono un consulente SEO uno sviluppatore uno che non indossa la camicia un papà un consulente di marketing skipped
H2 Dueparole dipresentazione.
H1 87 duplicate H1
H4 Progetti skipped
H1 73 duplicate H1
H4 Clienti skipped
H1 2003 duplicate H1
H4 Script skipped
H1 48 duplicate H1
H4 Audit SEO skipped
H2 Ottimo! Scopri che posso fare per te
H4 Alcune mie competenze: skipped
H4 Progettazione
H4 Coordinazione progetto
H4 Ottimizzazione SEO
H4 Sviluppo Web
H2 Il tuo Consulente SEO freelance!
H2 Alcuni dei miei lavori più recenti

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

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

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

F

404 Error Page

Action

HTTP 509, bare page

FIX

HTTP 509, bare page

Unexpected status code: HTTP 509

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

Got: HTTP 509

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 509 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ff4200

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 ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 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

Search

Skip Link

Labeled Navigation 2 <nav> element(s)

Back to Top

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.

B

Heading Text Quality

2 heading-text-quality issue(s) detected

REVIEW

2 heading-text-quality issue(s) detected

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: - H1: "87" - H1: "73" - H1: "48"

Got: 3 ≤2-char heading(s)

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: - H4: 150 chars

Got: 1 >120-char heading(s)

B

Link & Button Quality

11 issue(s) across 42 links and 0 buttons

REVIEW

11 issue(s) across 42 links and 0 buttons

11 link(s) with no accessible text

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

Got: #nav; https://www.pinogalvagno.com/portfolio/sito-personale-laravel; https://www.pinogalvagno.com/portfolio/sito-di-webmarketing; https://www.pinogalvagno.com/portfolio/sito-psicologo-torino; https://www.pinogalvagno.com/portfolio/sito-di-vending; https://www.pinogalvagno.com/portfolio/siti-linkbuilding; https://www.facebook.com/pinononono; https://www.linkedin.com/in/pinogalvagno/; skype:computerpinux; mailto:pino@posizionamento-seo.com (+1 more)

31 link(s) with descriptive text

42 links

11 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#nav	(empty)	empty	Add link text or aria-label
https://www.pinogalvagno.com/portfolio/s…	(empty)	empty	Add link text or aria-label
https://www.pinogalvagno.com/portfolio/s…	(empty)	empty	Add link text or aria-label
https://www.pinogalvagno.com/portfolio/s…	(empty)	empty	Add link text or aria-label
https://www.pinogalvagno.com/portfolio/s…	(empty)	empty	Add link text or aria-label
https://www.pinogalvagno.com/portfolio/s…	(empty)	empty	Add link text or aria-label
https://www.facebook.com/pinononono	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/in/pinogalvagno…	(empty)	empty	Add link text or aria-label
skype:computerpinux	(empty)	empty	Add link text or aria-label
mailto:pino@posizionamento-seo.com	(empty)	empty	Add link text or aria-label
#top	(empty)	empty	Add link text or aria-label

31 links and buttons have descriptive text

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

#nav; https://www.pinogalvagno.com/portfolio/sito-personale-laravel; https://www.pinogalvagno.com/portfolio/sito-di-webmarketing; https://www.pinogalvagno.com/portfolio/sito-psicologo-torino; https://www.pinogalvagno.com/portfolio/sito-di-vending; https://www.pinogalvagno.com/portfolio/siti-linkbuilding; https://www.facebook.com/pinononono; https://www.linkedin.com/in/pinogalvagno/; skype:computerpinux; mailto:pino@posizionamento-seo.com (+1 more)

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

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA 5 pass AA only

h1 2003

1.32:1

#000000

on

#222222

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Due

1.32:1

#000000

on

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 parole di

1.32:1

#000000

on

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ottimo! Scopri

1.32:1

#000000

on

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 che

1.32:1

#000000

on

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Il tuo

1.32:1

#000000

on

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Consulente SEO freelance!

1.32:1

#000000

on

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Alcuni dei miei

1.32:1

#000000

on

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

a home

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Consulente SEO

1.78:1

#000000

on

#662100

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

1 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)

Element	Ratio	Required	FG	BG	Result
h1 Pino Galvagno	8.83:1	3.0:1	#000000	#FF8900	Pass
h1 2003	1.32:1	3.0:1	#000000	#222222	Fail
h2 Due	1.32:1	3.0:1	#000000	#222222	Fail
h2 parole di	1.32:1	3.0:1	#000000	#222222	Fail
h2 Ottimo! Scopri	1.32:1	3.0:1	#000000	#222222	Fail
h2 che	1.32:1	3.0:1	#000000	#222222	Fail
h2 Il tuo	1.32:1	3.0:1	#000000	#222222	Fail
h2 Consulente SEO freel…	1.32:1	3.0:1	#000000	#222222	Fail
h2 Alcuni dei miei	1.32:1	3.0:1	#000000	#222222	Fail
a home	1.00:1	4.5:1	#000000	#000000	Fail
a Consulente SEO	1.78:1	4.5:1	#000000	#662100	Fail
a Servizi	6.55:1	4.5:1	#000000	#FF5500	Pass
a Esperienze	6.65:1	4.5:1	#000000	#FF5800	Pass
a Portfolio	6.75:1	4.5:1	#000000	#FF5B01	Pass
a Blog	6.82:1	4.5:1	#000000	#FE5E01	Pass
a Contatti	6.96:1	4.5:1	#000000	#FF6100	Pass
a Accetto i cookie	7.04:1	4.5:1	#000000	#FF6301	Pass
p Questo sito usa i co…	7.71:1	4.5:1	#000000	#FF7305	Pass
a Informativa estesa	7.32:1	4.5:1	#000000	#FE6B00	Pass
title Pino Galvagno: consu…	7.86:1	4.5:1	#000000	#FD7802	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.

C

Lighthouse Accessibility Audits

Action

Score 73/100 — 5 failing, 10 passed

REVIEW

73

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
Le Mie Abilità `div.col-md-6 > div.about-info > div.about-btn > a.primary-btn`
Consulenza SEO `div.col-md-6 > div.about-info > div.about-btn > a.primary-btn`
Progettazione `div.col-md-6 > div.single-service > div.service-title > h4`
Coordinazione progetto `div.col-md-6 > div.single-service > div.service-title > h4`
Ottimizzazione SEO `div.col-md-6 > div.single-service > div.service-title > h4`
Sviluppo Web `div.col-md-6 > div.single-service > div.service-title > h4`
Vedi Tutti I Miei Lavori `div.row > div.col-sm-12 > div.load-more-btn > a.primary-btn`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Informativa estesa `body.mean-container > div.cookie_container > p.cookie_message > 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
Sono UN CONSULENTE SEO UNO SVILUPPATORE UNO CHE NON INDOSSA LA CAMICIA UN PAPÀ … `div.row > div.col-md-6 > div.banner-text > h4.cd-headline`
Progetti `div.col-md-3 > div.single-counter > div.counter-content > h4`
Clienti `div.col-md-3 > div.single-counter > div.counter-content > h4`
Script `div.col-md-3 > div.single-counter > div.counter-content > h4`
Audit SEO `div.col-md-3 > div.single-counter > div.counter-content > h4`
Alcune mie competenze: `div.row > div.col-md-6 > div.expart-area > h4`

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
body.mean-container > div.mean-bar > a.meanmenu-reveal `body.mean-container > div.mean-bar > a.meanmenu-reveal`
div.grid > div.grid-item > div > a `div.grid > div.grid-item > div > a`
div.grid > div.grid-item > div > a `div.grid > div.grid-item > div > a`
div.grid > div.grid-item > div > a `div.grid > div.grid-item > div > a`
div.grid > div.grid-item > div > a `div.grid > div.grid-item > div > a`
div.grid > div.grid-item > div > a `div.grid > div.grid-item > div > a`
div.social-media > ul > li > a `div.social-media > ul > li > a`
div.social-media > ul > li > a `div.social-media > ul > li > a`
div.social-media > ul > li > a `div.social-media > ul > li > a`
div.social-media > ul > li > a `div.social-media > ul > li > 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.

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

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

●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

●Touch targets have sufficient size and spacing.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○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

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

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

○Buttons have an accessible name

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

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

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

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

A+

Alt Text Quality

1 of 11 images have issues

PASS

1 of 11 images have issues

1 image(s) with generic alt text

5 decorative image(s) correctly marked

5 image(s) with good alt text

11 images 5 good alt text 5 decorative 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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+

Mobile-Readable Font Sizes

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

PASS

All 69 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

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.