Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 8 REVIEW 5 FIX

Tabindex Anti-Patterns

Action

0 positive, 75 -1-on-focusable

FIX

0 positive, 75 -1-on-focusable

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

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>

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

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

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

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

22 landmarks

REVIEW

22 landmarks

<main> landmark present

17 <nav> landmark(s) found

4 of 17 <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

32 headings, 1 skip(s)

REVIEW

32 headings, 1 skip(s)

Single H1 present

Heading level skipped: H3 → H6 (missing H4)

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

2 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 Enel
H2 (empty)
H2 Build the futurethrough sustainable power
H2 Highlighted contents
H3 Growth, productivity, and an improved risk/return profile: Enel’s new Strategic Plan
H3 From wind to creativity: the winners of WinDesign
H3 Not another light gone out: Panchine Rosse™ (red benches) against gender-based violence
H3 Enel’s Talent Scout project kicks off
H3 Financial and environmental sustainability: the energy transition according to Enel
H3 Group's commitment to the energy transition in Brazil continues
H3 In Colombia, new investments in the energy transition
H3 Enel Innothon 2025: Energy and Artificial Intelligence, working together for the future
H3 The RES4Africa Foundation is training energy transition leaders: the first High Level Management Course has concluded
H3 Italy and Brazil are consolidating their relationship. After the G7 summit, CEO Cattaneo confirmed the Group's commitment during President Mattarella's State Visit to President Lula
H3 Enlit Europe 2024: continuous innovation for a flexible, integrated and sustainable network
H3 International collaboration and energy innovation: the role of Enel at the G7 summit
H3 Enel's new DEIB Policy: toward a more inclusive future in order to meet new challenges
H3 The distribution grids, the pillar of the energy transition
H3 Enel's innovation through AI
H3 Financial sustainability: the key to a sustainable future
H3 Hydroelectricity: a global renewable source
H3 (empty)
H3 Enel at UN General Assembly: global commitment to sustainability
H2 The power company that is changing the face of energy
H3 Our story
H3 Vision
H3 Locations
H3 Management team
H2 Energy is our starting point
H3 Discover what motivates us to keep on driving change
H3 Join us and play your part in the new energy era
H6 Select your language skipped

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

Alt Text Quality

1 of 27 images have issues

REVIEW

1 of 27 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

22 image(s) with good alt text

27 images 22 good alt text 1 decorative 1 missing

Issue	Count
missing	1 image(s)
too long	3 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Link & Button Quality

1 issue(s) across 125 links and 6 buttons

REVIEW

1 issue(s) across 125 links and 6 buttons

1 link(s) with no accessible text

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

Got: https://www.enel.com/azienda/storie/articles/2024/05/el-nino-la-nina-enso-cos…

26 link(s) open in new tab without warning

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

Got: https://www.enelgreenpower.com/; https://globaltrading.enel.com/en.html; https://openinnovability.enel.com; https://globalprocurement.enel.com/en.html; https://www.enelfoundation.org/; https://secure.ethicspoint.eu/domain/media/en/gui/102504/index.html; https://www.enelamericas.com/en.html; https://www.enel.com.ar/Home-Enel.html; https://www.enel.com.br/en; https://www.enel.cl/en.html (+16 more)

98 link(s) with descriptive text

125 links

1 empty

0 generic text

26 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.enelgreenpower.com/	Enel Green Power	new tab	Add '(opens in new tab)' to text
https://globaltrading.enel.com/en.html	Enel Global Energy and Commodi…	new tab	Add '(opens in new tab)' to text
https://openinnovability.enel.com	Enel Open Innovability®	new tab	Add '(opens in new tab)' to text
https://globalprocurement.enel.com/en.ht…	Enel Global Procurement	new tab	Add '(opens in new tab)' to text
https://www.enelfoundation.org/	Enel Foundation	new tab	Add '(opens in new tab)' to text
https://secure.ethicspoint.eu/domain/med…	Ethical Channel	new tab	Add '(opens in new tab)' to text
https://www.enelamericas.com/en.html	Americas	new tab	Add '(opens in new tab)' to text
https://www.enel.com.ar/Home-Enel.html	Argentina	new tab	Add '(opens in new tab)' to text
https://www.enel.com.br/en	Brasil	new tab	Add '(opens in new tab)' to text
https://www.enel.cl/en.html	Chile	new tab	Add '(opens in new tab)' to text
https://www.enel.com.co/en	Colombia	new tab	Add '(opens in new tab)' to text
https://www.endesa.com/en.html	Iberia	new tab	Add '(opens in new tab)' to text
https://www.enel.it/	Italy	new tab	Add '(opens in new tab)' to text
https://www.enel.mx/en	Mexico	new tab	Add '(opens in new tab)' to text
https://www.enelnorthamerica.com/	North America	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/EnelGroup/	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/EnelGroup/	Twitter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@enelgroup	YouTube	new tab	Add '(opens in new tab)' to text
http://www.linkedin.com/company/enelgrou…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/enelgroup/	Instagram	new tab	Add '(opens in new tab)' to text
#	Open Enel Group Menu	img no alt	Add alt attribute to the image
https://www.enel.com/azienda/storie/arti…	(empty)	empty	Add link text or aria-label
https://www.facebook.com/enelgroup	Facebook Enel profile	new tab	Add '(opens in new tab)' to text
https://twitter.com/EnelGroup	Twitter Enel profile	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/enelgro…	LinkedIn Enel profile	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@enelgroup	YouTube Enel channel	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/enelgroup/	Instagram Enel profile	new tab	Add '(opens in new tab)' to text
https://www.enel.com/cookie-policy	Cookie Policy here	new tab	Add '(opens in new tab)' to text

104 links and buttons have descriptive text

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

https://www.enel.com/azienda/storie/articles/2024/05/el-nino-la-nina-enso-cos…

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://www.enelgreenpower.com/; https://globaltrading.enel.com/en.html; https://openinnovability.enel.com; https://globalprocurement.enel.com/en.html; https://www.enelfoundation.org/; https://secure.ethicspoint.eu/domain/media/en/gui/102504/index.html; https://www.enelamericas.com/en.html; https://www.enel.com.ar/Home-Enel.html; https://www.enel.com.br/en; https://www.enel.cl/en.html (+16 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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 | Enel Group ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Favicon & Branding

Action

7 icon(s) detected

REVIEW

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 through sustainable power

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Highlighted contents

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The power company that is changing the f…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 Energy is our starting point

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h3 Growth, productivity, and an improved ri…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 From wind to creativity: the winners of …

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Not another light gone out: Panchine Ros…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Enel’s Talent Scout project kicks off

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Financial and environmental sustainabili…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Group's commitment to the energy transit…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 In Colombia, new investments in the ener…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Enel Innothon 2025: Energy and Artificia…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 The RES4Africa Foundation is training en…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Italy and Brazil are consolidating their…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Enlit Europe 2024: continuous innovation…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 International collaboration and energy i…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Enel's new DEIB Policy: toward a more in…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 The distribution grids, the pillar of th…

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Enel's innovation through AI

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Financial sustainability: the key to a s…

1.00:1

#000000

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)

Element	Ratio	Required	FG	BG	Result
h2 through sustainable …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Highlighted contents	1.00:1	3.0:1	#000000	#000000	Fail
h2 The power company th…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Energy is our starti…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Growth, productivity…	1.00:1	3.0:1	#000000	#000000	Fail
h3 From wind to creativ…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Not another light go…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Enel’s Talent Scou…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Financial and enviro…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Group's commitment t…	1.00:1	3.0:1	#000000	#000000	Fail
h3 In Colombia, new inv…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Enel Innothon 2025: …	1.00:1	3.0:1	#000000	#000000	Fail
h3 The RES4Africa Found…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Italy and Brazil are…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Enlit Europe 2024: c…	1.00:1	3.0:1	#000000	#000000	Fail
h3 International collab…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Enel's new DEIB Poli…	1.00:1	3.0:1	#000000	#000000	Fail
h3 The distribution gri…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Enel's innovation th…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Financial sustainabi…	1.00:1	3.0:1	#000000	#000000	Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 26 passed

REVIEW

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Growth, productivity, and an improved risk/return profile: Enel’s new Strategic… `main#main > section.ContentBox > div > div.wrapper`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Settings `div#truste-consent-track > div#truste-consent-content > div#truste-consent-buttons > button#truste-show-consent`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#truste-consent-track > div#truste-consent-content > div#truste-consent-buttons > img#truste-consent-required `div#truste-consent-track > div#truste-consent-content > div#truste-consent-buttons > img#truste-consent-required`

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.

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
Accessibilty `div.footer-menu > nav.menu > div.item > a`
English `nav.menu > div.item > div.LanguagePopover > a.trigger`

○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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

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

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

○`[accesskey]` values are unique

○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

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

○No form fields have multiple labels

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

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

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

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 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: - H3: 181 chars

Got: 1 >120-char heading(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+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

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

PASS

All 142 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.

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