Skip to content
https://peerpush.net

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
84
GRADE
B
FIX
3
REVIEW
4
PASS
17
INFO
0
Checks
24
17 PASS 4 REVIEW 3 FIX
D
Tabindex Anti-Patterns
Action
0 positive, 11 -1-on-focusable
FIX
0 positive, 11 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
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::
1 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 1 <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.
B
Alt Text Quality
2 of 174 images have issues
REVIEW
2 of 174 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
11 decorative image(s) correctly marked
Info::
161 image(s) with good alt text
174 images 161 good alt text 11 decorative 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | PeerPush ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A
Landmark Structure
30 landmarks
PASS
30 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 "Primary" MAIN ASIDE "Promoted products" 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
159 headings
PASS
159 headings
Info::
Single H1 present
  • H1 Get Found by People and AI
  • H2 Explore PeerPush:
  • H2 Today Top 4
  • H3 China Employee Cost Calculator
  • H3 DocMaker AI
  • H3 DeepListen
  • H3 CarClever AI Car Buying Assistant
  • H2 🔥 Promoted
  • H3 Since.dev
  • H3 Guidely
  • H2 Yesterday Top 3
  • H3 Kaltrend
  • H3 Zush
  • H3 English Accent & Pronunciation
  • H2 🔥 Promoted
  • H3 Engramic
  • H3 Easyparser
  • H2 This Week Top 2
  • H3 EntreDash
  • H3 HyperBody
  • H2 🔥 Promoted
  • H3 Wiro AI
  • H3 KOOF
  • H2 This Month Top 2
  • H3 Papertools
  • H3 Loupe
  • H2 Today's Launches
  • H3 PEGGA
  • H3 DocuGenerate
  • H3 DeepListen
  • H3 CarClever AI Car Buying Assistant
  • H3 DocMaker AI
  • H3 China Employee Cost Calculator
  • H3 DataMinimal
  • H3 Pokopedia
  • H3 ArabicKeyboard.ai
  • H3 Daily Needs Free Tools
  • H3 EvoWerk Inventory
  • H3 Plaza TAI
  • H3 Curviate
  • H3 Sharp Digital
  • H3 ShuttleOps
  • H3 Screen Issues
  • H3 Emu Apps
  • H3 Weatherling
  • H3 B-Side Band Hub
  • H3 QRNeb
  • H3 Tannorium
  • H3 ScanSeal - Offline pdf scanner | no ads
  • H3 Daywatch
  • H3 Zenda
  • H3 MarketOwl
  • H3 Veinte
  • H3 Soul Cinema
  • H3 Webault
  • H3 Modellix
  • H3 Gembound
  • H3 Budgetisto
  • H3 LeadsGen
  • H3 CheckAIContent
  • H3 CocoCroco
  • H3 Vayme
  • H3 PresuBuild
  • H3 geotag.world
  • H3 Prime Notepad
  • H3 Sentia
  • H3 Try AI Editor
  • H3 KWT WordPress to HTML Converter
  • H3 Bookniapp
  • H3 Talon Platform
  • H3 Dropclips
  • H3 The One Fix
  • H3 DebutPin
  • H3 AEO Engine
  • H3 Examina
  • H3 VoxCode.app
  • H3 AI Face Shape Detector
  • H3 PingClass
  • H3 PDF Retype
  • H3 AIUndetectable
  • H3 Image to ASCII
  • H3 Hover
  • H3 Label Sorter
  • H3 Egress Observatory
  • H3 Image to Image AI
  • H3 SysTools Email Address Verification Tool
  • H3 FxBacktest
  • H3 Invisible Texts
  • H3 UrlHatch
  • H3 Snapkin
  • H3 Glass Money
  • H3 PicReplace
  • H3 Global Data Tracker
  • H3 CleanSlate
  • H3 Juso — Korea Road Address Search
  • H3 SubSync Player
  • H3 Dual Subtitles — Bilingual Merge
  • H3 Subtitle Spell — Broadcast & OTT Style C
  • H3 Subtitle Convert — Batch SMI/SRT/VTT/ASS
  • H3 Only Frontend Jobs
  • H3 Nanorater
  • H3 Producer Tag AI
  • H3 Shuffler
  • H3 Veredict
  • H3 FlowViz
  • H3 SaveClip
  • H3 ActionBox
  • H3 Rock Identification App
  • H3 Word Hype
  • H3 LaunchGrill
  • H3 Swift Billing Solutions
  • H3 Get MCP Ads
  • H3 Suparelay
  • H3 Presidentializer
  • H3 Top Tejados Burgos
  • H3 Shortsboost
  • H3 AllInOneQR
  • H3 MCPlama
  • H3 Mote
  • H3 Ecomerate
  • H3 The Face Report
  • H3 Stardew Valley Tracker
  • H3 Zambo
  • H3 Hard Graft Focus & Study Timer
  • H3 Countdown2Binge
  • H3 Caroush
  • H3 AI//COST
  • H3 Enhance.Dating
  • H3 Kling 4.0 AI
  • H3 LGTM
  • H3 Doorstep Gifts
  • H3 Name Generator Central
  • H3 Bumpy Keys
  • H3 hodgepodge
  • H2 Browse
  • H3 Platforms
  • H3 Categories
  • H3 Alternatives
  • H3 Use Cases
  • H3 Audiences
  • H2 Monthly Visits
  • H2 Submit to 100 directories
  • H2 Latest from Blog
  • H3 One home for your work: why we built Facet Cloud
  • H2 Deals
  • H2 Hall of Fame
  • H2 Frequently asked questions
  • H3 What is PeerPush?
  • H3 How does PeerPush compare to Product Hunt?
  • H3 What is a PeerPush score?
  • H3 How do I submit my product to PeerPush?
  • H3 Can AI assistants find products listed on PeerPush?
  • H3 How much does it cost to list a product on PeerPush?
  • H2 Discover
  • H2 Integrate
  • H2 Resources
  • H2 Company
  • H2 Legal
  • H2 Social
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
4 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: 4 all-caps heading(s)
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="headlessui-combobox-input-_R_1bkilb_">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtextSearch productsaria-label
#headlessui-combobox-input-_R_1bkilb_text(Search products...)placeholder only

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

<input type="text" id="headlessui-combobox-input-_R_1bkilb_">

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
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "headlessui-combobox-input-_R_1bkilb_" should use type="search" (currently type="text")
Field name "headlessui-combobox-input-_R_1bkilb_" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
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+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 787 visible text node(s) render at >= 12 CSS pixels
PASS
All 787 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: PeerPush - Get Found by People and AI
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name PeerPush - Get Found by People and AI ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name PeerPush - Get Found by People and AI Display Mode standalone Theme Color #000000 Background Color #ffffff Icons 2 icon(s)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
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
Info::
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+
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)
ElementRatioRequiredFGBGResult
h1 Get Found by21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore PeerPush:19.57:13.0:1
#000000
#FAF5FF
Pass
h2 Today Top 419.57:13.0:1
#000000
#FAF5FF
Pass
h2 🔥 Promoted19.57:13.0:1
#000000
#FAF5FF
Pass
h2 Yesterday Top 319.57:13.0:1
#000000
#FAF5FF
Pass
h2 🔥 Promoted19.57:13.0:1
#000000
#FAF5FF
Pass
h2 This Week Top 219.57:13.0:1
#000000
#FAF5FF
Pass
h2 🔥 Promoted19.57:13.0:1
#000000
#FAF5FF
Pass
h2 This Month Top 219.57:13.0:1
#000000
#FAF5FF
Pass
h2 Today's Launches19.57:13.0:1
#000000
#FAF5FF
Pass
h2 Browse19.57:13.0:1
#000000
#FAF5FF
Pass
h2 Monthly Visits19.57:13.0:1
#000000
#FAF5FF
Pass
h2 Submit to 100 direct…19.57:13.0:1
#000000
#FAF5FF
Pass
h2 Latest from Blog19.57:13.0:1
#000000
#FAF5FF
Pass
h2 Deals19.57:13.0:1
#000000
#FAF5FF
Pass
h2 Hall of Fame19.57:13.0:1
#000000
#FAF5FF
Pass
h2 Frequently asked que…19.57:13.0:1
#000000
#FAF5FF
Pass
h2 Discover19.57:13.0:1
#000000
#FAF5FF
Pass
h2 Integrate19.57:13.0:1
#000000
#FAF5FF
Pass
h2 Resources19.57:13.0:1
#000000
#FAF5FF
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 100/100 — 0 failing, 28 passed
PASS
100

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.

○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
●Background and foreground colors have a sufficient contrast ratio
●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
●Image elements do not have `[alt]` attributes that are redundant text.
●Elements with visible text labels have matching accessible names.
○`[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.
○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
○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.

Send Feedback