Skip to content
https://webscore.now

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
85
GRADE
B
FIX
3
REVIEW
5
PASS
16
INFO
0
Checks
24
16 PASS 5 REVIEW 3 FIX
D
Mobile-Readable Font Sizes
Action
67% of visible text renders at >= 12 CSS px (175 below threshold)
FIX
67% of visible text renders at >= 12 CSS px (175 below threshold)
Warning::
175 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 ("Free"); <span> 10.0px ("55"); <span> 11.0px ("Title tag"); <span> 11.0px ("Meta description"); <span> 11.0px ("robots.txt").
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Tap Target Adequacy
Action
5 tap target(s) too small or too close together
REVIEW
5 tap target(s) too small or too close together
Warning::
5 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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title WebScore — Website Analyzer & SEO Audit Tool ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: WebScore
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name WebScore ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name WebScore Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
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 white ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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
h1 Uncover what's quietly costing you
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
32px · bottom of viewport
h2 You don’t buy a score — you buy the …
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
24px · bottom of viewport
h2 From URL to action plan in under 2 minut…
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Integrate with your
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
24px · bottom of viewport
h2 tool of choice
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready to run your first scan?
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Every scan is a ranking — across four …
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What Google PageSpeed won't tell you
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pay per report. Or once — forever.
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Common questions
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Guides to help you rank, secure & optimi…
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your website has blind spots. Find them …
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
24px · bottom of viewport
h3 AI Conversion Audit
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Enter your URL
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Get your report
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Fix what matters
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
19px · bottom of viewport
h3 AI Conversion Audit
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Agent Ready audit
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Search Console Insights
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
19px · bottom of viewport
h3 MCP server for AI agents
1.17:1
#000000
on
#171717
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Uncover what's quiet…1.17:13.0:1
#000000
#171717
Fail
h2 You don’t buy a sc…1.17:13.0:1
#000000
#171717
Fail
h2 From URL to action p…1.17:13.0:1
#000000
#171717
Fail
h2 Integrate with your1.17:13.0:1
#000000
#171717
Fail
h2 tool of choice1.17:13.0:1
#000000
#171717
Fail
h2 Ready to run your fi…1.17:13.0:1
#000000
#171717
Fail
h2 Every scan is a rank…1.17:13.0:1
#000000
#171717
Fail
h2 What Google PageSpee…1.17:13.0:1
#000000
#171717
Fail
h2 Pay per report. Or o…1.17:13.0:1
#000000
#171717
Fail
h2 Common questions1.17:13.0:1
#000000
#171717
Fail
h2 Guides to help you r…1.17:13.0:1
#000000
#171717
Fail
h2 Your website has bli…1.17:13.0:1
#000000
#171717
Fail
h3 AI Conversion Audit1.17:13.0:1
#000000
#171717
Fail
h3 Enter your URL1.17:13.0:1
#000000
#171717
Fail
h3 Get your report1.17:13.0:1
#000000
#171717
Fail
h3 Fix what matters1.17:13.0:1
#000000
#171717
Fail
h3 AI Conversion Audit1.17:13.0:1
#000000
#171717
Fail
h3 Agent Ready audit1.17:13.0:1
#000000
#171717
Fail
h3 Search Console Insig…1.17:13.0:1
#000000
#171717
Fail
h3 MCP server for AI ag…1.17:13.0:1
#000000
#171717
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
27 landmarks
PASS
27 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN ASIDE CONTENTINFO footer
A+
Heading Hierarchy
28 headings
PASS
28 headings
Info::
Single H1 present
  • H1 Uncover what's quietly costing you traffic, conversions, and rankings
  • H2 You don’t buy a score — you buy the fixes
  • H3 AI Conversion Audit
  • H2 From URL to action plan in under 2 minutes
  • H3 Enter your URL
  • H3 Get your report
  • H3 Fix what matters
  • H2 Integrate with your agentic coding tool of choice
  • H2 Ready to run your first scan?
  • H2 Every scan is a ranking — across four core dimensions
  • H2 What Google PageSpeed won't tell you
  • H3 AI Conversion Audit
  • H3 Agent Ready audit
  • H3 Search Console Insights
  • H3 MCP server for AI agents
  • H2 Pay per report. Or once — forever.
  • H3 Scan free, pay per report
  • H3 Lifetime
  • H2 Common questions
  • H2 Guides to help you rank, secure & optimize
  • H3 Agent Ready: Every Check That Makes Your Site Usable by AI Agents
  • H3 AI Discoverability Check: Is Your Site Visible to ChatGPT, Claude & Perplexity?
  • H3 Free Website Security Checker: Scan Your Site in 60 Seconds
  • H2 Your website has blind spots. Find them now.
  • H3 Product
  • H3 Resources
  • H3 Company
  • H3 Free Tools
A+
Heading Text Quality
All 28 heading(s) have substantive, well-formed text
PASS
All 28 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 100 images OK
PASS
All 100 images OK
Info::
6 decorative image(s) correctly marked
Info::
94 image(s) with good alt text
100 images 94 good alt text 6 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtextWebsite URL to analyzearia-label
inputtextWebsite URL to analyzearia-label
inputtextWebsite URL to analyzearia-label
A
Form Input Types
3 input(s) using type=text where a specific type would help
PASS
3 input(s) using type=text where a specific type would help
Info::
Input "Website URL to analyze" should use type="url" (currently type="text")
Field name "Website URL to analyze" suggests type="url". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="url">.
Info::
Input "Website URL to analyze" should use type="url" (currently type="text")
Field name "Website URL to analyze" suggests type="url". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="url">.
Info::
Input "Website URL to analyze" should use type="url" (currently type="text")
Field name "Website URL to analyze" suggests type="url". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="url">.
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 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
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A
Favicon & Branding
12 icon(s) detected
PASS
12 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
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
2 mobile-depth signal(s) detected
PASS
2 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.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
A
Lighthouse Accessibility Audits
Score 93/100 — 3 failing, 27 passed
PASS
93

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
$49 div.mx-auto > div.relative > div.relative > span.text-lg

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
Show results for kreato.space aside.w-full > div.flex > div.flex > button.h-1.5
Show results for gdprfix.eu aside.w-full > div.flex > div.flex > button.h-1.5
Show results for sincronflow.tech aside.w-full > div.flex > div.flex > button.h-1.5
Show results for pantazisoft.com aside.w-full > div.flex > div.flex > button.h-1.5
Show results for pura-vida-forest-home.com aside.w-full > div.flex > div.flex > button.h-1.5

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Try the interactive demo div.max-w-5xl > div.rounded-xl > div.relative > button.group
○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 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
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○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.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback