Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 4 REVIEW 5 FIX

Form Accessibility

Action

4 of 5 controls have issues

FIX

4 of 5 controls have issues

3 control(s) without accessible label

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

Got: <select name="industry">; <select name="kpi_type">; <select name="content_lang">

1 control(s) rely on placeholder only

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

Got: <input type="text" name="q">

1 control(s) properly labeled

5 controls

1 labeled

1 placeholder only

3 unlabeled

Control	Type	Label	Method
select	select	Language	aria-label
q	text	(Tìm đề án theo tiêu đề, mô tả...)	placeholder only
industry	select	(none)	none
kpi_type	select	(none)	none
content_lang	select	(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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://costdown.org/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://costdown.org/manifest.json

Manifest contains invalid JSON.

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

Hamburger menu detected (responsive design)

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)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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.

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

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (3 below threshold)

3 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: <div> 11.0px ("Discover"); <div> 11.0px ("Intelligence"); <div> 11.0px ("Workspace").

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 ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

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 Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Heading Hierarchy

11 headings

PASS

11 headings

Single H1 present

H1 Giảm Chi Phí Sản Xuất, Xây Trên Cải Tiến Thực Tế.
H2 Mạng lưới Costdown
H2 Cơ hội nổi bật
H3 Eliminating Tool-Change Scrap in CNC Machining Using FANUC Macro Offset→
H3 Reduced Size-Defect Rate by 66.6% via Contact Point Optimization on Lathe Chucks, Saving $45,017/Year→
H3 Replacing a Hardware Counter with a FANUC Macro Program: $1,060 Saved per Month→
H2 Costdown hoạt động thế nào
H3 Vấn đề → Chi phí hiện tại
H3 Can thiệp → Chi phí mới
H3 Tiết kiệm → Xác minh
H2 Sẵn sàng giảm chi phí sản xuất?

A+

Heading Text Quality

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

PASS

All 11 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+

Link & Button Quality

15 links, 3 buttons — all OK

PASS

15 links, 3 buttons — all OK

15 link(s) with descriptive text

15 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

18 links and buttons have descriptive text

A+

Form Input Types

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

PASS

Lang attribute set to "vi"

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

Got: vi

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+

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.

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 Giảm Chi Phí Sả…	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h2 Mạng lưới Costd…	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h2 Cơ hội nổi bậ…	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h2 Costdown hoạt đ�…	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h2 Sẵn sàng giảm c…	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h3 Vấn đề → Chi …	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h3 Can thiệp → Chi …	19.54:1	3.0:1	#000000	#F6F7F5	Pass
h3 Tiết kiệm → X�…	19.54:1	3.0:1	#000000	#F6F7F5	Pass
div Discover	20.77:1	4.5:1	#000000	#FDFEFD	Pass
span Projects	20.77:1	4.5:1	#000000	#FDFEFD	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
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
span Write	19.54:1	4.5:1	#000000	#F6F7F5	Pass
span cost	19.54:1	4.5:1	#000000	#F6F7F5	Pass
span down	19.54:1	4.5:1	#000000	#F6F7F5	Pass
span .org	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 90/100 — 2 failing, 21 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`
ĐỀ ÁN `div.grid > div.group > div.flex > span`
NHÀ MÁY ĐÃ ÁP DỤNG `div.grid > div.group > div.flex > span`
CHUYÊN GIA `div.grid > div.group > div.flex > span`
ĐÃ XÁC MINH `div.grid > div.group > div.flex > span`
CASE #14 `a.group > div.rounded-lg > div.flex > span.font-mono`
Current Cost `div.rounded-lg > div.grid > div > div.text-xs`
Potential Cost `div.rounded-lg > div.grid > div > div.text-xs`
Potential Saving `div.rounded-lg > div.grid > div > div.text-xs`
100.0% `div.rounded-lg > div.grid > div > div.font-mono`
CASE #5 `a.group > div.rounded-lg > div.flex > span.font-mono`
Current Cost `div.rounded-lg > div.grid > div > div.text-xs`
Potential Cost `div.rounded-lg > div.grid > div > div.text-xs`
Potential Saving `div.rounded-lg > div.grid > div > div.text-xs`
66.7% `div.rounded-lg > div.grid > div > div.font-mono`
CASE #2 `a.group > div.rounded-lg > div.flex > span.font-mono`
Current Cost `div.rounded-lg > div.grid > div > div.text-xs`
Potential Cost `div.rounded-lg > div.grid > div > div.text-xs`
Potential Saving `div.rounded-lg > div.grid > div > div.text-xs`
100.0% `div.rounded-lg > div.grid > div > div.font-mono`
01 `section.py-8 > div.grid > div > div.font-mono`
02 `section.py-8 > div.grid > div > div.font-mono`
03 `section.py-8 > div.grid > div > div.font-mono`

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Tất cả ngành Sản xuất công nghiệp Sản xuất - Cơ khí & Máy móc Sản xuất - Ô tô, … `section.py-8 > form.mb-8 > div.w-44 > select.w-full`
Tất cả KPI Chi phí vật liệu Chi phí nhân công Tỷ lệ phế phẩm (Scrap) Tỷ lệ làm … `section.py-8 > form.mb-8 > div.w-44 > select.w-full`
Tất cả ngôn ngữ Tiếng Việt English 简体中文繁體中文日本語 한국어 हिन्दी Deutsch Français Italia… `section.py-8 > form.mb-8 > div.w-44 > select.w-full`

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

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

●Heading elements appear in a sequentially-descending order

●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

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

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