Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 5 REVIEW 5 FIX

Mobile-Readable Font Sizes

Action

35% of visible text renders at >= 12 CSS px (85 below threshold)

FIX

35% of visible text renders at >= 12 CSS px (85 below threshold)

85 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <a> 10.0px ("tools"); <a> 10.0px ("about"); <a> 10.0px ("privacy"); <div> 10.0px ("FREE · OFFLINE · NO TRACKING"); <span> 9.0px ("tools").

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

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

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

Got: #0a0a0c

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

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

Detection limited to meta tags and inline styles.

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.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

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

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

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

Favicon & Branding

7 icon(s) detected

REVIEW

7 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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

PWA Depth

3 PWA signal(s) surfaced

REVIEW

3 PWA signal(s) surfaced

Service worker registration detected

The page calls `navigator.serviceWorker.register(...)` -- the prerequisite for any real PWA capability (offline support, push notifications, background sync, Cache API). This is a positive signal; whether the registered worker actually does what you want is a separate question (check DevTools > Application > Service Workers).

Manifest declares display="browser" -- no PWA UX

When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

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

h1 tools for musicians

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

32px · above the fold

h2 Tools

1.04:1

#000000

#070709

needs 3.0:1 (large text)

24px · mid-page

h2 Why this exists

1.04:1

#000000

#070709

needs 3.0:1 (large text)

24px · bottom of viewport

h3 tuner

1.04:1

#000000

#070709

needs 3.0:1 (large text)

19px · mid-page

h3 flactest

1.04:1

#000000

#070709

needs 3.0:1 (large text)

19px · bottom of viewport

h3 metronome

1.04:1

#000000

#070709

needs 3.0:1 (large text)

19px · bottom of viewport

h3 chords

1.04:1

#000000

#070709

needs 3.0:1 (large text)

19px · bottom of viewport

h3 practice

1.04:1

#000000

#070709

needs 3.0:1 (large text)

19px · bottom of viewport

h3 split

1.04:1

#000000

#070709

needs 3.0:1 (large text)

19px · bottom of viewport

h3 convert

1.04:1

#000000

#070709

needs 3.0:1 (large text)

19px · bottom of viewport

h3 changes

1.04:1

#000000

#070709

needs 3.0:1 (large text)

19px · bottom of viewport

h3 sing

1.04:1

#000000

#070709

needs 3.0:1 (large text)

19px · bottom of viewport

title 440hz.app — Free Tools for Musicians

1.06:1

#000000

#0A0A0C

needs 4.5:1 (normal text)

16px · top of page (header area)

div 440hz

1.06:1

#000000

#09090B

needs 4.5:1 (normal text)

16px · top of page (header area)

span .app

1.06:1

#000000

#09090B

needs 4.5:1 (normal text)

16px · top of page (header area)

a tools

1.06:1

#000000

#09090B

needs 4.5:1 (normal text)

16px · top of page (header area)

a about

1.06:1

#000000

#09090B

needs 4.5:1 (normal text)

16px · above the fold

a privacy

1.06:1

#000000

#09090B

needs 4.5:1 (normal text)

16px · above the fold

div FREE · OFFLINE · NO TRACKING

1.06:1

#000000

#09090B

needs 4.5:1 (normal text)

16px · above the fold

span and music lovers.

1.06:1

#000000

#09090B

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 tools for musicians	1.06:1	3.0:1	#000000	#09090B	Fail
h2 Tools	1.04:1	3.0:1	#000000	#070709	Fail
h2 Why this exists	1.04:1	3.0:1	#000000	#070709	Fail
h3 tuner	1.04:1	3.0:1	#000000	#070709	Fail
h3 flactest	1.04:1	3.0:1	#000000	#070709	Fail
h3 metronome	1.04:1	3.0:1	#000000	#070709	Fail
h3 chords	1.04:1	3.0:1	#000000	#070709	Fail
h3 practice	1.04:1	3.0:1	#000000	#070709	Fail
h3 split	1.04:1	3.0:1	#000000	#070709	Fail
h3 convert	1.04:1	3.0:1	#000000	#070709	Fail
h3 changes	1.04:1	3.0:1	#000000	#070709	Fail
h3 sing	1.04:1	3.0:1	#000000	#070709	Fail
title 440hz.app — Free T…	1.06:1	4.5:1	#000000	#0A0A0C	Fail
div 440hz	1.06:1	4.5:1	#000000	#09090B	Fail
span .app	1.06:1	4.5:1	#000000	#09090B	Fail
a tools	1.06:1	4.5:1	#000000	#09090B	Fail
a about	1.06:1	4.5:1	#000000	#09090B	Fail
a privacy	1.06:1	4.5:1	#000000	#09090B	Fail
div FREE · OFFLINE · N…	1.06:1	4.5:1	#000000	#09090B	Fail
span and music lovers.	1.06:1	4.5:1	#000000	#09090B	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 — 2 failing, 9 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.

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
TOOLS `section.hero > div.hero-meta > div.meta-item > span.meta-label`
TRACKERS `section.hero > div.hero-meta > div.meta-item > span.meta-label`
FREE `section.hero > div.hero-meta > div.meta-item > span.meta-label`
/01 `a.tool-card > div.tool-body > div.tool-header > div.tool-idx`
GUITAR `a.tool-card > div.tool-body > div.tool-feats > span`
BASS `a.tool-card > div.tool-body > div.tool-feats > span`
UKULELE `a.tool-card > div.tool-body > div.tool-feats > span`
VIOLIN `a.tool-card > div.tool-body > div.tool-feats > span`
DROP D `a.tool-card > div.tool-body > div.tool-feats > span`
DADGAD `a.tool-card > div.tool-body > div.tool-feats > span`
/02 `a.tool-card > div.tool-body > div.tool-header > div.tool-idx`
FLAC `a.tool-card > div.tool-body > div.tool-feats > span`
WAV `a.tool-card > div.tool-body > div.tool-feats > span`
320K `a.tool-card > div.tool-body > div.tool-feats > span`
128K `a.tool-card > div.tool-body > div.tool-feats > span`
64K `a.tool-card > div.tool-body > div.tool-feats > span`
16K `a.tool-card > div.tool-body > div.tool-feats > span`
/03 `a.tool-card > div.tool-body > div.tool-header > div.tool-idx`
TAP TEMPO `a.tool-card > div.tool-body > div.tool-feats > span`
SUBDIVISIONS `a.tool-card > div.tool-body > div.tool-feats > span`
1-12 BEATS `a.tool-card > div.tool-body > div.tool-feats > span`
OFFLINE `a.tool-card > div.tool-body > div.tool-feats > span`
/04 `a.tool-card > div.tool-body > div.tool-header > div.tool-idx`
TRIADS `a.tool-card > div.tool-body > div.tool-feats > span`
7THS `a.tool-card > div.tool-body > div.tool-feats > span`
SUS `a.tool-card > div.tool-body > div.tool-feats > span`
12 KEYS `a.tool-card > div.tool-body > div.tool-feats > span`
MAJOR `a.tool-card > div.tool-body > div.tool-feats > span`
MINOR `a.tool-card > div.tool-body > div.tool-feats > span`
/05 `a.tool-card > div.tool-body > div.tool-header > div.tool-idx`
MIC `a.tool-card > div.tool-body > div.tool-feats > span`
REAL-TIME `a.tool-card > div.tool-body > div.tool-feats > span`
ANY KEY `a.tool-card > div.tool-body > div.tool-feats > span`
TRIADS `a.tool-card > div.tool-body > div.tool-feats > span`
SUS `a.tool-card > div.tool-body > div.tool-feats > span`
7THS `a.tool-card > div.tool-body > div.tool-feats > span`
/06 `a.tool-card > div.tool-body > div.tool-header > div.tool-idx`
CUE `a.tool-card > div.tool-body > div.tool-feats > span`
FLAC `a.tool-card > div.tool-body > div.tool-feats > span`
WAV `a.tool-card > div.tool-body > div.tool-feats > span`
MP3 `a.tool-card > div.tool-body > div.tool-feats > span`
ZIP `a.tool-card > div.tool-body > div.tool-feats > span`
/07 `a.tool-card > div.tool-body > div.tool-header > div.tool-idx`
FLAC `a.tool-card > div.tool-body > div.tool-feats > span`
WAV `a.tool-card > div.tool-body > div.tool-feats > span`
MP3 `a.tool-card > div.tool-body > div.tool-feats > span`
BATCH `a.tool-card > div.tool-body > div.tool-feats > span`
PARALLEL `a.tool-card > div.tool-body > div.tool-feats > span`
/08 `a.tool-card > div.tool-body > div.tool-header > div.tool-idx`
GENERATOR `a.tool-card > div.tool-body > div.tool-feats > span`
LOOP `a.tool-card > div.tool-body > div.tool-feats > span`
TEMPO `a.tool-card > div.tool-body > div.tool-feats > span`
CLICK `a.tool-card > div.tool-body > div.tool-feats > span`
/09 `a.tool-card > div.tool-body > div.tool-header > div.tool-idx`
PITCH DETECTION `a.tool-card > div.tool-body > div.tool-feats > span`
ALL VOICES `a.tool-card > div.tool-body > div.tool-feats > span`
INTERVALS `a.tool-card > div.tool-body > div.tool-feats > span`
CHROMATIC `a.tool-card > div.tool-body > div.tool-feats > span`

These are opportunities to improve the legibility of your content.

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

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

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

○`[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 input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

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

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

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

12 headings

PASS

12 headings

Single H1 present

H1 tools for musiciansand music lovers.
H2 Tools
H3 tuner.
H3 flactest.
H3 metronome.
H3 chords.
H3 practice.
H3 split.
H3 convert.
H3 changes.
H3 sing.
H2 Why this exists

A+

Heading Text Quality

All 12 heading(s) have substantive, well-formed text

PASS

All 12 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

16 links, 0 buttons — all OK

PASS

16 links, 0 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://buymeacoffee.com/vladimirj.dev

15 link(s) with descriptive text

16 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://buymeacoffee.com/vladimirj.dev	buy me a coffee	new tab	Add '(opens in new tab)' to text

15 links and buttons have descriptive text

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

https://buymeacoffee.com/vladimirj.dev

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

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

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

PASS

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

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

Web Manifest

Valid manifest

PASS

Valid manifest

Name present: 440hz.app — Tools for Musicians

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name 440hz.app — Tools for Musicians ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode browser ✗

Name 440hz.app — Tools for Musicians Display Mode browser Theme Color #0A0A0C Background Color #0A0A0C Icons 3 icon(s)

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

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

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

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