Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

20 PASS 3 REVIEW 1 FIX

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 ✗

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404: This page could not be found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

10 icon(s) detected

REVIEW

10 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

A+

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

Heading Hierarchy

14 headings, 1 skip(s)

PASS

14 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H1 Manufacturing Cost Reduction — Stop Solving What's Already Been Solved.
H3 Someone has already paid to learn your problem skipped
H3 How many plants can you help in a year?
H3 You once cut the cost of a process. Where is the proof?
H2 Featured Opportunities
H3 CNC Turning Cost Reduction: A Fourth Tool Cuts Machine Time — saving $14,415/year→
H3 How to Eliminate Tool-Change Scrap in CNC Turning with FANUC Custom Macro B. Save $30,021/year→
H3 How a 3-Point Collet Contact Design Cut Lathe Length Defects by 66.6% - Saving $45,070 a Year→
H3 Replacing Hardware Counters with a FANUC Macro Program: Saving $12,720 a Year→
H2 How Costdown Works
H3 Problem → Current Cost
H3 Intervention → New Cost
H3 Saving → Validation
H2 Ready to reduce your production costs?

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

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 7 controls labeled

PASS

All 7 controls labeled

7 control(s) properly labeled

7 controls

7 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
select	select	Language	aria-label
q	text	Search proposals by title, description...	aria-label
industry	select	All industries	aria-label
kpi_type	select	All KPI Types	aria-label
sort	select	Sort	aria-label
content_lang	select	All languages	aria-label
select	select	Language	aria-label

A+

Link & Button Quality

25 links, 3 buttons — all OK

PASS

25 links, 3 buttons — all OK

25 link(s) with descriptive text

25 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

28 links and buttons have descriptive 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

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

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

PASS

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

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

A+

Mobile-Readable Font Sizes

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

PASS

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

All text uses legible mobile font sizes (>= 12 CSS px)

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Costdown.org

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Costdown.org ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Costdown.org Display Mode standalone Theme Color #090b0c Background Color #090b0c Icons 3 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

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

A+

Dark Mode Support

Full dark mode support

PASS

Full dark mode support

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light dark

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

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

Dark Mode✓ Dark Mode Supported

color-scheme meta light dark ✓Dark theme-color #f6f7f5 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

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

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Manufacturing Cost R…	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h2 Featured Opportuniti…	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h2 How Costdown Works	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h2 Ready to reduce your…	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h3 Someone has already …	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h3 How many plants can …	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h3 You once cut the cos…	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h3 Problem → Current …	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h3 Intervention → New…	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h3 Saving → Validatio…	19.54:1	3.0:1	#000000	#F6F7F5	Pass
a Skip to main content	20.77:1	4.5:1	#000000	#FDFEFD	Pass
div Discover	20.77:1	4.5:1	#000000	#FDFEFD	Pass
span Projects	19.54:1	4.5:1	#000000	#F6F7F5	Pass
span People	19.54:1	4.5:1	#000000	#F6F7F5	Pass
div Intelligence	19.54:1	4.5:1	#000000	#F6F7F5	Pass
span Calculator	19.54:1	4.5:1	#000000	#F6F7F5	Pass
span Guides	19.54:1	4.5:1	#000000	#F6F7F5	Pass
div Workspace	19.54:1	4.5:1	#000000	#F6F7F5	Pass
span My Projects	19.54:1	4.5:1	#000000	#F6F7F5	Pass
span My Proposals	19.54:1	4.5:1	#000000	#F6F7F5	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.

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 22 passed

PASS

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
cost `header.sticky > a.inline-flex > span.brand-wordmark > span`
down `header.sticky > a.inline-flex > span.brand-wordmark > span`
$1,201 / mo41.6% `div.rounded-lg > div.grid > div > div.font-mono`
41.6% `div.grid > div > div.font-mono > span.ml-1.5`
~8 days `div.rounded-lg > div.grid > div > div.font-mono`
$14,415 `div.rounded-lg > div.grid > div > div.font-mono`
$2,502 / mo83.3% `div.rounded-lg > div.grid > div > div.font-mono`
83.3% `div.grid > div > div.font-mono > span.ml-1.5`
~2 days `div.rounded-lg > div.grid > div > div.font-mono`
$30,021 `div.rounded-lg > div.grid > div > div.font-mono`
$3,756 / mo61.1% `div.rounded-lg > div.grid > div > div.font-mono`
61.1% `div.grid > div > div.font-mono > span.ml-1.5`
~1 days `div.rounded-lg > div.grid > div > div.font-mono`
$45,070 `div.rounded-lg > div.grid > div > div.font-mono`
$1,060 / mo100% `div.rounded-lg > div.grid > div > div.font-mono`
100% `div.grid > div > div.font-mono > span.ml-1.5`
~8 days `div.rounded-lg > div.grid > div > div.font-mono`
$12,720 `div.rounded-lg > div.grid > div > div.font-mono`

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
Someone has already paid to learn your problem `main#main > div.grid > div.rounded-lg > h3.text-h4`

These are opportunities to improve keyboard navigation in your application.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

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

●Select elements have associated label elements.

●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

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

○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

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

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

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