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 3 REVIEW 6 FIX

Mobile-Readable Font Sizes

Action

32% of visible text renders at >= 12 CSS px (204 below threshold)

FIX

32% of visible text renders at >= 12 CSS px (204 below threshold)

204 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: <a> 11.0px ("LIVE DEMO"); <div> 11.0px ("AI-POWERED REVERSE PROXY"); <div> 10.0px ("LIVE TRAFFIC — WRENDA EDGE"); <span> 10.0px ("SIMULATION"); <span> 10.0px ("REQ").

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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.

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

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

Action

12 landmarks

REVIEW

12 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

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

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

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 Wrenda — AI Crawler Optimization & GEO Platform ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

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

1.09:1

#000000

#0F0D12

needs 3.0:1 (large text)

32px · above the fold

h1 YOUR CONTENT

1.09:1

#000000

#100E13

needs 3.0:1 (large text)

32px · mid-page

h2 WHAT AI CRAWLERS SEE

1.12:1

#000000

#101219

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 SEE IT IN ACTION

1.12:1

#000000

#101219

needs 3.0:1 (large text)

24px · bottom of viewport

h2 INTELLIGENT CONTENT TRANSFORMATION

1.12:1

#000000

#101219

needs 3.0:1 (large text)

24px · bottom of viewport

h2 FULL BROWSER RENDERING AT THE EDGE

1.12:1

#000000

#101219

needs 3.0:1 (large text)

24px · bottom of viewport

h2 KNOW WHEN AI CITES YOUR BRAND

1.12:1

#000000

#101219

needs 3.0:1 (large text)

24px · bottom of viewport

h2 EDGE-FAST RESPONSE TIMES

1.12:1

#000000

#101219

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AI AGENTS INTERACT WITH YOUR SITE

1.12:1

#000000

#101219

needs 3.0:1 (large text)

24px · bottom of viewport

h2 MEASURE WHAT ACTUALLY MOVES RANKINGS

1.12:1

#000000

#101219

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Frequently Asked Questions

1.12:1

#000000

#101219

needs 3.0:1 (large text)

24px · bottom of viewport

h2 READY TO CONTROL YOUR AI PRESENCE?

1.12:1

#000000

#101219

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h3 Connect in About 15 Minutes

1.12:1

#000000

#101219

needs 3.0:1 (large text)

19px · bottom of viewport

title Wrenda — AI Crawler Optimization & GEO…

1.07:1

#000000

#0B0C10

needs 4.5:1 (normal text)

16px · top of page (header area)

span WRENDA

1.07:1

#000000

#0B0C10

needs 4.5:1 (normal text)

16px · top of page (header area)

button Features

1.07:1

#000000

#0B0C10

needs 4.5:1 (normal text)

16px · top of page (header area)

button Solutions

1.07:1

#000000

#0B0C10

needs 4.5:1 (normal text)

16px · top of page (header area)

a Use Cases

1.07:1

#000000

#0B0C10

needs 4.5:1 (normal text)

16px · above the fold

a Pricing

1.07:1

#000000

#0B0C10

needs 4.5:1 (normal text)

16px · above the fold

a Docs

1.07:1

#000000

#0B0C10

needs 4.5:1 (normal text)

16px · above the fold

2 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 CONTROL HOW	1.09:1	3.0:1	#000000	#0F0D12	Fail
h1 YOUR CONTENT	1.09:1	3.0:1	#000000	#100E13	Fail
h2 WHAT AI CRAWLERS SEE	1.12:1	3.0:1	#000000	#101219	Fail
h2 SEE IT IN ACTION	1.12:1	3.0:1	#000000	#101219	Fail
h2 INTELLIGENT CONTENT …	1.12:1	3.0:1	#000000	#101219	Fail
h2 FULL BROWSER RENDERI…	1.12:1	3.0:1	#000000	#101219	Fail
h2 KNOW WHEN AI CITES Y…	1.12:1	3.0:1	#000000	#101219	Fail
h2 EDGE-FAST RESPONSE T…	1.12:1	3.0:1	#000000	#101219	Fail
h2 AI AGENTS INTERACT W…	1.12:1	3.0:1	#000000	#101219	Fail
h2 MEASURE WHAT ACTUALL…	1.12:1	3.0:1	#000000	#101219	Fail
h2 Frequently Asked Que…	1.12:1	3.0:1	#000000	#101219	Fail
h2 READY TO CONTROL YOU…	1.12:1	3.0:1	#000000	#101219	Fail
h3 Connect in About 15 …	1.12:1	3.0:1	#000000	#101219	Fail
title Wrenda — AI Crawle…	1.07:1	4.5:1	#000000	#0B0C10	Fail
span WRENDA	1.07:1	4.5:1	#000000	#0B0C10	Fail
button Features	1.07:1	4.5:1	#000000	#0B0C10	Fail
button Solutions	1.07:1	4.5:1	#000000	#0B0C10	Fail
a Use Cases	1.07:1	4.5:1	#000000	#0B0C10	Fail
a Pricing	1.07:1	4.5:1	#000000	#0B0C10	Fail
a Docs	1.07:1	4.5:1	#000000	#0B0C10	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

12 headings

PASS

12 headings

Single H1 present

H1 CONTROL HOW AI SEES YOUR CONTENT
H2 WHAT AI CRAWLERS SEE
H2 SEE IT IN ACTION
H3 Connect in About 15 Minutes
H2 INTELLIGENT CONTENT TRANSFORMATION
H2 FULL BROWSER RENDERING AT THE EDGE
H2 KNOW WHEN AI CITES YOUR BRAND
H2 EDGE-FAST RESPONSE TIMES
H2 AI AGENTS INTERACT WITH YOUR SITE
H2 MEASURE WHAT ACTUALLY MOVES RANKINGS
H2 Frequently Asked Questions
H2 READY TO CONTROL YOUR AI PRESENCE?

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

10 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 10 all-caps heading(s)

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

34 links, 28 buttons — all OK

PASS

34 links, 28 buttons — all OK

34 link(s) with descriptive text

34 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

62 links and buttons have descriptive text

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

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

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+

Lighthouse Accessibility Audits

Score 96/100 — 1 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
<html> `div.flex > div.flex-1 > div.font-mono > div`
<body> `div.flex > div.flex-1 > div.font-mono > div`
<div id="root"></div> `div.flex > div.flex-1 > div.font-mono > div`
</body></html> `div.flex > div.flex-1 > div.font-mono > div`
02 CRAWLER RULES `section#tour > div.max-w-[1200px] > div.flex > button.flex`
02 `div.max-w-[1200px] > div.flex > button.flex > span.opacity-50`
03 AI ENRICHMENT `section#tour > div.max-w-[1200px] > div.flex > button.flex`
03 `div.max-w-[1200px] > div.flex > button.flex > span.opacity-50`
04 PAGE OPTIMIZATIONS `section#tour > div.max-w-[1200px] > div.flex > button.flex`
04 `div.max-w-[1200px] > div.flex > button.flex > span.opacity-50`
05 LIVE ACTIVITY `section#tour > div.max-w-[1200px] > div.flex > button.flex`
05 `div.max-w-[1200px] > div.flex > button.flex > span.opacity-50`
06 ANALYTICS `section#tour > div.max-w-[1200px] > div.flex > button.flex`
06 `div.max-w-[1200px] > div.flex > button.flex > span.opacity-50`
← PREV `div.flex > div.lg:w-[320px] > div.flex > button.flex`
NEXT → `div.flex > div.lg:w-[320px] > div.flex > button.flex`
https://shop.example.com/shoes/air-max-90 `div.flex-1 > div.flex > div.flex-1 > span.text-[7px]`
Home `div.flex-1 > div.flex-1 > div.flex > span.text-[6px]`
Shoes `div.flex-1 > div.flex-1 > div.flex > span.text-[6px]`
Sale `div.flex-1 > div.flex-1 > div.flex > span.text-[6px]`
$129.99 `div.flex-1 > div.flex > div.flex-1 > div.mt-1`
ENRICHED MARKDOWN `div.flex > div.flex-1 > div.flex > span.ml-auto`
https://shop.example.com/shoes/air-max-90 `div.flex-1 > div.flex > div.flex-1 > span.text-[7px]`
∞ — never resolves `div.flex > div.flex-1 > div.flex-1 > span.text-[8px]`
https://shop.example.com/shoes/air-max-90 `div.flex-1 > div.flex > div.flex-1 > span.text-[7px]`
Home `div.flex-1 > div.flex > div.flex > span.text-[6px]`
Shoes `div.flex-1 > div.flex > div.flex > span.text-[6px]`
Sale `div.flex-1 > div.flex > div.flex > span.text-[6px]`
Cart `div.flex-1 > div.flex > div.flex > span.text-[6px]`
$159.99 `div.flex > div.flex-1 > div.flex > span.text-[7px]`
SAMPLE `div.flex > div.flex-1 > div.flex > span.text-[8px]`
ChatGPT `div.flex-1 > div.flex > div.flex > span.text-[10px]`
Perplexity `div.flex-1 > div.flex > div.flex > span.text-[10px]`
Gemini `div.flex-1 > div.flex > div.flex > span.text-[10px]`
Google AI Overviews `div.flex-1 > div.flex > div.flex > span.text-[10px]`
Microsoft Copilot `div.flex-1 > div.flex > div.flex > span.text-[10px]`
Grok `div.flex-1 > div.flex > div.flex > span.text-[10px]`
TRACKED PROMPTS `div.flex-1 > div.mt-5 > div.border > div.text-[8px]`
by plan `div.flex-1 > div.mt-5 > div.border > div.text-[8px]`
MODELS `div.flex-1 > div.mt-5 > div.border > div.text-[8px]`
per prompt `div.flex-1 > div.mt-5 > div.border > div.text-[8px]`
REFRESH `div.flex-1 > div.mt-5 > div.border > div.text-[8px]`
daily on Scale `div.flex-1 > div.mt-5 > div.border > div.text-[8px]`
POST `div.flex > div.p-4 > div.text-[var(--color-text-secondary)] > span`
How it will work → `section.py-16 > div.max-w-[1200px] > div.shrink-0 > a.no-underline`
PRODUCT `div.max-w-6xl > div.grid > div.flex > p.font-display`
DOCS `div.max-w-6xl > div.grid > div.flex > p.font-display`
COMPANY `div.max-w-6xl > div.grid > div.flex > p.font-display`
LEGAL `div.max-w-6xl > div.grid > div.flex > p.font-display`
© 2026 Wrenda. All rights reserved. `footer > div.max-w-6xl > div.flex > p.font-mono`
Accept `div.fixed > div.mx-auto > div.flex > button.rounded-md`

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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

○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

○Form elements have associated labels

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

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

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