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

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

12 landmarks

REVIEW

12 landmarks

<main> landmark present

6 <nav> landmark(s) found

5 of 6 <nav> elements are unlabeled

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

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

Tap Target Adequacy

1 tap target(s) too small or too close together

REVIEW

1 tap target(s) too small or too close together

1 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

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

REVIEW

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

27 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 ("50% OFF"); <span> 9.0px ("50% OFF"); <span> 10.0px ("Free"); <span> 10.0px ("Free"); <span> 10.0px ("Pro").

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 Page Not Found – AI Text Watermark Remover ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 89/100 — 3 failing, 26 passed

REVIEW

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
Cleans invisible Unicode locally in your browser. Hidden marks vary by source. `div.flex > div.px-3 > div.relative > p.pointer-events-none`
0 characters · 0 words `div.px-3 > div.relative > div.pointer-events-none > span.whitespace-nowrap`
Paste `div.border-t > div.flex > div.flex > button.inline-flex`
Clear `div.border-t > div.flex > div.flex > button.shrink-0`
Try a Sample `div.border-t > div.flex > div.flex > button.inline-flex`
Claude `main#top > section.section-wash > div.mx-auto > span.font-display`
ChatGPT `main#top > section.section-wash > div.mx-auto > span.font-display`
Gemini `main#top > section.section-wash > div.mx-auto > span.font-display`
Docs `main#top > section.section-wash > div.mx-auto > span.font-display`
CMS `main#top > section.section-wash > div.mx-auto > span.font-display`
Email `main#top > section.section-wash > div.mx-auto > span.font-display`
3 hidden · Markdown noise `div.mt-6 > div.overflow-hidden > div.mb-4 > span.text-xs`
Visible text intact `div.mt-6 > div.overflow-hidden > div.mb-4 > span.text-xs`
01 `div.mx-auto > ol.mt-12 > li.rounded-2xl > div.flex`
02 `div.mx-auto > ol.mt-12 > li.rounded-2xl > div.flex`
03 `div.mx-auto > ol.mt-12 > li.rounded-2xl > div.flex`
FEATURES `section#what > div.mx-auto > div.mx-auto > p.section-label`
DEFINITION `main#top > section#definition > div.mx-auto > p.section-label`
SOURCES `section#sources > div.mx-auto > div.mx-auto > p.section-label`
Anthropic, How Claude’s text watermark works (14 Aug 2026) `blockquote.rounded-2xl > footer.mt-4 > cite > a.font-semibold`
Unicode Standard, General Punctuation (U+2000 block) `blockquote.rounded-2xl > footer.mt-4 > cite > a.font-semibold`
CommonMark spec `section#sources > div.mx-auto > p.mt-5 > a.font-semibold`
USE CASES `section#cases > div.mx-auto > div.mx-auto > p.section-label`
01 `div.mt-14 > article.grid > div.flex > div.flex`
Open the tool → `div.mt-14 > article.grid > div.flex > a.mt-6`
02 `div.mt-14 > article.grid > div.flex > div.flex`
Open the tool → `div.mt-14 > article.grid > div.flex > a.mt-6`
03 `div.mt-14 > article.grid > div.flex > div.flex`
Open the tool → `div.mt-14 > article.grid > div.flex > a.mt-6`
04 `div.mt-14 > article.grid > div.flex > div.flex`
Open the tool → `div.mt-14 > article.grid > div.flex > a.mt-6`
TESTIMONIALS `section#testimonials > div.mx-auto > div.mx-auto > p.section-label`
SEO & CMS `div.mx-auto > div.mt-12 > article.flex > p.text-xs`
Publishing `div.mx-auto > div.mt-12 > article.flex > p.text-xs`
Docs & support `div.mx-auto > div.mt-12 > article.flex > p.text-xs`
GUIDES `section.bg-white > div.mx-auto > div.mx-auto > p.section-label`
Claude guide → `div.mx-auto > div.mt-12 > a.group > span.mt-5`
ChatGPT guide → `div.mx-auto > div.mt-12 > a.group > span.mt-5`
Gemini guide → `div.mx-auto > div.mt-12 > a.group > span.mt-5`
View all tools → `section.bg-white > div.mx-auto > div.mt-6 > a.text-sm`
BLOG `section.bg-white > div.mx-auto > div.mt-12 > p.section-label`
Read more → `div.mt-5 > a.group > div.flex > span.mt-4`
Read more → `div.mt-5 > a.group > div.flex > span.mt-4`
Monthly `div.px-4 > div.mx-auto > div.mx-auto > button.relative`
−50% `div.mx-auto > div.mx-auto > button.relative > span.rounded-full`
Credit Packs `div.px-4 > div.mx-auto > div.mx-auto > button.relative`
CREDITS / MO `article.relative > div.mt-4 > div.rounded-xl > div.text-[10px]`
WORDS / MO `article.relative > div.mt-4 > div.rounded-xl > div.text-[10px]`
CREDITS / MO `article.relative > div.mt-4 > div.rounded-xl > div.text-[10px]`
WORDS / MO `article.relative > div.mt-4 > div.rounded-xl > div.text-[10px]`
CREDITS / MO `article.relative > div.mt-4 > div.rounded-xl > div.text-[10px]`
WORDS / MO `article.relative > div.mt-4 > div.rounded-xl > div.text-[10px]`
Available payment methods are confirmed on the Stripe Checkout page. `div.px-4 > div.mx-auto > div.mt-14 > p.mt-4`
support@aitextwatermarkremover.com `div.mx-auto > div.mt-14 > p.mt-3 > a.font-semibold`
ABOUT US `section#about > div.mx-auto > div.text-center > p.section-label`
PRODUCT `div.mx-auto > div.grid > div > div.text-xs`
TOOLS `div.mx-auto > div.grid > div > div.text-xs`
MODEL GUIDES `div.mx-auto > div.grid > div > div.text-xs`
About Us `footer.border-t > div.mx-auto > nav.mt-12 > a.hover:text-ink`
Contact `footer.border-t > div.mx-auto > nav.mt-12 > a.hover:text-ink`
Privacy `footer.border-t > div.mx-auto > nav.mt-12 > a.hover:text-ink`
Terms `footer.border-t > div.mx-auto > nav.mt-12 > a.hover:text-ink`
Refund Policy `footer.border-t > div.mx-auto > nav.mt-12 > a.hover:text-ink`
Email Support `footer.border-t > div.mx-auto > nav.mt-12 > a.hover:text-ink`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.sticky > header.border-b > div.mx-auto > a.flex `div.sticky > header.border-b > div.mx-auto > a.flex`

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Install AI Text Watermark Remover as an app `body.min-h-screen > div.fixed > div.group > button.inline-flex`

These items highlight common accessibility best practices.

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

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

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

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

●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

●Elements with visible text labels have matching accessible names.

●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

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

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

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

A+

Heading Hierarchy

37 headings

PASS

37 headings

Single H1 present

H1 AI Text Watermark Remover
H2 Before noise. After clarity.
H2 Why clean your text?
H3 Privacy first
H3 Surgical precision
H3 Formatting integrity
H2 How it works
H3 Paste your draft
H3 Inspect what is hidden
H3 Clean or rewrite
H2 Built for real paste workflows
H3 Invisible character detection
H3 Markdown cleaner
H3 Text watermark remover
H3 AI Humanizer
H2 What is an AI text watermark remover?
H2 How the three paste traces differ
H2 Where teams use it
H3 SEO & content ops
H3 Editorial teams
H3 Agencies & freelancers
H3 Technical writers
H2 What people say
H2 Model-specific watermark removers
H3 Claude Watermark Remover
H3 ChatGPT Watermark Remover
H3 Gemini Watermark Remover
H3 ChatGPT Paste Residue Isn’t Claude’s Official Watermark
H3 Claude Text Watermark: Reconstruction, Not Hidden Characters
H2 Simple credits. Clear limits.
H3 Starter
H3 Professional
H3 Advanced
H2 Honest note on “AI watermarks”
H2 Frequently asked questions
H2 A focused tool for cleaner AI paste
H2 Ready to clean your text?

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 36 images OK

PASS

All 36 images OK

2 decorative image(s) correctly marked

34 image(s) with good alt text

36 images 34 good alt text 2 decorative

All images have appropriate alt text.

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
textarea	textarea	Paste AI-generated text to clean or humanize	aria-label

Link & Button Quality

83 links, 22 buttons — all OK

PASS

83 links, 22 buttons — all OK

12 link(s) open in new tab without warning

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

Got: https://www.anthropic.com/news/claude-text-watermark; https://www.unicode.org/charts/PDF/U2000.pdf; https://spec.commonmark.org/; https://www.freeai.run; https://tooldirs.com; https://www.toolpilot.ai; https://startupfa.st; https://deeplaunch.io; https://firstlook.tools; https://turbo0.com/item/aitextwatermarkremover (+2 more)

71 link(s) with descriptive text

83 links

0 empty

0 generic text

12 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.anthropic.com/news/claude-te…	Anthropic, How Claude’s text…	new tab	Add '(opens in new tab)' to text
https://www.unicode.org/charts/PDF/U2000…	Unicode Standard, General Punc…	new tab	Add '(opens in new tab)' to text
https://spec.commonmark.org/	CommonMark spec	new tab	Add '(opens in new tab)' to text
/blog/chatgpt-paste-hidden-characters	ChatGPT Paste Residue Isn’t …	img no alt	Add alt attribute to the image
/blog/claude-official-text-watermark	Claude Text Watermark: Reconst…	img no alt	Add alt attribute to the image
https://www.freeai.run	Featured on FreeAI	new tab	Add '(opens in new tab)' to text
https://tooldirs.com	Featured on ToolDirs	new tab	Add '(opens in new tab)' to text
https://www.toolpilot.ai	Featured on ToolPilot	new tab	Add '(opens in new tab)' to text
https://startupfa.st	Powered by Startup Fast	new tab	Add '(opens in new tab)' to text
https://deeplaunch.io	Featured on DeepLaunch.io	new tab	Add '(opens in new tab)' to text
https://firstlook.tools	Featured on First Look	new tab	Add '(opens in new tab)' to text
https://turbo0.com/item/aitextwatermarkr…	Listed on Turbo0	new tab	Add '(opens in new tab)' to text
https://toolrain.com/item/aitextwatermar…	Listed on ToolRain	new tab	Add '(opens in new tab)' to text
https://navfolders.com	NavFolders	new tab	Add '(opens in new tab)' to text

93 links and buttons have descriptive text

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

https://www.anthropic.com/news/claude-text-watermark; https://www.unicode.org/charts/PDF/U2000.pdf; https://spec.commonmark.org/; https://www.freeai.run; https://tooldirs.com; https://www.toolpilot.ai; https://startupfa.st; https://deeplaunch.io; https://firstlook.tools; https://turbo0.com/item/aitextwatermarkremover (+2 more)

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

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+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: AI Text Watermark Remover

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name AI Text Watermark Remover ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=pwa&utm_medium=install ✓Display Mode standalone ✓

Name AI Text Watermark Remover Display Mode standalone Theme Color #4b8adb Background Color #ffffff 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 AI Text Watermark Re…	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 Before noise. After …	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 Why clean your text?	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 How it works	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 Built for real paste…	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 What is an AI text w…	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 How the three paste …	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 Where teams use it	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 What people say	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 Model-specific water…	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 Simple credits. Clea…	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 Honest note on “AI…	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 Frequently asked que…	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 A focused tool for c…	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h2 Ready to clean your …	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h3 Privacy first	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h3 Surgical precision	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h3 Formatting integrity	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h3 Paste your draft	18.07:1	3.0:1	#000000	#E5EFFB	Pass
h3 Inspect what is hidd…	18.07:1	3.0:1	#000000	#E5EFFB	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.

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