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 5 REVIEW 4 FIX

Mobile-Readable Font Sizes

Action

67% of visible text renders at >= 12 CSS px (70 below threshold)

FIX

67% of visible text renders at >= 12 CSS px (70 below threshold)

70 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> 9.0px ("DECK · WAITE · 78 · UPRIGHT + REVERSED"); <span> 8.0px ("READER"); <span> 11.0px ("Mystic Poet · Mira Vale"); <span> 8.0px ("SPREAD"); <span> 11.0px ("Three Card").

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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

3 navigation landmark(s) detected

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 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

Landmark Structure

Action

9 landmarks

REVIEW

9 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

3 <nav> landmark(s) found

All <nav> elements are properly labeled

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Free AI Tarot Reading & Rider-Waite Cards | TAROTAI.CHAT ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

11 icon(s) detected

REVIEW

11 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 Missing

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

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

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Free AI Tarot Reading

1.12:1

#000000

#12120F

needs 3.0:1 (large text)

32px · above the fold · over background image/gradient

h2 Frame your question, draw cards online, …

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 When navigating uncertainty, find clarit…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How to do an online tarot reading on TAR…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Pricing

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AI tarot interpretations, classic spread…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 One spread, six distinct Tarot AI perspe…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Questions seekers bring to TAROTAI.CHAT.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Frequently Asked Questions

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to begin.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Four Steps to Your AI Tarot Reading

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Login & Free Daily Credits

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Monthly Subscription Plans

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 One-Time Purchase Plans

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

title Free AI Tarot Reading & Rider-Waite Card…

1.02:1

#000000

#030405

needs 4.5:1 (normal text)

16px · top of page (header area)

span TAROTAI

1.02:1

#000000

#030405

needs 4.5:1 (normal text)

16px · top of page (header area)

span CHAT

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a How it works

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Blog

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Pricing

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Free AI Tarot Readin…	1.12:1	3.0:1	#000000	#12120F	Fail
h2 Frame your question,…	1.00:1	3.0:1	#000000	#000000	Fail
h2 When navigating unce…	1.00:1	3.0:1	#000000	#000000	Fail
h2 How to do an online …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Pricing	1.00:1	3.0:1	#000000	#000000	Fail
h2 AI tarot interpretat…	1.00:1	3.0:1	#000000	#000000	Fail
h2 One spread, six dist…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Questions seekers br…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Frequently Asked Que…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Ready to begin.	1.00:1	3.0:1	#000000	#000000	Fail
h3 Four Steps to Your A…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Login & Free Daily C…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Monthly Subscription…	1.00:1	3.0:1	#000000	#000000	Fail
h3 One-Time Purchase Pl…	1.00:1	3.0:1	#000000	#000000	Fail
title Free AI Tarot Readin…	1.02:1	4.5:1	#000000	#030405	Fail
span TAROTAI	1.02:1	4.5:1	#000000	#030405	Fail
span CHAT	1.00:1	4.5:1	#000000	#000000	Fail
a How it works	1.00:1	4.5:1	#000000	#000000	Fail
a Blog	1.00:1	4.5:1	#000000	#000000	Fail
a Pricing	1.00:1	4.5:1	#000000	#000000	Fail

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+

Heading Hierarchy

23 headings

PASS

23 headings

Single H1 present

H1 Free AI Tarot ReadingTAROTAI.CHAT
H2 Frame your question, draw cards online, and begin an in-depth AI tarot reading.
H2 When navigating uncertainty, find clarity on TAROTAI.CHAT
H2 How to do an online tarot reading on TAROTAI.CHAT
H3 Four Steps to Your AI Tarot Reading
H4 Frame your question
H4 Draw cards online yourself
H4 Receive AI tarot insights and ask follow-ups
H4 Draw a free daily card
H3 Login & Free Daily Credits
H2 Pricing
H3 Monthly Subscription Plans
H4 Plus
H4 Pro
H3 One-Time Purchase Plans
H4 Starter
H4 Standard
H4 Premium
H2 AI tarot interpretations, classic spreads, and the complete 78 Rider-Waite deck.
H2 One spread, six distinct Tarot AI perspectives.
H2 Questions seekers bring to TAROTAI.CHAT.
H2 Frequently Asked Questions
H2 Ready to begin.

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 30 images OK

PASS

All 30 images OK

17 decorative image(s) correctly marked

13 image(s) with good alt text

30 images 13 good alt text 17 decorative

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <textarea id="question-input">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#question-input	textarea	(e.g.: How is my career development direction?)	placeholder only

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

A+

Link & Button Quality

31 links, 26 buttons — all OK

PASS

31 links, 26 buttons — all OK

31 link(s) with descriptive text

31 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

57 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

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+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 23 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
TAROTAI.CHAT PROVIDES SYMBOLIC AI TAROT READINGS INTENDED FOR PERSONAL CONTEMPL… `div.dark > div.relative > section#faq > p.mt-6`
© 2025 TAROTAI.CHAT. All rights reserved. `div.relative > footer.border-t > div.mx-auto > p.text-[11px]`

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

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

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

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

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

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