http://wonk.sytes.net/76s/pratka/index.html

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 3 REVIEW 10 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Alt Text Quality

Action

56 of 57 images have issues

FIX

56 of 57 images have issues

56 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

54 image-in-link without alt text

An image inside a link with no alt creates an empty link.

1 image(s) with good alt text

57 images 1 good alt text 56 missing

Issue	Count
missing	56 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Document Language

Action

Missing <html lang> attribute (WCAG 3.1.1)

FIX

Missing <html lang> attribute (WCAG 3.1.1)

Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

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 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

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

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 ✗

Lighthouse Accessibility Audits

Action

Score 69/100 — 4 failing, 7 passed

FIX

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.

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
Takaisin pääsivulle `tbody > tr > td > h3`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

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
td > center > a > img `td > center > a > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > center > a > img `td > center > a > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > center > a > img `td > center > a > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > center > a > img `td > center > a > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > center > a > img `td > center > a > img`
td > a > center > img `td > a > center > img`
td > center > a > img `td > center > a > img`
td > a > center > img `td > a > center > img`
td > center > a > img `td > center > a > img`
td > a > center > img `td > a > center > img`
td > center > a > img `td > center > a > img`
td > center > a > img `td > center > a > img`
td > center > a > img `td > center > a > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > center > a > img `td > center > a > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
a > center > p > img `a > center > p > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
td > a > center > img `td > a > center > img`
tr > td > center > img `tr > td > center > img`
tr > td > center > img `tr > td > center > img`

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

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●Links are distinguishable without relying on color.

●Links have a discernible name

●Touch targets have sufficient size and spacing.

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

○`[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 a valid value for its `[lang]` attribute

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

Heading Hierarchy

4 headings, 1 skip(s)

REVIEW

4 headings, 1 skip(s)

Multiple H1 headings (3 found)

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

Heading level skipped: H1 → H3 (missing H2)

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

H1 MYYDÄÄN!
H1 EIKÄ MYYDÄKÄÄN! duplicate H1
H1 2015 duplicate H1
H3 Takaisin pääsivulle skipped

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

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

48 issue(s) across 138 links and 0 buttons

REVIEW

48 issue(s) across 138 links and 0 buttons

48 link(s) with no accessible text

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

Got: a (#23 on page); a (#26 on page); a (#44 on page); a (#52 on page); a (#55 on page); a (#68 on page); a (#74 on page); a (#77 on page); a (#97 on page); a (#103 on page) (+38 more)

90 link(s) with descriptive text

138 links

48 empty

0 generic text

0 new tab

0 empty buttons

Text	Issue	Suggested Fix
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
Siinä se nyt on! Vuosmalli 20…	img no alt	Add alt attribute to the image
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
Eräs kaiffarikin pysähtyi pa…	img no alt	Add alt attribute to the image
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
Tosta kuvasta voi huomata myö…	img no alt	Add alt attribute to the image
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
Viikonloppuna on vaan vähän …	img no alt	Add alt attribute to the image
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
Katteita lukuunottamatta saati…	img no alt	Add alt attribute to the image
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
Kuten jo aijemmin todettu niin…	img no alt	Add alt attribute to the image
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
Mulla ei ihan kauhean suurta l…	img no alt	Add alt attribute to the image
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
Uuden iskarin hintelyys ei juu…	img no alt	Add alt attribute to the image
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
Siniset ois tietysti olleet tu…	img no alt	Add alt attribute to the image
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
Kun olin tuon edellisen päivi…	img no alt	Add alt attribute to the image
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
2015 22.4.2015 Talvi oli ja …	img no alt	Add alt attribute to the image
(empty)	empty	Add link text or aria-label

90 links and buttons have descriptive text

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

a (#23 on page); a (#26 on page); a (#44 on page); a (#52 on page); a (#55 on page); a (#68 on page); a (#74 on page); a (#77 on page); a (#97 on page); a (#103 on page) (+38 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

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 1 pass AA only

p Otin tulpan irti ja tuuttasin pytyn täy…

2.92:1

#000000

#5D5652

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

p Konepuoli nyt siis vähän surkeana, mut…

3.09:1

#000000

#605A55

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

p Kuten todettua, en tiedä näistä vehke…

1.39:1

#000000

#2A2522

needs 4.5:1 (normal text)

16px · above the fold

p Plusmiinusnollaksi laskettakoon toi paka…

1.46:1

#000000

#2F2828

needs 4.5:1 (normal text)

16px · above the fold

p Siinä oikeastaan kaikki tässä vaihees…

1.42:1

#000000

#2E2627

needs 4.5:1 (normal text)

16px · above the fold

b Torstai.8.2013

1.40:1

#000000

#2A2625

needs 3.0:1 (large text)

16px · above the fold

a Olen aina tallin lähistöltä kulkiessa…

1.41:1

#000000

#2B2624

needs 4.5:1 (normal text)

16px · mid-page

a Iltasella lähdin sitten tyttiksen kanss…

1.78:1

#000000

#59292A

needs 4.5:1 (normal text)

16px · mid-page

p Eräs kaiffarikin pysähtyi paikalla (no…

2.44:1

#000000

#7E352F

needs 4.5:1 (normal text)

16px · mid-page

p Jonkun ajan päästä remonttiapulainenk…

2.33:1

#000000

#773434

needs 4.5:1 (normal text)

16px · mid-page

p Eikä siinä kauaa mennyt kun homma alko…

1.46:1

#000000

#422022

needs 4.5:1 (normal text)

16px · mid-page

p Vaikka mulla olikin suunnitelmissa väh�…

1.65:1

#000000

#30323C

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

3 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 MYYDÄÄN!	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Prätkä	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a TÄSTÄ VIIMEISIMPÄ…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
b Tiistai 27.8.2013	21.00:1	3.0:1	#000000	#FFFFFF	Pass
p Olen tässä pitkä�…	15.61:1	4.5:1	#000000	#DEDEDE	Pass
p Kuten sanottu, en ti…	17.30:1	4.5:1	#000000	#E9E9E9	Pass
b Keskiviikko 28.8.201…	15.02:1	3.0:1	#000000	#DADADA	Pass
p Siinä se nyt on! Vu…	5.12:1	4.5:1	#000000	#827C7B	Pass
p Otin tulpan irti ja …	2.92:1	4.5:1	#000000	#5D5652	Fail
p Konepuoli nyt siis v…	3.09:1	4.5:1	#000000	#605A55	Fail
p Kuten todettua, en t…	1.39:1	4.5:1	#000000	#2A2522	Fail
p Plusmiinusnollaksi l…	1.46:1	4.5:1	#000000	#2F2828	Fail
p Siinä oikeastaan ka…	1.42:1	4.5:1	#000000	#2E2627	Fail
b Torstai.8.2013	1.40:1	3.0:1	#000000	#2A2625	Fail
a Olen aina tallin lä…	1.41:1	4.5:1	#000000	#2B2624	Fail
a Iltasella lähdin si…	1.78:1	4.5:1	#000000	#59292A	Fail
p Eräs kaiffarikin py…	2.44:1	4.5:1	#000000	#7E352F	Fail
p Jonkun ajan pääst�…	2.33:1	4.5:1	#000000	#773434	Fail
p Eikä siinä kauaa m…	1.46:1	4.5:1	#000000	#422022	Fail
p Vaikka mulla olikin …	1.65:1	4.5:1	#000000	#30323C	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.

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 2 all-caps heading(s)

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+

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 237 visible text node(s) render at >= 12 CSS pixels

PASS

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