Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 2 REVIEW 5 FIX

Tabindex Anti-Patterns

Action

0 positive, 336 -1-on-focusable

FIX

0 positive, 336 -1-on-focusable

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

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: #0f3e17

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 ✗

Mobile-Readable Font Sizes

98% of visible text renders at >= 12 CSS px (8 below threshold)

REVIEW

98% of visible text renders at >= 12 CSS px (8 below threshold)

8 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: <span> 11.0px ("Illustrative example"); <dt> 11.0px ("Mother born"); <dt> 11.0px ("Conceived"); <dt> 11.0px ("Lunar age"); <dt> 11.0px ("Lunar month").

Favicon & Branding

8 icon(s) detected

REVIEW

8 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

A+

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

31 headings

PASS

31 headings

Single H1 present

H1 Chinese Gender Predictor & Chinese Gender Calendar
H2 Try the Chinese gender predictor
H2 The full Chinese gender chart
H2 What is the Chinese gender predictor?
H2 How to use the Chinese gender predictor in 3 steps
H3 Enter the mother’s birth date
H3 Enter the conception date
H3 Read the Chinese gender chart result
H2 Everything a Chinese gender calendar needs, nothing it doesn’t
H3 Automatic lunar conversion
H3 “Only know the month” mode
H3 Full 336-cell Chinese gender chart
H3 Year calendar 1901–2100
H3 Private by design
H3 Print & save as PDF
H2 Popular ways families use the Chinese gender chart
H3 Baby-shower game
H3 Settling family debates
H3 Comparing other sites
H3 Learning the lunar calendar
H2 Questions the Chinese gender predictor answers
H2 Chinese gender predictor FAQ
H3 What is the Chinese gender calendar based on?
H3 What is lunar age?
H3 Why does my result change around late January or February?
H3 What if I only know the month I conceived?
H3 How are leap months handled?
H3 Does the chart change every year?
H3 Why do other websites show different results?
H3 Do you store my dates?
H2 Curious what the Chinese gender calendar says?

A+

Heading Text Quality

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

PASS

All 31 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

All 6 controls labeled

PASS

All 6 controls labeled

6 control(s) properly labeled

6 controls

6 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#birth	date	Mother’s date of birth	for/id
#conception	date	Estimated conception date	for/id
input	checkbox		none
select	select	Lunar age	none
select	select	Lunar month	none
#m-age	select	Lunar age	for/id

A+

Link & Button Quality

37 links, 355 buttons — all OK

PASS

37 links, 355 buttons — all OK

37 link(s) with descriptive text

37 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

392 links and buttons have descriptive text

A+

Form Input Types

6 form control(s) checked, no type mismatches

PASS

6 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

6 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+

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+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Chinese Gender Predictor

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Chinese Gender Predictor ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Chinese Gender Predictor Display Mode standalone Theme Color #0f3e17 Background Color #fffefc Icons 3 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

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 Chinese Gender Predi…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h2 Try the Chinese gend…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h2 The full Chinese gen…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h2 What is the Chinese …	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h2 How to use the Chine…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h2 Everything a Chinese…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h2 Popular ways familie…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h2 Questions the Chines…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h2 Chinese gender predi…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h2 Curious what the Chi…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h3 Enter the mother’s…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h3 Enter the conception…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h3 Read the Chinese gen…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h3 Automatic lunar conv…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h3 “Only know the mon…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h3 Full 336-cell Chines…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h3 Year calendar 1901�…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h3 Private by design	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h3 Print & save as PDF	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h3 Baby-shower game	20.83:1	3.0:1	#000000	#FFFEFC	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.

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 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
© 2026 Chinese Gender Predictor `footer.mt-24 > div.border-t > div.mx-auto > p`
LLMs.txt `footer.mt-24 > div.border-t > div.mx-auto > a.hover:text-[#0f3e17]`

These are opportunities to improve the legibility of your content.

○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

●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

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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

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

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