Skip to content
http://Teenaadentalcare.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
10
REVIEW
3
PASS
11
INFO
0
Checks
24
11 PASS 3 REVIEW 10 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
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 MAIN (missing!) CONTENTINFO footer

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

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

D
Heading Hierarchy
Action
27 headings, 4 skip(s)
FIX
27 headings, 4 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Elevating Smiles with Expert Care and a Gentle Touch
  • H4 Need Dental Services? skipped
  • H4 Opening Hours
  • H4 Email Us
  • H2 Led by Expertise, Driven by Compassion
  • H2 Complete Care for Every Smile
  • H4 Dental Cleaning skipped
  • H4 Dental Implants
  • H4 Aligners Treatment
  • H4 Orthodontic Treatment
  • H4 Pediatric Dentistry
  • H4 Restorative Dentistry
  • H3 0+
  • H3 0+
  • H3 0+
  • H2 Expert Care, Gentle Touch – Led by Dr. Paarvathi Thenappan
  • H5 Specialized Expertise skipped
  • H5 Kid-Friendly Dentistry
  • H5 Pain-Free Treatments
  • H5 Advanced Technology
  • H2 Frequently Asked Questions
  • H2 Our Happy Customers
  • H3 Ready to book your dental care session?
  • H2 We are always ready to help you and answer your questions
  • H3 Send Us a Message
  • H5 Company skipped
  • H5 Contact Us

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

D
Mobile Keyboard & Autofill
Action
3/3 eligible field(s) missing autocomplete or inputmode
FIX
3/3 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: name, email.
Got: <input type="text" name="name" id="name">, <input type="email" name="email" id="email">
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" name="email" id="email">
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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: <input type="submit" id="send_message">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="name" id="name">; <input type="email" name="email" id="email">; <input type="text" name="phone" id="phone">; <textarea name="message" id="message">
5 controls
0 labeled
4 placeholder only
1 unlabeled
ControlTypeLabelMethod
#nametext(Your Name)placeholder only
#emailemail(Your Email)placeholder only
#phonetext(Your Phone)placeholder only
#messagetextarea(Your Message)placeholder only
#send_messagesubmit(none)none

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

<input type="submit" id="send_message">

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="name" id="name">; <input type="email" name="email" id="email">; <input type="text" name="phone" id="phone">; <textarea name="message" id="message">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA 6 pass AA only
h1 Elevating Smiles with Expert Care and a …
2.68:1
#000000
on
#524F69
needs 3.0:1 (large text)
32px · above the fold · over background image/gradient
h2 Led by Expertise, Driven by Compassion
2.80:1
#000000
on
#505275
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Complete Care for Every Smile
2.80:1
#000000
on
#505275
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Expert Care, Gentle Touch – Led by Dr.…
2.80:1
#000000
on
#505275
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frequently Asked Questions
2.80:1
#000000
on
#505275
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Happy Customers
2.80:1
#000000
on
#505275
needs 3.0:1 (large text)
24px · bottom of viewport
h2 We are always ready to help you and answ…
2.80:1
#000000
on
#505275
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Ready to book your dental care session?
2.80:1
#000000
on
#505275
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Send Us a Message
2.80:1
#000000
on
#505275
needs 3.0:1 (large text)
19px · bottom of viewport
title Teenaa Dental Care – Dentist in Thirum…
1.38:1
#000000
on
#10244B
needs 4.5:1 (normal text)
16px · top of page (header area)
a 7395973164
1.38:1
#000000
on
#10244B
needs 4.5:1 (normal text)
16px · top of page (header area)
a teenaadentalcare@gmail.com
1.38:1
#000000
on
#10244B
needs 4.5:1 (normal text)
16px · top of page (header area)

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)
ElementRatioRequiredFGBGResult
h1 Elevating Smiles wit…2.68:13.0:1
#000000
#524F69
Fail
h2 Led by Expertise, Dr…2.80:13.0:1
#000000
#505275
Fail
h2 Complete Care for Ev…2.80:13.0:1
#000000
#505275
Fail
h2 Expert Care, Gentle …2.80:13.0:1
#000000
#505275
Fail
h2 Frequently Asked Que…2.80:13.0:1
#000000
#505275
Fail
h2 Our Happy Customers2.80:13.0:1
#000000
#505275
Fail
h2 We are always ready …2.80:13.0:1
#000000
#505275
Fail
h3 Ready to book your d…2.80:13.0:1
#000000
#505275
Fail
h3 Send Us a Message2.80:13.0:1
#000000
#505275
Fail
title Teenaa Dental Care …1.38:14.5:1
#000000
#10244B
Fail
a 73959731641.38:14.5:1
#000000
#10244B
Fail
a teenaadentalcare@gma…1.38:14.5:1
#000000
#10244B
Fail
a Home8.69:14.5:1
#000000
#9FA7B7
Pass
a Services13.32:14.5:1
#000000
#CDCDD8
Pass
a About5.73:14.5:1
#000000
#84839F
Pass
a Experience5.73:14.5:1
#000000
#84839F
Pass
a FAQ5.86:14.5:1
#000000
#8585A0
Pass
a Testimonials5.88:14.5:1
#000000
#8685A0
Pass
a Contact5.88:14.5:1
#000000
#8685A0
Pass
span Book on WhatsApp5.80:14.5:1
#000000
#85849F
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.

B
Lighthouse Accessibility Audits
Score 86/100 — 3 failing, 13 passed
REVIEW
86

Accessibility

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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About div.de-flex-col > ul#mainmenu > li > a.menu-item
Experience div.de-flex-col > ul#mainmenu > li > a.menu-item
FAQ div.de-flex-col > ul#mainmenu > li > a.menu-item
Testimonials div.de-flex-col > ul#mainmenu > li > a.menu-item
Contact div.de-flex-col > ul#mainmenu > li > a.menu-item
Ready to book your dental care session? div.container > div.row > div.col-md-9 > h3.mb-0
Book Appointment div.row > div.col-lg-3 > a.btn-main > span
Get In Touch div.container > div.row > div.col-lg-6 > div.subtitle
Whether you have a question, a suggestion, or just want to say hello, this is t… div.container > div.row > div.col-lg-6 > p
We're Open Mon – Sun 9:00 AM – 1:00 PM 4:00 PM – 9:00 PM div.row > div.col-lg-6 > div.row > div.col-lg-6
Clinic Location FIRST FLOOR, UMA COMPLEX, 65, Cholambedu Main Rd, Near OLD KANN… div.row > div.col-lg-6 > div.row > div.col-lg-6
Call / WhatsApp 73959 73164 div.row > div.col-lg-6 > div.row > div.col-lg-6
Email teenaadentalcare@gmail.com div.row > div.col-lg-6 > div.row > div.col-lg-6
div.p-40 > form#contact_form > div#submit > input#send_message div.p-40 > form#contact_form > div#submit > input#send_message

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
Need Dental Services? div.col-lg-4 > div.d-flex > div.ms-3 > h4.mb-0
Company div.row > div.col-lg-6 > div.widget > h5

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
div.row > div.col-md-6 > div.top-social > a div.row > div.col-md-6 > div.top-social > a
div.row > div.col-md-6 > div.top-social > a div.row > div.col-md-6 > div.top-social > a
div.row > div.col-md-6 > div.top-social > a div.row > div.col-md-6 > div.top-social > a
div.row > div.col-md-6 > div.top-social > a div.row > div.col-md-6 > div.top-social > a
div.de-flex > div.de-flex-col > div#logo > a div.de-flex > div.de-flex-col > div#logo > a
div.row > div.col-lg-4 > div.social-icons > a div.row > div.col-lg-4 > div.social-icons > a
div.row > div.col-lg-4 > div.social-icons > a div.row > div.col-lg-4 > div.social-icons > a
div.row > div.col-lg-4 > div.social-icons > a div.row > div.col-lg-4 > div.social-icons > a
div.row > div.col-lg-4 > div.social-icons > a div.row > div.col-lg-4 > div.social-icons > a
div.row > div.col-lg-4 > div.social-icons > a div.row > div.col-lg-4 > div.social-icons > 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.

○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
●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.
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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.
●Document has a main landmark.
○`[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
○`<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.
○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.
○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.
A
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 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: "0+" - H3: "0+" - H3: "0+"
Got: 3 ≤2-char heading(s)
A+
Alt Text Quality
All 15 images OK
PASS
All 15 images OK
Info::
4 decorative image(s) correctly marked
Info::
11 image(s) with good alt text
15 images 11 good alt text 4 decorative
All images have appropriate alt text.
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "phone" should use type="tel" (currently type="text")
Field name "phone" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.
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+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 62 visible text node(s) render at >= 12 CSS pixels
PASS
All 62 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