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

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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 ModeNo Dark Mode Detected

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

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

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <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

Action

76% of visible text renders at >= 12 CSS px (58 below threshold)

REVIEW

76% of visible text renders at >= 12 CSS px (58 below threshold)

58 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 ("Example"); <span> 11.0px ("Example"); <span> 11.0px ("Example"); <span> 10.0px ("10"); <span> 10.0px ("11").

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title I Ching Online ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

A+

Heading Hierarchy

44 headings

PASS

44 headings

Single H1 present

H1 I Ching Online — a free online I Ching reading with three coins
H2 Cast your I Ching online reading now
H2 A three-thousand-year-old book about how situations change
H2 How an online I Ching reading works on I Ching Online
H3 Frame your question
H3 Toss three coins six times
H3 Read the hexagram
H3 Follow the change
H2 Everything a careful reading needs
H3 Faithful three-coin method
H3 Manual entry
H3 All changing lines
H3 64-hexagram library
H3 Private by default
H3 Optional AI reading
H3 What people use it for
H4 Decisions at a crossroads
H4 Relationships
H4 Creative work
H4 Daily reflection
H2 What a reading can look like
H3 A career change
H3 A strained friendship
H3 Starting a new project
H2 Explore every hexagram
H2 A personal reading, when you want one
H3 Single reading
H3 Starter pack
H3 Plus pack
H3 Deep pack
H3 Pro monthly
H3 Pro yearly
H2 Questions about I Ching Online and the I Ching
H3 What is the best free online I Ching reading?
H3 Is the I Ching accurate?
H3 Is the I Ching fortune telling or philosophy?
H3 How do I interpret my I Ching reading?
H3 What is the difference between the primary and the relating hexagram?
H3 What does it mean if I get no changing lines?
H3 Can I ask the I Ching about love, career or yes-or-no questions?
H3 Are my I Ching readings private?
H3 Can AI interpret the I Ching?
H3 How often can I ask the I Ching the same question?
H2 Your question deserves a quiet minute

A+

Heading Text Quality

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

PASS

All 44 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 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#iching-question	textarea	Your question (optional)	for/id

A+

Link & Button Quality

100 links, 8 buttons — all OK

PASS

100 links, 8 buttons — all OK

100 link(s) with descriptive text

100 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

108 links and buttons have descriptive text

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

1 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

7 icon(s) detected

PASS

7 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: I Ching Online

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name I Ching Online ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=pwa&utm_medium=install ✓Display Mode standalone ✓

Name I Ching Online Display Mode standalone Theme Color #294A42 Background Color #F7F4EE Icons 2 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+

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 I Ching Online — a…	18.30:1	3.0:1	#000000	#F2EFE9	Pass
h2 Cast your I Ching on…	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h2 A three-thousand-yea…	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h2 How an online I Chin…	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h2 Everything a careful…	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h2 What a reading can l…	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h2 Explore every hexagr…	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h2 A personal reading, …	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h2 Questions about I Ch…	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h2 Your question deserv…	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h3 Frame your question	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h3 Toss three coins six…	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h3 Read the hexagram	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h3 Follow the change	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h3 Faithful three-coin …	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h3 Manual entry	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h3 All changing lines	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h3 64-hexagram library	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h3 Private by default	19.13:1	3.0:1	#000000	#F7F4EE	Pass
h3 Optional AI reading	19.13:1	3.0:1	#000000	#F7F4EE	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 96/100 — 2 failing, 24 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
Your question does not affect the coin results. Standard commentary is matched … `div.flex > div.space-y-2 > div.flex > span`
0/500 `div.flex > div.space-y-2 > div.flex > span.tabular-nums`
Each toss adds one line, from the bottom up. Enter your own coin results `div.container > div.mx-auto > div.flex > p.text-sm`
One-time purchase `div > div.grid > div.rounded-xl > p.mt-2`
Credits do not expire `div > div.grid > div.rounded-xl > p.mt-2`
Best per-reading value among packs `div > div.grid > div.rounded-xl > p.mt-2`
For regular practice `div > div.grid > div.rounded-xl > p.mt-2`
Billed once a year `div > div.grid > div.rounded-xl > p.mt-2`
Readings are for reflection and entertainment, not medical, legal, financial or… `div.container > div.grid > div.col-span-full > p.max-w-sm`

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 `main.flex-1 > div.fixed > div.group > button.inline-flex`
support@ichingonline.pro `div.grid > div.col-span-full > div.flex > a.text-xs`

○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 are distinguishable without relying on color.

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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