Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

18 PASS 3 REVIEW 3 FIX

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 ✗

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

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

8 landmarks

REVIEW

8 landmarks

<main> landmark present

4 <nav> landmark(s) found

1 of 4 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) 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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

90% of visible text renders at >= 12 CSS px (52 below threshold)

REVIEW

90% of visible text renders at >= 12 CSS px (52 below threshold)

52 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: <dt> 10.9px ("Year turns at"); <dt> 10.9px ("Months by"); <dt> 10.9px ("Day turns at"); <dt> 10.9px ("Hour by"); <b> 10.0px ("example").

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

62 headings

PASS

62 headings

Single H1 present

H1 Free BaZi Calculator
H2 Enter your birth details
H2 Complete Four Pillars chart with solar alignment
H2 What BaZi is, and why precision matters
H3 What it is
H3 Why precision matters
H3 How to start
H2 What your chart includes
H3 Four Pillars
H3 Day Master
H3 Ten Gods
H3 Five Elements
H3 Luck Pillars
H3 Compare
H2 How to calculate your BaZi chart
H3 Enter the birth date
H3 Enter the birth time
H3 Pick the birth city
H3 Read the chart
H2 Example chart
H3 Four Pillars
H3 Day Master
H3 Five Elements distribution
H3 Ten Gods
H3 Luck Pillars (大运)
H2 How we calculate
H3 True solar time
H3 Solar terms set year and month
H3 The five-element cycles
H2 More calculators
H3 Liu Yao
H3 Mei Hua Yi Shu
H3 Qi Men Dun Jia
H3 Zi Wei Dou Shu
H3 Chinese Almanac
H3 Learn
H2 What people use it for
H3 Learning BaZi
H3 Checking a hand-cast chart
H3 Uncertain birth hour
H3 Born abroad
H3 Comparing two charts
H3 Casting and date lookup
H2 Latest articles
H2 How the BaZi calculator works
H2 What is BaZi?
H2 What people use it for
H2 Calculator vs charting by hand
H2 The ten Day Masters
H2 The Ten Gods
H2 Five elements and strength
H2 Luck pillars and annual pillars
H2 Focused BaZi tools
H2 I Ching and other tools
H2 Learn to read your chart
H2 Glossary
H2 Conventions and comparisons
H2 Reading your first chart in five minutes
H2 Accuracy and testing
H2 Privacy and accounts
H2 Ready? Scroll up and calculate your chart.
H2 FAQ

A+

Heading Text Quality

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

PASS

All 62 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 13 controls labeled

PASS

All 13 controls labeled

13 control(s) properly labeled

13 controls

13 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
select	select	Year	none
select	select	Month	none
select	select	Day	none
select	select	Birth time	none
input	time	Exact time	aria-label
select	select	Traditional gender rule	none
input	input	Birth city	none
select	select	Time used for day & hour pillars	none
input	number	Expert: override UTC offset (minutes)	none
input	input	Reason (saved with the chart)	none
#mm-includes	checkbox	Show all 6Show less	for/id
#mm-method	checkbox	Show the full methodShow less	for/id
#mm-guide	checkbox	Read the full guideCollapse guide	for/id

A+

Link & Button Quality

167 links, 16 buttons — all OK

PASS

167 links, 16 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://www.geonames.org

166 link(s) with descriptive text

167 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.geonames.org	GeoNames	new tab	Add '(opens in new tab)' to text

182 links and buttons have descriptive text

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

https://www.geonames.org

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

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 "Birth city" should use type="search" (currently type="text")

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

A+

Form Input Quality

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

PASS

13 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

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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

Favicon & Branding

9 icon(s) detected

PASS

9 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: BaZi Calculator

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name BaZi Calculator ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name BaZi Calculator Display Mode standalone Theme Color #1d8a8a Background Color #f3f2f1 Icons 4 icon(s)

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 Free	17.18:1	3.0:1	#000000	#DEEBEA	Pass
h1 Calculator	17.40:1	3.0:1	#000000	#E1ECEB	Pass
h2 Enter your birth det…	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 Complete Four Pillar…	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 What BaZi is, and wh…	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 What your chart incl…	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 How to calculate you…	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 Example chart	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 How we calculate	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 More calculators	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 What people use it f…	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 Latest articles	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 How the BaZi calcula…	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 What is BaZi?	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 What people use it f…	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 Calculator vs charti…	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 The ten Day Masters	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 The Ten Gods	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 Five elements and st…	16.97:1	3.0:1	#000000	#E7E7E6	Pass
h2 Luck pillars and ann…	16.97:1	3.0:1	#000000	#E7E7E6	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 — 3 failing, 31 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
Calculate my chart `div.mx-auto > div > div.mt-7 > a.btn-teal`
EXAMPLE `div.mx-auto > div.window > div.window-bar > b.window-badge`
02 / YOU GET `div > div.showcase > div.showcase-col > p.showcase-num`
03 / THREE STEPS `div > div.showcase > div.showcase-col > p.showcase-num`
City not listed? Enter time zone and coordinates manually `section#birth-form > form.flex > div.relative > button.mt-1`
Calculate My Chart `div.no-print > section#birth-form > form.flex > button.inline-flex`
15S CHART PREVIEW `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
OVERVIEW `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
WHAT `div.grid-rule > div.p-6 > div.flex > span.font-mono`
WHY `div.grid-rule > div.p-6 > div.flex > span.font-mono`
HOW `div.grid-rule > div.p-6 > div.flex > span.font-mono`
INSIDE THE CHART `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
01 `div.grid > ol.steps > li > span.step-num`
02 `div.grid > ol.steps > li > span.step-num`
03 `div.grid > ol.steps > li > span.step-num`
04 `div.grid > ol.steps > li > span.step-num`
EXAMPLE `div.no-print > section#example > div.mx-auto > p.eyebrow`
● Metal `tr > td.rounded-xl > div.flex > span.inline-flex`
● Metal `tr > td.rounded-xl > div.flex > span.inline-flex`
▲ Wood `tbody > tr > th.w-24 > span.inline-flex`
■ Earth `tbody > tr > th.w-24 > span.inline-flex`
METHOD `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
MORE TOOLS `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
USE CASES `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
ARTICLES `div.no-print > section.scroll-mt-24 > div.mx-auto > p.eyebrow`
Install App `div.no-print > div.fixed > div.group > button.inline-flex`
Calculate my chart `footer.no-print > div.container > div.flex > a.btn-teal`
BaZi and the I Ching are traditional cultural systems. Results here are for stu… `div.container > div.grid > div.col-span-full > p.mt-4`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
methodology `section#how-it-works > div.mt-5 > p.leading-7 > a.text-primary`

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Install App `div.no-print > div.fixed > div.group > button.inline-flex`

○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

●Image elements have `[alt]` attributes

●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

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

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

●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

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

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

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

○Input buttons have discernible text.

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

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

○`<object>` elements have alternate text

○Skip links are focusable.

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

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