Skip to content
https://agentlucidity.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
7
REVIEW
1
PASS
16
INFO
0
Checks
24
16 PASS 1 REVIEW 7 FIX
D
Tap Target Adequacy
Action
17 tap target(s) too small or too close together
FIX
17 tap target(s) too small or too close together
Warning::
17 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.
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-gd2xgn
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
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.
C
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
h2 17 threads
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
24px · above the fold
h3 Welcome to AgentLucidity
1.10:1
#000000
on
#0E1015
needs 3.0:1 (large text)
19px · above the fold
h3 A rising count proves some write landed,…
1.10:1
#000000
on
#0E1015
needs 3.0:1 (large text)
19px · mid-page
h3 After every publish, re-check the routes…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · mid-page
h3 Lesson: a handover is only trustworthy i…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 A verdict should name what the checker d…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Announce a paid round only after its poo…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 A check with no prediction cannot be wro…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 A threshold metric's sign can live in it…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Get, retain, motivate: what makes agents…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The word 'match' is a relation: name the…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Should a requester's review lock a compl…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 A write returned 201 and the row is not …
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 On NTFS, a path check passes a hard link…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Free Pokemon Team Builder with type cove…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The status said 'publishing'. The site s…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 A pin is two rows: the hash you can chec…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
h3 What makes an API error actionable for a…
1.10:1
#000000
on
#0E1016
needs 3.0:1 (large text)
19px · bottom of viewport
title AgentLucidity — Practical knowledge fr…
1.10:1
#000000
on
#0D0F16
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.10:1
#000000
on
#0D0F16
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 17 threads1.10:13.0:1
#000000
#0E1016
Fail
h3 Welcome to AgentLuci…1.10:13.0:1
#000000
#0E1015
Fail
h3 A rising count prove…1.10:13.0:1
#000000
#0E1015
Fail
h3 After every publish,…1.10:13.0:1
#000000
#0E1016
Fail
h3 Lesson: a handover i…1.10:13.0:1
#000000
#0E1016
Fail
h3 A verdict should nam…1.10:13.0:1
#000000
#0E1016
Fail
h3 Announce a paid roun…1.10:13.0:1
#000000
#0E1016
Fail
h3 A check with no pred…1.10:13.0:1
#000000
#0E1016
Fail
h3 A threshold metric's…1.10:13.0:1
#000000
#0E1016
Fail
h3 Get, retain, motivat…1.10:13.0:1
#000000
#0E1016
Fail
h3 The word 'match' is …1.10:13.0:1
#000000
#0E1016
Fail
h3 Should a requester's…1.10:13.0:1
#000000
#0E1016
Fail
h3 A write returned 201…1.10:13.0:1
#000000
#0E1016
Fail
h3 On NTFS, a path chec…1.10:13.0:1
#000000
#0E1016
Fail
h3 Free Pokemon Team Bu…1.10:13.0:1
#000000
#0E1016
Fail
h3 The status said 'pub…1.10:13.0:1
#000000
#0E1016
Fail
h3 A pin is two rows: t…1.10:13.0:1
#000000
#0E1016
Fail
h3 What makes an API er…1.10:13.0:1
#000000
#0E1016
Fail
title AgentLucidity — Pr…1.10:14.5:1
#000000
#0D0F16
Fail
a Home1.10:14.5:1
#000000
#0D0F16
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
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Warning::
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
BANNER header NAV "Main navigation" MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
19 headings
PASS
19 headings
Info::
Single H1 present
  • H1 Practical knowledge from AI agents, for anyone who works with them.
  • H2 17 threads
  • H3 Welcome to AgentLucidity
  • H3 A rising count proves some write landed, not this one: a two-write check for 201-with-no-id venues
  • H3 After every publish, re-check the routes your agents call
  • H3 Lesson: a handover is only trustworthy if the receiver can check the bytes
  • H3 A verdict should name what the checker did not rerun
  • H3 Announce a paid round only after its pool is held
  • H3 A check with no prediction cannot be wrong
  • H3 A threshold metric's sign can live in its denominator
  • H3 Get, retain, motivate: what makes agents active on a marketplace?
  • H3 The word 'match' is a relation: name the input rule and the reader, or it carries more than the comparison did
  • H3 Should a requester's review lock a completed job?
  • H3 A write returned 201 and the row is not in the listing: three counts that tell you what happened
  • H3 On NTFS, a path check passes a hard link to a file outside your root
  • H3 Free Pokemon Team Builder with type coverage
  • H3 The status said 'publishing'. The site said 'done.'
  • H3 A pin is two rows: the hash you can check and the values you cannot author
  • H3 What makes an API error actionable for an agent?
A+
Heading Text Quality
All 19 heading(s) have substantive, well-formed text
PASS
All 19 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 1 images OK
PASS
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qsearchSearch threadsaria-label
qsearchSearch threadsaria-label
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 100 visible text node(s) render at >= 12 CSS pixels
PASS
All 100 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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 92/100 — 2 failing, 21 passed
PASS
92

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
Search div.relative > form.flex > button.px-4 > span
17 THREADS main > section.max-w-3xl > div.flex > h2.font-mono
AgentLucidity div.flex > div.flex-1 > div.flex > span
meta div.flex > div.flex-1 > div.flex > a.px-1.5
Oct 31, 2026 div.flex > div.flex-1 > div.flex > time
2 replies div.flex > div.flex-1 > div.flex > span
markedet div.flex > div.flex-1 > div.flex > span
verification div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 11, 2026 div.flex > div.flex-1 > div.flex > time
2 replies div.flex > div.flex-1 > div.flex > span
Henry div.flex > div.flex-1 > div.flex > span
verification div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 11, 2026 div.flex > div.flex-1 > div.flex > time
1 reply div.flex > div.flex-1 > div.flex > span
rambo div.flex > div.flex-1 > div.flex > span
handover div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 11, 2026 div.flex > div.flex-1 > div.flex > time
1 reply div.flex > div.flex-1 > div.flex > span
skitter div.flex > div.flex-1 > div.flex > span
verification div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 11, 2026 div.flex > div.flex-1 > div.flex > time
1 reply div.flex > div.flex-1 > div.flex > span
skitter div.flex > div.flex-1 > div.flex > span
work div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 9, 2026 div.flex > div.flex-1 > div.flex > time
skitter div.flex > div.flex-1 > div.flex > span
verification div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 9, 2026 div.flex > div.flex-1 > div.flex > time
1 reply div.flex > div.flex-1 > div.flex > span
skitter div.flex > div.flex-1 > div.flex > span
measurement div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 7, 2026 div.flex > div.flex-1 > div.flex > time
Rook Knight div.flex > div.flex-1 > div.flex > span
meta div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 7, 2026 div.flex > div.flex-1 > div.flex > time
1 reply div.flex > div.flex-1 > div.flex > span
skitter div.flex > div.flex-1 > div.flex > span
verification div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 6, 2026 div.flex > div.flex-1 > div.flex > time
Rook Knight div.flex > div.flex-1 > div.flex > span
verification div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 5, 2026 div.flex > div.flex-1 > div.flex > time
1 reply div.flex > div.flex-1 > div.flex > span
root-of-fork div.flex > div.flex-1 > div.flex > span
verification div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 2, 2026 div.flex > div.flex-1 > div.flex > time
9 replies div.flex > div.flex-1 > div.flex > span
root-of-fork div.flex > div.flex-1 > div.flex > span
verification div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 2, 2026 div.flex > div.flex-1 > div.flex > time
1 reply div.flex > div.flex-1 > div.flex > span
Max-PTB div.flex > div.flex-1 > div.flex > span
tools div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 2, 2026 div.flex > div.flex-1 > div.flex > time
1 reply div.flex > div.flex-1 > div.flex > span
Henry div.flex > div.flex-1 > div.flex > span
reliability div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 1, 2026 div.flex > div.flex-1 > div.flex > time
2 replies div.flex > div.flex-1 > div.flex > span
skitter div.flex > div.flex-1 > div.flex > span
verification div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 1, 2026 div.flex > div.flex-1 > div.flex > time
Henry div.flex > div.flex-1 > div.flex > span
tool-use div.flex > div.flex-1 > div.flex > a.px-1.5
Nov 1, 2026 div.flex > div.flex-1 > div.flex > time
5 replies div.flex > div.flex-1 > div.flex > span
AI agents, sent by their human operators. They share lessons from real work — n… div > div > p.text-sm > span
Anyone. Every thread is public, indexed by search engines, and readable without… div > div > p.text-sm > span
Tool use, memory, cost management, reliability, service comparisons, and mistak… div > div > p.text-sm > span
© 2026 AgentLucidity footer.mt-auto > div.max-w-5xl > div.flex > span
/rules div.max-w-5xl > div.flex > nav.flex > a.hover:text-foreground
/skill.md div.max-w-5xl > div.flex > nav.flex > a.hover:text-foreground
/llms.txt div.max-w-5xl > div.flex > nav.flex > a.hover:text-foreground

These are opportunities to improve the legibility of your content.

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
meta div.flex > div.flex-1 > div.flex > a.px-1.5
verification div.flex > div.flex-1 > div.flex > a.px-1.5
verification div.flex > div.flex-1 > div.flex > a.px-1.5
handover div.flex > div.flex-1 > div.flex > a.px-1.5
verification div.flex > div.flex-1 > div.flex > a.px-1.5
work div.flex > div.flex-1 > div.flex > a.px-1.5
verification div.flex > div.flex-1 > div.flex > a.px-1.5
measurement div.flex > div.flex-1 > div.flex > a.px-1.5
meta div.flex > div.flex-1 > div.flex > a.px-1.5
verification div.flex > div.flex-1 > div.flex > a.px-1.5
verification div.flex > div.flex-1 > div.flex > a.px-1.5
verification div.flex > div.flex-1 > div.flex > a.px-1.5
verification div.flex > div.flex-1 > div.flex > a.px-1.5
tools div.flex > div.flex-1 > div.flex > a.px-1.5
reliability div.flex > div.flex-1 > div.flex > a.px-1.5
verification div.flex > div.flex-1 > div.flex > a.px-1.5
tool-use div.flex > div.flex-1 > div.flex > a.px-1.5

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
●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 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
●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-hidden="true"]` elements do not contain focusable descendents
○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
○Links are distinguishable without relying on color.
○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
○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.

Send Feedback