Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 7 REVIEW 5 FIX

Form Accessibility

Action

6 of 6 controls have issues

FIX

6 of 6 controls have issues

3 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">; <input type="submit">

3 control(s) rely on placeholder only

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

Got: <input type="email" name="your-email">; <input type="email" name="your-email">; <input type="email" name="your-email">

6 controls

0 labeled

3 placeholder only

3 unlabeled

Control	Type	Label	Method
your-email	email	(Write your email)	placeholder only
your-email	email	(Write your email)	placeholder only
your-email	email	(Write your email)	placeholder only
input	submit	(none)	none
input	submit	(none)	none
input	submit	(none)	none

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

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

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

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

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

Heading Hierarchy

11 headings, 2 skip(s)

REVIEW

11 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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 Adaptive Autonomy for Unmanned Systems
H2 THE AUTONOMOUS UNMANNED ERA IS HERE
H2 Adaptive autonomy for aerial, surface and subsurface unmanned systems
H2 Bavovna Products
H2 Carolina DroneHub
H4 Manufacturing the next generation of NDAA-compliant drones, here in the Carolinas. skipped
H3 Bavovna Latest Updates:
H2 Bavovna UAV Directory
H4 A completely free and open directory of UAV manufacturers and platforms from across the world. skipped
H4 Follow us
H4 Sign up to our newsletter

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

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

Action

4 issue(s) across 54 links and 7 buttons

REVIEW

4 issue(s) across 54 links and 7 buttons

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://bavovna.ai/news/bavovna-best-solution-uav-expo-2024/ ("learn more"); https://bavovna.ai/seadrone/ ("Learn more")

9 link(s) open in new tab without warning

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

Got: https://www.wsj.com/world/europe/ukraine-russia-drone-swarm-ai-9c3389d2; https://www.economist.com/europe/2026/03/24/ukraine-leads-the-world-in-using-…; https://www.technologyreview.com/2026/01/06/1129737/autonomous-warfare-europe…; https://www.defensenews.com/unmanned/2026/04/24/ukraine-to-field-25000-ground…; https://foreignpolicy.com/2026/04/13/russia-ukraine-war-drones-ground-robots-…; https://www.newsweek.com/ukraine-ugvs-machine-gun-combat-robots-drones-1864843; https://www.reuters.com/world/europe/timeline-suspected-underwater-sabotage-b…; https://www.ft.com/content/baltic-undersea-cable-sabotage; https://www.cnbc.com/2026/04/23/the-future-of-air-power-is-autonomous-and-the…

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.cookies-close (#93 on page); button.menu-toggle (#104 on page)

43 link(s) with descriptive text

54 links

0 empty

2 generic text

9 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://bavovna.ai/news/bavovna-best-sol…	learn more	generic text	Replace with descriptive text
Before: learn more Suggested: Bavovna Best Solution Uav Expo 2024
https://www.wsj.com/world/europe/ukraine…	Ukraine deploys AI-controlled …	new tab	Add '(opens in new tab)' to text
https://www.economist.com/europe/2026/03…	Drone swarms reshape warfare, …	new tab	Add '(opens in new tab)' to text
https://www.technologyreview.com/2026/01…	Europe's drone-filled vision f…	new tab	Add '(opens in new tab)' to text
https://www.defensenews.com/unmanned/202…	Ukraine to field 25,000 ground…	new tab	Add '(opens in new tab)' to text
https://foreignpolicy.com/2026/04/13/rus…	Pressed by Russian Drones, Ukr…	new tab	Add '(opens in new tab)' to text
https://www.newsweek.com/ukraine-ugvs-ma…	Ukraine UGVs Machine Gun Comba…	new tab	Add '(opens in new tab)' to text
https://www.reuters.com/world/europe/tim…	Timeline of suspected underwat…	new tab	Add '(opens in new tab)' to text
https://www.ft.com/content/baltic-unders…	Another undersea cable damaged…	new tab	Add '(opens in new tab)' to text
https://www.cnbc.com/2026/04/23/the-futu…	The future of air power is aut…	new tab	Add '(opens in new tab)' to text
https://bavovna.ai/seadrone/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Seadrone
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

48 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://bavovna.ai/news/bavovna-best-solution-uav-expo-2024/ ("learn more"); https://bavovna.ai/seadrone/ ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.wsj.com/world/europe/ukraine-russia-drone-swarm-ai-9c3389d2; https://www.economist.com/europe/2026/03/24/ukraine-leads-the-world-in-using-…; https://www.technologyreview.com/2026/01/06/1129737/autonomous-warfare-europe…; https://www.defensenews.com/unmanned/2026/04/24/ukraine-to-field-25000-ground…; https://foreignpolicy.com/2026/04/13/russia-ukraine-war-drones-ground-robots-…; https://www.newsweek.com/ukraine-ugvs-machine-gun-combat-robots-drones-1864843; https://www.reuters.com/world/europe/timeline-suspected-underwater-sabotage-b…; https://www.ft.com/content/baltic-undersea-cable-sabotage; https://www.cnbc.com/2026/04/23/the-future-of-air-power-is-autonomous-and-the…

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.cookies-close (#93 on page); button.menu-toggle (#104 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Tap Target Adequacy

Action

5 tap target(s) too small or too close together

REVIEW

5 tap target(s) too small or too close together

5 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Страница не найдена - BAVOVNA ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 13 fail WCAG AA

REVIEW

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

7 pass 13 fail WCAG AA 2 pass AA only

title AI Navigation for Uncrewed Vehicles

1.40:1

#000000

#1C2738

needs 4.5:1 (normal text)

16px · top of page (header area)

a Commercial UAV Expo 2024: Bavovna.AI is …

1.42:1

#000000

#1C283C

needs 4.5:1 (normal text)

16px · top of page (header area)

a learn more

1.42:1

#000000

#1A283F

needs 4.5:1 (normal text)

16px · top of page (header area)

a Solutions

1.56:1

#000000

#202F47

needs 4.5:1 (normal text)

16px · top of page (header area)

a Products

1.58:1

#000000

#20304A

needs 4.5:1 (normal text)

16px · above the fold

a AI Autonomy Kit

1.58:1

#000000

#1E304C

needs 4.5:1 (normal text)

16px · above the fold

a AirTower

1.54:1

#000000

#1C2E4A

needs 4.5:1 (normal text)

16px · above the fold

a AirFlow Sensor

1.60:1

#000000

#1D314D

needs 4.5:1 (normal text)

16px · above the fold

a SeaDrone

1.75:1

#000000

#213756

needs 4.5:1 (normal text)

16px · above the fold

a Carolina DroneHub

1.96:1

#000000

#273F5E

needs 4.5:1 (normal text)

16px · above the fold

a Company

2.13:1

#000000

#2D455F

needs 4.5:1 (normal text)

16px · above the fold

a News

3.37:1

#000000

#4E6375

needs 4.5:1 (normal text)

16px · above the fold

a UAV Directory

3.33:1

#000000

#4B6372

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Adaptive Autonomy fo…	3.42:1	3.0:1	#000000	#4A666F	Pass
h2 THE AUTONOMOUS UNMAN…	4.11:1	3.0:1	#000000	#756C69	Pass
h2 Adaptive autonomy fo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Bavovna Products	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Carolina DroneHub	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Bavovna UAV Director…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Bavovna Latest Updat…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title AI Navigation for Un…	1.40:1	4.5:1	#000000	#1C2738	Fail
a Commercial UAV Expo …	1.42:1	4.5:1	#000000	#1C283C	Fail
a learn more	1.42:1	4.5:1	#000000	#1A283F	Fail
a Solutions	1.56:1	4.5:1	#000000	#202F47	Fail
a Products	1.58:1	4.5:1	#000000	#20304A	Fail
a AI Autonomy Kit	1.58:1	4.5:1	#000000	#1E304C	Fail
a AirTower	1.54:1	4.5:1	#000000	#1C2E4A	Fail
a AirFlow Sensor	1.60:1	4.5:1	#000000	#1D314D	Fail
a SeaDrone	1.75:1	4.5:1	#000000	#213756	Fail
a Carolina DroneHub	1.96:1	4.5:1	#000000	#273F5E	Fail
a Company	2.13:1	4.5:1	#000000	#2D455F	Fail
a News	3.37:1	4.5:1	#000000	#4E6375	Fail
a UAV Directory	3.33:1	4.5:1	#000000	#4B6372	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, 25 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.

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.container > div.row > nav#site-navigation > button.menu-toggle `div.container > div.row > nav#site-navigation > button.menu-toggle`

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
AI Autonomy Kit `div.container > div.row > div.solutions-col-2 > a.btn`
All Blogs and Posts `div.container > div.row > div.col-12 > a.btn`
Sep 05, 2026 `div.grid > div.blog-article > div.blog-article__content > span.blog-article__date`
Aug 26, 2026 `div.grid > div.blog-article > div.blog-article__content > span.blog-article__date`
Feb 27, 2026 `div.grid > div.blog-article > div.blog-article__content > span.blog-article__date`

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
Manufacturing the next generation of NDAA-compliant drones, here in the Carolin… `div.container > div.sector__content > div.sector__block > h4`
A completely free and open directory of UAV manufacturers and platforms from ac… `div.container > div.sector__content > div.sector__block > h4`

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 `div.col > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.col > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.col > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div.col > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `div.col > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`

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

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

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

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

○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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 23 images OK

PASS

All 23 images OK

23 image(s) with good alt text

23 images 23 good alt text

All images have appropriate alt text.

A+

Form Input Types

6 form control(s) checked, no type mismatches

PASS

6 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

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

Got: en-US

Tabindex Anti-Patterns

0 positive, 3 -1-on-focusable

PASS

0 positive, 3 -1-on-focusable

tabindex="-1" on naturally-focusable <input id="wpcf7-6ab01ad65160f-field">

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 <input id="wpcf7-6ab01ad655501-field">

tabindex="-1" on naturally-focusable <input id="wpcf7-6ab01ad66243d-field">

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

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

PASS

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